Part of your reporting database has crashed/become corrupted is the reason for the problem. By manually deleting the files, you will have broken some part of reporting.
Log into the shell as root (or loginuser, then SU), then you'll need to run the following commands to get everything fixed, with each line being run separately.
/etc/init.d/postgresql stop
rm -fr /var/log/reporting/pgsql
/etc/init.d/postgresql start
mkdir /var/log/reporting/pgsql
chown postgres[:P]ostgres /var/log/reporting/pgsql
/var/storage/pgsql/init/reporting_db_init.sh -v
[BAlfson]In a post on 2012-05-09, Scott informed us:
It's even easier now. Just a single command:
/etc/init.d/postgresql rebuild
[BAlfson 2016-08-24] Several years ago, the command became
/etc/init.d/postgresql92 rebuild
Uh, guys...is this still valid? Seems I am missing something. I have a postgresql92 available, and tried this postgresql92 rebuild and then prompted for password which is not root password.
The data is filling up even after clearing logs, which I understand is not going to happen until next maintenance cycle? Just curious if this is supposed to still work with UTM 230 and 9.405-5
Thanks,
joel
Uh, guys...is this still valid? Seems I am missing something. I have a postgresql92 available, and tried this postgresql92 rebuild and then prompted for password which is not root password.
The data is filling up even after clearing logs, which I understand is not going to happen until next maintenance cycle? Just curious if this is supposed to still work with UTM 230 and 9.405-5
Thanks,
joel