Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Management, Networking, Logging and Reporting

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 12-10-2008, 08:01 AM
trossetto's Avatar
Junior Member
 
Join Date: Feb 2008
Location: Treviso
Posts: 29
Exclamation Executive Report Problem (rotate_adbs.plx ???)

hi,

I m using ASG 7.305 and on the daily executive report that I receive, I see an impossible value for "traffic processed" under Summary-->Network Usage ( I think it's the sum of all the values recorded until now, but I m not sure )

Searching on the posts archive I 've found other similar issue, so I tried to restart the ulogd service but without obtaining result. Then I see on the system.log file and I found these lines about the procedure rotate_adbs.plx :

2008:12:10-02:30:01 (none) /usr/sbin/cron[32390]: (root) CMD (nice -n19 /usr/local/bin/rotate_adbs.plx)
2008:12:10-02:30:02 (none) system: websec_aud log rotation starting
2008:12:10-02:30:02 (none) system: websec_aud log rotation finished
2008:12:10-02:30:02 (none) system: websec_aud rotation took 0 seconds to complete
2008:12:10-02:30:02 (none) system: websec_au log rotation starting
2008:12:10-02:30:02 (none) system: websec_au log rotation finished
2008:12:10-02:30:02 (none) system: websec_au rotation took 0 seconds to complete
2008:12:10-02:30:02 (none) system: ips log rotation starting
2008:12:10-02:30:02 (none) postgres[32412]: [3-1] ERROR: could not open relation 16969/16519/16563: No such file or directory
2008:12:10-02:30:02 (none) postgres[32412]: [3-2] STATEMENT: select distinct dayabs from ips where dayabs < $1
2008:12:10-02:32:01 (none) /usr/sbin/cron[32542]: (root) CMD ( nice -n19 /usr/local/bin/gen_inline_reporting_data.plx)
2008:12:10-02:32:02 (none) /usr/sbin/cron[32544]: (root) CMD (/sbin/auisys.plx --nosys)
2008:12:10-02:32:04 (none) postgres[32553]: [3-1] ERROR: could not open relation 16969/16519/16534: No such file or directory



I receive the same error if i try to do :

# psql -U reporting reporting
Welcome to psql 8.3.4, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

reporting=> SELECT * from accounting_data ;
ERROR: could not open relation 16969/16519/16534: No such file or directory

It' s here the problem? How can I resolve it?

many thanks
Reply With Quote
  #2 (permalink)  
Old 12-10-2008, 09:06 AM
Moderator
 
Join Date: May 2001
Location: Karlsruhe, Germany
Posts: 925
Default

Quote:
Originally Posted by trossetto View Post
2008:12:10-02:30:02 (none) system: ips log rotation starting
2008:12:10-02:30:02 (none) postgres[32412]: [3-1] ERROR: could not open relation 16969/16519/16563: No such file or directory
2008:12:10-02:30:02 (none) postgres[32412]: [3-2] STATEMENT: select distinct dayabs from ips where dayabs < $1
...
reporting=> SELECT * from accounting_data ;
ERROR: could not open relation 16969/16519/16534: No such file or directory
Hi,
unfortunately, your database has some corrupt tables. From the logfile snippet above, at least the ips table and the accounting (probably the archive, accounting_archive - accounting_data is a view) tables are affected.
If you don't care about the reporting data in those tables you can just wipe them all using the following command (as root):
/var/storage/pgsql/init/reporting_db_init.sh

If the data is important to you, you need to find out which database tables are corrupt, and manually drop and re-create them. Using the psql shell, you can do a "VACUUM <table>;" for each table that you can see with \d. Then you need to manually drop the views that rely on the broken tables, drop the broken tables, and re-create the tables and views. You can find the create strings here: /usr/share/postgresql/contrib/astaro_reporting_tables.sql .

Sorry, doing this stuff manually is a real hazzle :/
Cheers,
andreas
__________________
GPG Key Fingerprint: FB30 CD95 55BF AC02 44A2 D4BC D7BB 9CAB 3725 FA7F
Reply With Quote
  #3 (permalink)  
Old 12-10-2008, 09:32 AM
trossetto's Avatar
Junior Member
 
Join Date: Feb 2008
Location: Treviso
Posts: 29
Default

Hey... nice shot guy!
Many thanks, I ve solved the problem with your trick!
Pratically I run these steps :

1) /etc/init.d/ulogd stop
2) DROP DATABASE reporting ; (after psql -U postgres)
3) /var/storage/pgsql/init/reporting_db_init.sh
4) /etc/init.d/ulogd start

and now the values on executive report are reset!
Now I check in the next few days if it properly proceed,
thanks again
bye
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 08:15 PM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.