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

After update to 7.3 not getting daily executive report

/usr/local/bin # report_render.plx --type daily --sendmail
------
product: ASG | Astaro Security Gateway Software
running get_summary
DBD:[[:P]]g::st execute failed: ERROR: invalid page header in block 4356 of relation "accounting"
DBD:[[:P]]g::st execute failed: ERROR: invalid page header in block 4356 of relation "accounting"

/var/log/system.log

2008:09:04-09:40:20 (none) postgres[13697]: [3-1] LOG:  unexpected EOF on client connection
2008:09:04-09:40:21 (none) ulogd[2983]: input key `flow.start.sec' already has source
2008:09:04-09:40:21 (none) ulogd[2983]: stack_fsm_timer_cb: error
2008:09:04-09:40:27 (none) postgres[13737]: [3-1] ERROR:  invalid page header in block 4358 of relation "accounting"
2008:09:04-09:40:27 (none) postgres[13737]: [3-2] STATEMENT:  INSERT INTO public.accounting
2008:09:04-09:40:27 (none) postgres[13737]: [3-3]  (ip_saddr,ip_daddr,ip_protocol,l4_dport,raw_in_pktlen,raw_in_pktcount,raw_out_pktlen,raw_out_pktcount,flow_start_day,flow_start
2008:09:04-09:40:27 (none) postgres[13737]: [3-4] _sec,flow_duration) VALUES ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11);
2008:09:04-09:40:27 (none) ulogd[2983]: pg1: ERROR:  invalid page header in block 4358 of relation "accounting"
2008:09:04-09:40:27 (none) ulogd[2983]: pg1: commit failed
2008:09:04-09:40:32 (none) ulogd[2983]: input key `flow.start.sec' already has source
2008:09:04-09:40:32 (none) ulogd[2983]: stack_fsm_timer_cb: error

This thread was automatically locked due to age.

Parents

0 ewilson@ebiz.cx over 15 years ago

Iive had this problem too.  I've updated to v7.301 and still have the problem.

I droped the table and recreated it via the above instructions, and it seems good now.

Specifically the instructions are:
1.)  /etc/init.d/ulog stop
2.)  /etc/init.d/syslogng stop
3.)  /var/storage/pgsql/init/reporting_db_init.sh
4.)  /etc/init.d/syslogng start
5.)  /etc/init.d/ulog start

Function complete.
Cancel
Vote Up 0 Vote Down

Cancel
0 ahargrove over 15 years ago in reply to ewilson@ebiz.cx

Iive had this problem too.  I've updated to v7.301 and still have the problem.

I droped the table and recreated it via the above instructions, and it seems good now.

Specifically the instructions are:
1.)  /etc/init.d/ulog stop
2.)  /etc/init.d/syslogng stop
3.)  /var/storage/pgsql/init/reporting_db_init.sh
4.)  /etc/init.d/syslogng start
5.)  /etc/init.d/ulog start

Function complete.

FWIW, I had this problem too and the above instructions helped...
Cancel
Vote Up 0 Vote Down

Cancel
0 jabuin over 15 years ago in reply to ahargrove

When i run /var/storage/pgsql/init/reporting_db_init.sh
i receive this message

psql: FATAL:  database "root" does not exist
createdb: could not connect to database postgres: FATAL:  role "root" does not exist
createlang: could not connect to database reporting: FATAL:  role "root" does not exist
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:21: ERROR:  relation "accounting" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:23: ERROR:  relation "accounting_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:39: ERROR:  relation "accounting_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:41: ERROR:  relation "accountingarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:52: ERROR:  relation "auth" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:54: ERROR:  relation "auth_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:62: ERROR:  relation "ipscount" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:76: ERROR:  relation "ips" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:78: ERROR:  relation "ips_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:92: ERROR:  relation "ips_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:94: ERROR:  relation "ipsarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:108: ERROR:  relation "imp2p" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:110: ERROR:  relation "imp2p_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:124: ERROR:  relation "imp2p_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:126: ERROR:  relation "imp2parc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:144: ERROR:  relation "mailsec" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:146: ERROR:  relation "mailsec_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:164: ERROR:  relation "mailsec_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:166: ERROR:  relation "mailsecarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:178: ERROR:  relation "pfilter" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:180: ERROR:  relation "pfilter_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:181: ERROR:  relation "pfilter_srcidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:193: ERROR:  relation "pfilter_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:195: ERROR:  relation "pfilterarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:196: ERROR:  relation "pfilterarc_srcidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:210: ERROR:  relation "websec_aud" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:212: ERROR:  relation "websec_aud_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:213: ERROR:  relation "websec_aud_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:226: ERROR:  relation "websec_aud_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:228: ERROR:  relation "websec_audarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:229: ERROR:  relation "websec_audarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:241: ERROR:  relation "websec_au" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:243: ERROR:  relation "websec_au_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:244: ERROR:  relation "websec_au_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:255: ERROR:  relation "websec_au_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:257: ERROR:  relation "websec_auarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:258: ERROR:  relation "websec_auarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:275: ERROR:  relation "websec_bud" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:277: ERROR:  relation "websec_bud_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:278: ERROR:  relation "websec_bud_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:294: ERROR:  relation "websec_bud_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:296: ERROR:  relation "websec_budarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:297: ERROR:  relation "websec_budarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:326: ERROR:  relation "accounting_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:343: ERROR:  relation "imp2p_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:362: ERROR:  relation "ips_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:385: ERROR:  relation "mailsec_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:411: ERROR:  relation "mailsec_addresses" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:440: ERROR:  relation "mailsec_contacts" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:458: ERROR:  relation "pfilter_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:479: ERROR:  relation "websec_aud_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:500: ERROR:  relation "websec_au_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:525: ERROR:  relation "websec_bud_data" already exists
Cancel
Vote Up 0 Vote Down

Cancel
0 Kestutis over 15 years ago in reply to jabuin

My problem is the same.
Executive report and accounting not working [:@]

After /var/storage/pgsql/init/reporting_db_init.sh i get errors:

ERROR: tablespace "reporting" already exists
createdb: database creation failed: ERROR: database "reporting" already exists
createlang: language "plpgsql" is already installed in database "reporting"
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:21: ERROR: relation "accounting" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:23: ERROR: relation "accounting_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:39: ERROR: relation "accounting_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:41: ERROR: relation "accountingarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:52: ERROR: relation "auth" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:54: ERROR: relation "auth_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:62: ERROR: relation "ipscount" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:76: ERROR: relation "ips" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:78: ERROR: relation "ips_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:92: ERROR: relation "ips_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:94: ERROR: relation "ipsarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:108: ERROR: relation "imp2p" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:110: ERROR: relation "imp2p_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:124: ERROR: relation "imp2p_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:126: ERROR: relation "imp2parc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:144: ERROR: relation "mailsec" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:146: ERROR: relation "mailsec_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:164: ERROR: relation "mailsec_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:166: ERROR: relation "mailsecarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:178: ERROR: relation "pfilter" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:180: ERROR: relation "pfilter_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:181: ERROR: relation "pfilter_srcidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:193: ERROR: relation "pfilter_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:195: ERROR: relation "pfilterarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:196: ERROR: relation "pfilterarc_srcidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:210: ERROR: relation "websec_aud" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:212: ERROR: relation "websec_aud_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:213: ERROR: relation "websec_aud_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:226: ERROR: relation "websec_aud_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:228: ERROR: relation "websec_audarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:229: ERROR: relation "websec_audarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:241: ERROR: relation "websec_au" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:243: ERROR: relation "websec_au_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:244: ERROR: relation "websec_au_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:255: ERROR: relation "websec_au_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:257: ERROR: relation "websec_auarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:258: ERROR: relation "websec_auarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:275: ERROR: relation "websec_bud" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:277: ERROR: relation "websec_bud_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:278: ERROR: relation "websec_bud_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:294: ERROR: relation "websec_bud_archive" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:296: ERROR: relation "websec_budarc_dayidx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:297: ERROR: relation "websec_budarc_idx" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:326: ERROR: relation "accounting_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:343: ERROR: relation "imp2p_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:362: ERROR: relation "ips_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:385: ERROR: relation "mailsec_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:411: ERROR: relation "mailsec_addresses" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:440: ERROR: relation "mailsec_contacts" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:458: ERROR: relation "pfilter_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:479: ERROR: relation "websec_aud_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:500: ERROR: relation "websec_au_data" already exists
psql:/usr/share/postgresql/contrib/astaro_reporting_tables.sql:525: ERROR: relation "websec_bud_data" already exists
Cancel
Vote Up 0 Vote Down

Cancel
0 sunland_01 over 15 years ago in reply to Kestutis

Hello, befor you use the reporting script please move the following folder to the home folder

/var/log/reporting/pgsql/16***x
Cancel
Vote Up 0 Vote Down

Cancel

0 xXlAinXx over 15 years ago in reply to sunland_01

WHello!




# sudo su



# /etc/init.d/ulog stop

# /etc/init.d/syslogng stop



# cd /var/log/reporting/pgsql/ 

# mv 16*** /home





# su - postgres



> /var/storage/pgsql/init/reporting_db_init.sh



# su root

# /etc/init.d/syslogng start

# /etc/init.d/ulog start



# test -x /usr/local/bin/snort-cleanup && /usr/local/bin/snort-cleanup

# /usr/local/bin/report_render.plx --sendmail



# reboot

Best Regards

Reply

0 xXlAinXx over 15 years ago in reply to sunland_01

WHello!




# sudo su



# /etc/init.d/ulog stop

# /etc/init.d/syslogng stop



# cd /var/log/reporting/pgsql/ 

# mv 16*** /home





# su - postgres



> /var/storage/pgsql/init/reporting_db_init.sh



# su root

# /etc/init.d/syslogng start

# /etc/init.d/ulog start



# test -x /usr/local/bin/snort-cleanup && /usr/local/bin/snort-cleanup

# /usr/local/bin/report_render.plx --sendmail



# reboot

Best Regards

Children

0 jabuin over 15 years ago in reply to xXlAinXx

It WOrks NOW, TKSssss
Cancel
Vote Up 0 Vote Down

Cancel
0 pharse over 15 years ago in reply to jabuin

ur Welcome!
Cancel
Vote Up 0 Vote Down

Cancel
0 pharse over 15 years ago in reply to jabuin
Almost forgot to say.. This is just a workaround, use the code at uor risk and remember to save uor backups and config file.
By the way here one missing parts. Should be ok to run after the maintenace by superuser (root).

# killall ctasd

Best Regards
Cancel
Vote Up 0 Vote Down

Cancel
0 xXlAinXx over 15 years ago in reply to jabuin
Almost forgot to say.. This is just a workaround, use the code at uor risk and remember to save uor backups and config file.
By the way here one missing parts. Should be ok to run after the maintenace by superuser (root).

# killall ctasd

Best Regards
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 15 years ago in reply to xXlAinXx

Why kill these?

By "after the maintenance by the superuser (root)", do you mean after the reboot?

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

Uor thought is high, it's for forcing syncronyze some patterns after the reboot and deal with the
CFCTcpServer Thread Exception on Create/listen socket: Error (98) related issue, wich probably the machine could be affected to.
Cancel
Vote Up 0 Vote Down

Cancel