Richard Huxton wrote:
> To follow up to Tom's message, you need to look at two things:
> 1. What happened at 20:09 (and *something* must have)
The only thing i can see is that at 20.19 (20.09 was a typo, but it
doesn't matter) all of the query are result in a error. Before 20.19,
there are no errors from PostgreSQL in /var/log/messages.
Here is the message log (/var/log/messages)
Mar 13 20:18:31 epauli dhcpd: Dynamic and static leases present for
192.168.1.4.
Mar 13 20:18:31 epauli dhcpd: Remove host declaration Dennis or remove
192.168.1.4
Mar 13 20:18:31 epauli dhcpd: from the dynamic address pool for
192.168.1.0/24
Mar 13 20:19:29 epauli postgres[23313]: [1-1] ERROR: syntax error at
or near "'d41261f4c273da146b119b225df7849a'" at character 64
Mar 13 20:19:29 epauli postgres[23313]: [2-1] ERROR: syntax error at
or near "hoofdid" at character 8
Mar 13 20:19:29 epauli postgres[23313]: [3-1] ERROR: syntax error at
or near "TO_CHAR" at character 17
Mar 13 20:19:29 epauli postgres[23313]: [4-1] ERROR: syntax error at
or near "TO_CHAR" at character 17
Mar 13 20:19:29 epauli postgres[23313]: [5-1] ERROR: syntax error at
or near "klasse_id" at character 17
> 2. Does pg_ctl start up the server and can you access it from psql?
No, it doesn't startup
A big problem is that pg_ctl don't log the error, also when
de log facility in the postgres conf is enabled.
When i copy a backup from 3 weeks ago to /usr/local/pgsql, the server
can startup and working correctly.
Maybe the database is corrupt?
--
Edwin Pauli
