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

FATAL: database "reporting" does not exist

Hello,

i have a problem on one of our SG115.

On the Dashboard i have seen that the CPU is continously running at 97% and i get an error message:

"Can't use an undefined value as a HASH reference at /wfe/asg/modules/asg_dashboard.pm line 4111."

when i try to open Network Protection.

 

one of the Forum Discussions i found with the above Error, said it is my log Partition that went full.

Allthough the Dashboard says that the log Disk is at 6%, when i go to "logging & Reporting" it says:


Log partition size:   0 MB
 
Free space:   0 MB
 
Current fillup rate:   0 MB/day
 
Free space will be exhausted in   0 days at current fillup rate

 

I then logged in via SSH and did an "ls -l /var/log/":

the system.log seemed a little bit big:

-rw-r--r-- 1 root log  155997670 Sep 23 11:35 system.log

 tail /var/log/system.log:

2019:09:23-11:38:34 hostname postgres[15575]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15580]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15589]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15594]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15603]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15608]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15617]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15622]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15631]: [3-1] FATAL: database "reporting" does not exist
2019:09:23-11:38:34 hostname postgres[15636]: [3-1] FATAL: database "reporting" does not exist

 

i cant find something to look further. Everything i found related to this error ist from 2008...

 

thank you.



This thread was automatically locked due to age.
Parents Reply
  • Hi  

    Do you see Postgres service threads running in UTM9 (use ps aux | grep postgres )? Also, make sure that the device has enough space. Please check the space consumed by postgres (du -sh /var/storage/pgsql92/data/ ) and that should tell us something about the issue.

    Regards

    Jaydeep

Children
  • Hi,

    output of ps aux | grep postgres:

    postgres 6426 0.2 0.1 579096 6016 ? Ss 00:15 2:16 postgres: smtp smtp 127.0.0.1(44922) idle
    root 13988 0.0 0.0 5668 748 pts/0 S+ 13:14 0:00 grep postgres
    postgres 16952 0.0 0.1 579024 5140 ? Ss Sep23 0:02 postgres: smtp smtp 127.0.0.1(54147) idle
    postgres 30356 2.6 0.9 575724 37712 ? S Sep23 119:56 /usr/pgsql92/bin/postgres -D /var/storage/pgsql92/data
    postgres 30402 0.0 0.0 575984 872 ? Ss Sep23 0:00 postgres: checkpointer process
    postgres 30403 0.0 0.1 575984 4044 ? Ss Sep23 0:01 postgres: writer process
    postgres 30404 0.0 0.0 575984 616 ? Ss Sep23 0:02 postgres: wal writer process
    postgres 30405 0.0 0.0 576876 2192 ? Ss Sep23 0:31 postgres: autovacuum launcher process
    postgres 30406 0.0 0.0 10028 468 ? Ss Sep23 0:00 postgres: archiver process
    postgres 30407 0.5 0.0 10452 1136 ? Ss Sep23 25:43 postgres: stats collector process

     

    output of du -sh /var/storage/pgsql92/data/:

    224M    /var/storage/pgsql92/data/