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

7.306 Accounting Problem

Hi Everyone,

I installed the 7.306 Up2Date this morning and now my accounting page and executive report are not working.

I've read through a couple of threads and just would like some to confirm if database reinitialization listed in a couple of forums will fix my issue before I try it.

System log:

2009:02:09-10:08:59 (none) postgres[20062]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:08:59 (none) postgres[20062]: [3-2] STATEMENT: select "_asg_cluster".registerNodeConnection(2); unlisten "_asg_cluster_Event";
2009:02:09-10:09:04 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:08 (none) postgres[20053]: [4-1] LOG: unexpected EOF on client connection
2009:02:09-10:09:08 (none) postgres[20077]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:08 (none) postgres[20077]: [3-2] STATEMENT: select last_value::int4 from "_asg_cluster".sl_local_node_id
2009:02:09-10:09:09 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:09 (none) postgres[20079]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:09 (none) postgres[20079]: [3-2] STATEMENT: select "_asg_cluster".registerNodeConnection(2); unlisten "_asg_cluster_Event";
2009:02:09-10:09:14 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:18 (none) postgres[20077]: [4-1] LOG: unexpected EOF on client connection
2009:02:09-10:09:18 (none) postgres[20086]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:18 (none) postgres[20086]: [3-2] STATEMENT: select last_value::int4 from "_asg_cluster".sl_local_node_id
2009:02:09-10:09:19 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:19 (none) postgres[20088]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:19 (none) postgres[20088]: [3-2] STATEMENT: select "_asg_cluster".registerNodeConnection(2); unlisten "_asg_cluster_Event";
2009:02:09-10:09:24 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:28 (none) postgres[20086]: [4-1] LOG: unexpected EOF on client connection
2009:02:09-10:09:28 (none) postgres[20102]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:28 (none) postgres[20102]: [3-2] STATEMENT: select last_value::int4 from "_asg_cluster".sl_local_node_id
2009:02:09-10:09:29 (none) ulogd[9217]: pg1: error allocating keyset: Success
2009:02:09-10:09:29 (none) postgres[20104]: [3-1] ERROR: schema "_asg_cluster" does not exist
2009:02:09-10:09:29 (none) postgres[20104]: [3-2] STATEMENT: select "_asg_cluster".registerNodeConnection(2); unlisten "_asg_cluster_Event";

Thanks

This thread was automatically locked due to age.

0 BarryG over 15 years ago

If accounting was working before the update, then yes, the database is probably corrupted.
I believe the correct re-initialization procedure is at
https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/p/26603/77403#77403

You will lose all the old accounting data however.

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 15 years ago in reply to BarryG

Look here for 'reindex' and try that first.

Cheers - Bob
PS I'm 3-for-3 on situations where indexing did not solve the problem and re-initialzation was necessary.

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 adurbridge over 15 years ago in reply to BAlfson

Hi Guys,

Thanks for the input.

The system message log was showing an error with asg_cluster.....

I run in HA mode and during the up2date the systems did switch roles, so out of curiosity I rebooted the master so it went back to the master/slave roles before the update....my accounting works again.... [:S]

This might be a bug with the HA config?

Andrew
Cancel
Vote Up 0 Vote Down

Cancel
0 andreas over 15 years ago in reply to adurbridge

This indicates that the database on the current slave system is probably hosed. All accounting and reporting is only done on the master and the databases are synchronized to the slave, so if things are working now the master is fine but the slave may not.

Cheers,
andreas
Cancel
Vote Up 0 Vote Down

Cancel