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

SG330 unresponsive for a couple of minutes with postgres[4267] error

Randomly during the day I might get this error:

"postgres[4267]: [10-1] LOG: using stale statistics instead of current ones because stats collector is not responding"

for a few minutes.

The my UTM becomes unresponsive for one minute or so and then i comes back to life.

The UTM is the SG330 with 9.355-1 firmware.

The CPU or memory load is low in general or during those errors. I cannot find any rational reason why this happens. Seems like a db bug to me.

Thanks!

This thread was automatically locked due to age.

0 BAlfson over 8 years ago in reply to IliasTsoukalis

The following command will reset the databases in reporting and the graphs in reporting. It will not affect the log files. I can't be certain that it will fix your problem.

/etc/init.d/postgresql92 rebuild

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 IliasTsoukalis over 8 years ago in reply to BAlfson

OK, so I did execute the postgres rebuild command but did not solve my problem.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 8 years ago in reply to IliasTsoukalis

Ilias, you need to be insistent that Sophos Support address this issue. Please let us know what the problem was and how they fixed it.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 IliasTsoukalis over 8 years ago in reply to BAlfson

The issue was fixed after updating to v. 9.403-4.

Cheers!

Update: I am running the last few months with the same issue. It just happens more rare and for short period of time. My thought is that this db unresponsiveness is more like a performance issue rather than a db error.
Cancel
Vote Up 0 Vote Down

Cancel
+1 IliasTsoukalis over 7 years ago

After a few months of usage and with the help of SebastianMeyer I can verify that disabling proxy cache resolves the issue.

However, I don't know if a later version fixes the problem with proxy cache enabled since there is no need for cache mode to be enabled in our company.

Cheers!
Cancel
Vote Up 0 Vote Down

Cancel