Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 7512 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
    I performed a factory reset on my ASG 220, and received the "Database Reporting does not exist" error.  I attempted to recreate the reporting tables as described in this post and received the following errors:

    fw:/home/login # chown postgres[:P]ostgres /var/log/reporting/pgsql
    fw:/home/login # /var/storage/pgsql/init/reporting_db_init.sh
    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:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist

    I contacted tech support and they suggested waiting for version 7.303 to correct the problem.  I installed it yesterday, but still have the same errors:  

    2008:10:21-09:51:10 (none) postgres[8968]: [3-1] FATAL: database "reporting" does not exist 
    2008:10:21-09:51:10 (none) ulogd[2535]: pg1: unable to connect: FATAL: database "reporting" does not exist 
    2008:10:21-09:51:15 (none) postgres[8969]: [3-1] FATAL: database "reporting" does not exist 
    2008:10:21-09:51:15 (none) ulogd[2535]: pg1: unable to connect: FATAL: database "reporting" does not exist 

    Do I need to perform another factory reset or remove the /var/log/reporting/pgsql directory to recreate the reporting tables?

    Thanks for your help.
Reply
  • 0
    I performed a factory reset on my ASG 220, and received the "Database Reporting does not exist" error.  I attempted to recreate the reporting tables as described in this post and received the following errors:

    fw:/home/login # chown postgres[:P]ostgres /var/log/reporting/pgsql
    fw:/home/login # /var/storage/pgsql/init/reporting_db_init.sh
    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:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist
    psql: FATAL:  database "reporting" does not exist

    I contacted tech support and they suggested waiting for version 7.303 to correct the problem.  I installed it yesterday, but still have the same errors:  

    2008:10:21-09:51:10 (none) postgres[8968]: [3-1] FATAL: database "reporting" does not exist 
    2008:10:21-09:51:10 (none) ulogd[2535]: pg1: unable to connect: FATAL: database "reporting" does not exist 
    2008:10:21-09:51:15 (none) postgres[8969]: [3-1] FATAL: database "reporting" does not exist 
    2008:10:21-09:51:15 (none) ulogd[2535]: pg1: unable to connect: FATAL: database "reporting" does not exist 

    Do I need to perform another factory reset or remove the /var/log/reporting/pgsql directory to recreate the reporting tables?

    Thanks for your help.
Children
  • 0 in reply to ordbob
    I performed a factory reset on my ASG 220, and received the "Database Reporting does not exist" error.  I attempted to recreate the reporting tables as described in this post and received the following errors:

    fw:/home/login # chown postgres[:P]ostgres /var/log/reporting/pgsql
    fw:/home/login # /var/storage/pgsql/init/reporting_db_init.sh
    psql: FATAL:  database "root" does not exist


    Make sure (not told anywhere else, but quite critical (v7.304) that you execute the init as user postgres via the following command:

    # su postgres /var/storage/pgsql/init/reporting_db_init.sh

    I should work out nice. If you have still have problems, move the old files out of the way (mine was numbered 25***).
Unfiltered HTML