Hi,
the Log Partition Status Page shows incorrect size after changing the partition structure manually (separate Disk for /var/log), here is a picture:
OK, after mulling over things and following code paths from a to z things now became clear. Those two webadmin pages use the identical data in the backend, there's just one more step in between when computing the data for the Logging page which seems to be broken on your machine. Can you please check out the timestamps for the files in '/var/log/reporting/inline/' ? I'd assume that the timestamp for at least the logging.ph file did not change in quite a while. If so, can you please run '/usr/local/bin/gen_inline_reporting_data.plx --debug' and post the output here? This should give us precise information on where the breakage occurs.
Cheers,
andreas
Ok, the timestamp for /var/log/reporting/inline is 25.02.2009 23:40:35 and the /usr/local/bin/gen_inline_reporting_data.plx --debug gives following error :
Timeframe is defaulting to 'today'
DBI connect('dbname=reporting','reporting',...) failed: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
at /PerlApp/Astaro/Reporting/ADBShelper.pm line 573
can't open database connection to 'reporting' (retry 1 of 3)
Error: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
DBI connect('dbname=reporting','reporting',...) failed: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
at /PerlApp/Astaro/Reporting/ADBShelper.pm line 573
can't open database connection to 'reporting' (retry 2 of 3)
Error: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
DBI connect('dbname=reporting','reporting',...) failed: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
at /PerlApp/Astaro/Reporting/ADBShelper.pm line 573
can't open database connection to 'reporting' (retry 3 of 3)
Error: FATAL: could not open file "pg_tblspc/16519/16520/PG_VERSION": Permission denied
Now I wonder how you did change the partition structure, did you maybe run a stray chown on the partition contents? Can you check the permissions on the /var/log/reporting/pgsql/ directory and subdirectories? We are using a separate 'postgres' user and 'postgres' group to run the database, if the files are owned by root instead this would cause errors like the one you got.
Cheers,
andreas
Ok, it looks like there was the problem, i've copied the content without the permission or ownership information. i made a chown -R postgres : postgres to the directory /var/log/reporting/pgsql and now it works fine. I hope this was the only chown that the system needs. [8-)]
Just one minor suggestion for the next time: try 'tar cvpzf backup.tgz /var/log/' and 'tar xvpfz backup.tgz -C /var/log/', since this will preserve permissions. Thanks for trying this out, now we know that the calculations are safe against counter-wraps [:)]
Just one minor suggestion for the next time: try 'tar cvpzf backup.tgz /var/log/' and 'tar xvpfz backup.tgz -C /var/log/', since this will preserve permissions. Thanks for trying this out, now we know that the calculations are safe against counter-wraps [:)]
