[BUGS] Start up error
Hello Sir, I have installed postgresql DB on my Linux server. When I am trying to stop and start the DB, below error is reported in postgresql start up log file. FATAL: lock file postmaster.pid already exists HINT: Is another postmaster (PID 25372) running in data directory /var/lib/pgsql/data? FATAL: lock file postmaster.pid already exists HINT: Is another postmaster (PID 25372) running in data directory /var/lib/pgsql/data? I have deleted the file postmaster.pid in the directory /var/lib/pgsql/data for number of times and restarted the postgresql service, but I am still not able to restart the server and the same error is repeating again. Could you please suggest on this as the applications are completely inaccessible due to this error. ThanksRegards, -Jawad.
Re: [BUGS] Start up error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 17, 2007 at 08:19:37AM +0800, Hussain Jawad-FXRM43 wrote: Hello Sir, I have installed postgresql DB on my Linux server. When I am trying to stop and start the DB, below error is reported in postgresql start up log file. FATAL: lock file postmaster.pid already exists HINT: Is another postmaster (PID 25372) running in data directory /var/lib/pgsql/data? FATAL: lock file postmaster.pid already exists HINT: Is another postmaster (PID 25372) running in data directory /var/lib/pgsql/data? This doesn't look like a PostgreSQL bug. I'd suggest to post such questions in other mailing lists. Have a look at http://www.postgresql.org/community/lists/ especially pgsql-general or pgsql-novice I have deleted the file postmaster.pid in the directory /var/lib/pgsql/data for number of times and restarted the postgresql service, but I am still not able to restart the server and the same error is repeating again. - From your mail I gather that this postmaster.pid appears every time you start the service. Things to check: (1) are you really sure the service is not running? (try e.g. ps wwaux | grep postmaster). (2a) if the answer to (1) is service is not running, that would mean that the postmaster process starts, creates the PID file and dies unexpectedly. In this case: have you had a look at the relevant log files (typically in /var/log/postgresql -- but it depends on distribution). (2a) if the answer to (1) is is running, but your clients are not able to connect, perhaps the server is listening just on an unix domain socket while the clients are trying to contact it via an Internet socket. HTH. Regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFHPtO6Bcgs9XrR2kYRAiEAAJ4gt/IKJSHvB4kJmADWChXmXdwtSgCfW52W CiMqL1XXWgcN2X0Wi+7wumI= =g8Jw -END PGP SIGNATURE- ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] Start up error
Hussain Jawad-FXRM43 [EMAIL PROTECTED] writes: When I am trying to stop and start the DB, below error is reported in postgresql start up log file. Exactly what are you doing to start and stop the server? If you are using a startup script, whose is it? I have deleted the file postmaster.pid in the directory /var/lib/pgsql/data for number of times and restarted the postgresql service, but I am still not able to restart the server and the same error is repeating again. The best theory that comes to mind is that your start procedure is somehow starting multiple copies of the postmaster. The first one starts OK and then the second (and third?) ones fail with the lockfile complaint --- as well they should. I'm a bit afraid that your manual removals of the lockfile (which is A Bad Idea as a rule) have left you with multiple versions of the postmaster running sans lockfile. This would be very bad because you can easily end up with a corrupted database. Have you looked around with ps to verify that there really aren't any postgres-owned processes left over after a failed start? In particular, you should absolutely not see any lockfile complaints unless the PID mentioned in the message is a live process. What is PID 25372 and what is it doing? regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY
hi there i'm not sure it its really a bug - the manual specifies that COPY ... BINARY between different PGSQL versions might be problematic. nevertheless: i've imported several tables from 8.2.5 to 8.3b2 without any problems, until one table produced an error on a timestamp field: from pgsql 8.2.5: COPY users.ratings TO '/temp/ratings' BINARY; pgsql 8.3b2: COPY users.ratings FROM '/temp/ratings' BINARY; 2007-11-17 20:17:55 CET ERROR: timestamp out of range 2007-11-17 20:17:55 CET CONTEXT: COPY ratings, line 15081, column r_date when using COPY ... CVS/TEXT; everything works. by using CVS output, i was able do determine that the failing record is: 447,883,0.0,1999-01-01 00:00:00,f it seems to be the only timestamp that is failing, i've removed it from the source table and was able to binary copy the remaining data without problems. is this a bug or a feature? :) - thomas ps: is there a way to convert the binary file to plain sql to directly check which record fails? i've tried to use pg_restore to read the file, but it said does not appear to be a valid archive. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY
Thomas H. [EMAIL PROTECTED] writes: i'm not sure it its really a bug - the manual specifies that COPY ... BINARY between different PGSQL versions might be problematic. nevertheless: i've imported several tables from 8.2.5 to 8.3b2 without any problems, until one table produced an error on a timestamp field: I'll bet a nickel that you built one version with float timestamps and the other with integer ... regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY
tom lane wrote: i'm not sure it its really a bug - the manual specifies that COPY ... BINARY between different PGSQL versions might be problematic. nevertheless: i've imported several tables from 8.2.5 to 8.3b2 without any problems, until one table produced an error on a timestamp field: I'll bet a nickel that you built one version with float timestamps and the other with integer ... both versions are the official win32 builds from postgresl.org... - thomas ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
