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

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
  • Have you tried reinitializing the Reporting databases?  Just be aware that this deletes all history in Reporting.

    Cheers - Bob


    Having these same issues... the link to Reinitializing the Reporting databases appears to go nowhere... any chance to get this info once again?

    I'm experiencing this presently:
    2013:10:28-15:00:36 astaro ulogd[6303]: pg1: connect: FATAL:  "pg_tblspc/16546/16547" is not a valid data directory
    2013:10:28-15:00:21 astaro postgres[13715]: [2-2] DETAIL:  File "pg_tblspc/16546/16547/PG_VERSION" is missing.
    2013:10:28-15:00:26 astaro postgres[13716]: [2-1] FATAL:  "pg_tblspc/16546/16547" is not a valid data directory
Children