Postgresql – Postgres startup fail error

postgresql

I was running some code when my laptop shut down. Now everytime I connect to the server, I get an error message as follows:

ambangra@access1:~$ LOG:  database system shutdown was interrupted; last known up at 2014-04-03 04:27:57 SGT
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 0/1864240
LOG:  record with zero length at 0/18668CC
LOG:  redo done at 0/18668A4
LOG:  last completed transaction was at log time 2014-04-03 04:19:34.929757+08
FATAL:  xlog flush request 0/18B02DC is not satisfied --- flushed only to 0/18668CC
CONTEXT:  writing block 0 of relation base/16384/12547_vm
LOG:  startup process (PID 14919) exited with exit code 1
LOG:  aborting startup due to startup process failure

Does it mean the code is still running? I am unable to connect at all. Any help would be greatly appreciated. Thanks!

Best Answer

Hi managed to clear it up using:

pg_dump data -f

I am able to connect to the server now.

Related Solutions

PostgreSQL 9.1 Hot Backup Error: the database system is starting up

The message "The database system is starting up." does not indicate an error. The reason it is at the FATAL level is so that it will always make it to the log, regardless of the setting of log_min_messages:

http://www.postgresql.org/docs/9.1/interactive/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN

After the rsync, did you really run what you show?:

pgsql -c "select pg_stop_backup();";

Since there is, so far as I know, no pgsql executable, that would leave the backup uncompleted, and the slave would never come out of recovery mode. On the other hand, maybe you really did run psql, because otherwise I don't see how the slave would have logged such success messages as:

Log: consistent recovery state reached at 0/BF0000B0

and:

Log: streaming replication successfully connected to primary

Did you try connecting to the slave at this point? What happened?

The "Success. You can now start..." message you mention is generated by initdb, which shouldn't be run as part of setting up a slave; so I think you may be confused about something there. I'm also concerned about these apparently conflicting statements:

The only ways I have restarted Postgres is through the service postgresql-9.1 restart or /etc/init.d/postgresql-9.1 restart commands. After I receive this error, I kill all processes and again try to restart the database...

Did you try to stop the service through the service script? What happened? It might help in understanding the logs if you prefixed lines with more information. We use:

log_line_prefix = '[%m] %p %q<%u %d %r> '

The recovery.conf script looks odd. Are you copying from the master's pg_xlog directory, the slave's active pg_xlog directory, or an archive directory?

Postgresql – Streaming Replication in PostgreSQL

PostgreSQL replicas never finish recovering. This is by design. Basically a replica is always in "recovering from disaster" mode except that it is using receiving the WAL segments from the master rather than on disk.

So what you are seeing is not cause for concern. If it is not working yet, then you will need to provide a more detailed description of what you are trying to do and what is not working. But as far as you are posting it seems normal.

Best Answer

Related Solutions

PostgreSQL 9.1 Hot Backup Error: the database system is starting up

Postgresql – Streaming Replication in PostgreSQL

Related Question