Postgres fatal error message (?)

[dmg2206]

I just got back from the weekend, and found out that someone had turned off our Linux database server without properly shutting it down. PostgreSQL was running at the time. When we restarted Postgres this morning, we got the following on the terminal screen:

DEBUG: database system was interupted at 2002-08-16 16:00:39 EST
DEBUG: CheckPoint record at (0,964410968)
DEBUG: Redo record at (0, 964410968); Undo record at (0, 0); Shutdown FALSE
DEBUG: NextTransactionId: 2234424; NextOid: 578974
DEBUG: database system was not properly shut down; automatic recovery in progress...
DEBUG: ReadRecord: record with zero len at (0, 964411032)
DEBUG: redo is not required
DEBUG: database system is in production state
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "root" does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist
FATAL 1: user "Admin" does not exist
ERROR: Relation 'msysconf' does not exist

The database seems to be running fine, though. Is there anything here that I should be worried about?

 

[Hameedullah]

I can't tell you if whether you should be worred or not. But there is certainly a problem. Someon with the username 'admin' who I assume to be the administrator of the database tried to connect but couldn't possible problems:
1. User admin never existed
2. User admin was deleted from teh database

A relation/table called msysconf was tried to be accessed and it seems it does not exist and the problem is the same.

Make sure who was user 'admin' if any, if not someone tried to connect as 'admin'. Make sure if there was a relation/table/etc on the database. If not, then someone misspelled something....

There is not much that can be said. The recovery seems to be correctly performed.