Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 2527 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ASG 8.301 Hung up

JimmyM
I didn't get my daily report this morning so when I went to log in to see if anything was amiss, I could not connect via browser I would get a 500 error.
Without a screen or keyboard on my ASG box, I shut it down and restarted it via the power button.

My logs from yesterday morning show the below entries in the system log.
2012:04:12-01:50:15 firewall1 postgres[26487]: [2-1] WARNING:  pgstat wait timeout
2012:04:12-01:50:25 firewall1 postgres[8162]: [6-1] WARNING:  pgstat wait timeout
2012:04:12-01:50:35 firewall1 postgres[8162]: [7-1] WARNING:  pgstat wait timeout
2012:04:12-01:50:45 firewall1 postgres[8162]: [8-1] WARNING:  pgstat wait timeout
2012:04:12-01:50:55 firewall1 postgres[8162]: [9-1] WARNING:  pgstat wait timeout
2012:04:12-01:51:05 firewall1 postgres[8162]: [10-1] WARNING:  pgstat wait timeout
2012:04:12-01:50:30 firewall1 postgres[26499]: [2-1] WARNING:  pgstat wait timeout

It would still pass traffic but I checked several logs and today's logs have entries from yesterday, but they all seem to stop at around 1:48AM on Apr 12.


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to JimmyM
    Well, it did it again.

     postgres[20744]: [2-1] WARNING:  pgstat wait timeout

    I did the report database re-initialization last week as suggested, but it apparently didn't change anything. I was running one of the lower versions of v8 previously for months with no problems. What has changed in the postgresql db since then?
  • 0 in reply to JimmyM
    And again just the other day.
    I've run ASG for months on end with no issues in the past. However, this is the first time I've ever used the remote log file archive via FTP before. Could gathering the log file data cause this sort of issue? Is the logged data even stored in the DB inside ASG?