Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 7516 views
  • Users 0 members are here
Options
Suggested
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

error database reporting does not exist

arthur.wiebe
Hello folks. I just did a factory reset on a Astaro unit running 7.302 with pattern currently at 8431.

After the reset, executive reports no longer worked, (page just came up blank), and there were a few other reports that just stopped working.

Here's my troubleshooting log:

/var/log/reporting/accu is empty
/var/log/reporting/current_report.ph doesn't exist

in system.log:
2008:10:06-07:44:31 (none) postgres[7668]: [3-1] FATAL:  database "reporting" does not exist
2008:10:06-07:44:31 (none) ulogd[2684]: pg1: unable to connect: FATAL:  database "reporting" does not exist 
2008:10:06-07:44:36 (none) postgres[7670]: [3-1] FATAL:  database "reporting" does not exist
2008:10:06-07:44:36 (none) ulogd[2684]: pg1: unable to connect: FATAL:  database "reporting" does not exist 
2008:10:06-07:44:39 (none) daemon-watcher[3148]: Watching selfmonng.plx - running fine
2008:10:06-07:44:41 (none) postgres[7671]: [3-1] FATAL:  database "reporting" does not exist
2008:10:06-07:44:41 (none) ulogd[2684]: pg1: unable to connect: FATAL:  database "reporting" does not exist 
2008:10:06-07:44:46 (none) postgres[7673]: [3-1] FATAL:  database "reporting" does not exist
2008:10:06-07:44:46 (none) ulogd[2684]: pg1: unable to connect: FATAL:  database "reporting" does not exist 

ran /usr/local/bin/reportcontrol.sh and still got same messages in system.log

also restarted cron, and verified that it's running.


This thread was automatically locked due to age.
Parents
  • 0
    Currently (starting with 7.301) the factory reset is broken - it will remove the reporting data, but not re-create the necessary tables. This bug will be fixed in 7.303.
    To re-create this manually, you can do the following steps:
    mkdir /var/log/reporting/pgsql
    chown postgres[:P]ostgres /var/log/reporting/pgsql
    /var/storage/pgsql/init/reporting_db_init.sh
    On non-HA environments this should be sufficient to get your reporting stuff back running.
    Cheers,
     andreas
  • 0 in reply to andreas
    Thanks andreas, that seemed to work great! Don't see any more errors in system.log.

    I assume there are no other known breakages when doing a factory reset with 7.302 that I didn't catch?
  • 0 in reply to arthur.wiebe
    At least none that I know of [:)]
Reply Children
No Data
Unfiltered HTML