> lmyho <lm_yho@xxxxxxxxx> writes: > > In more detail, the logs looks like: > > ... > > imcomplete startup packet > > received fast shutdown request > > shuttingdown > > database system is shut down > > logger shutting down > > > Something like this, each has a little different, but ends the same way. > > This is not a "server does not start" problem. This is something > sending SIGINT to the postmaster, which makes it terminate. > > Do all the log files mention "incomplete startup packet" right before > the shutdown request? That's not a very usual message, and it might > be a clue to what's causing the SIGINT. > > You might try setting log_line_prefix to '%m ' in postgresql.conf to add > timestamps to the log messages --- that would tell us more about which > messages are actually appearing close together in time. Hi Tom, You are right, every log file contain "incomplete startup packet", so sad.:( Actually I have timestamp in the log file, but yesterday I was typing those info to the post (as I couldn't transfer the files to Windows where I sent the emails), I just ignored it. I am copying two of them here and hope you can help me figure the things out! Also I have just finally find the reasone why system couldn't boot up last night, it boots up now (see reason below) and I am in the system already so I can copy the log files out. But doesn't change the "incomplete startup packet" line in the new log files, so the problem must still there, and will crash thesystem sometime. So please do help me out of it! Thanks!! The reason why the system couldn't boot is only because the system generated pg_hba.conf file was modified when I altered the password of user postgres. The original pg_hba.conf file has a first line read as "local all postgres ident sameuser". After I altered the passwd of postgres, I changed the end of this line to "md5", which allows me to use the passwd to login to the db as postgres through pgAdmin. But my Debian system doesn't like it! When booting the system, it found this line changed, so it refuse to startup my db server! When I changed ot back, it boots fine. But the "incomplete startup packet" line still in the log: The newest log (server still running): /pg_log# more postgresql-2006-03-30_103437.log 2006-03-30 10:34:37 CSTLOG: database system was shut down at 2006-03-30 10:33:42 CST 2006-03-30 10:34:37 CSTLOG: checkpoint record is at 0/33B9B0 2006-03-30 10:34:37 CSTLOG: redo record is at 0/33B9B0; undo record is at 0/0; shutdown TRUE 2006-03-30 10:34:37 CSTLOG: next transaction ID: 5843; next OID: 16386 2006-03-30 10:34:37 CSTLOG: next MultiXactId: 1; next MultiXactOffset: 0 2006-03-30 10:34:37 CSTLOG: database system is ready 2006-03-30 10:34:37 CSTLOG: transaction ID wrap limit is 2147484146, limited by database "postgres" 2006-03-30 10:34:37 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:34:37 CSTLOG: incomplete startup packet 2006-03-30 10:35:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:36:39 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:37:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:38:39 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:39:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:40:39 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:41:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:42:39 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:43:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:44:39 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:45:39 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:46:39 CSTLOG: autovacuum: processing database "template1" ... The last one (successful bootup and shutdown): pg_log# more postgresql-2006-03-30_103237.log 2006-03-30 10:32:37 CSTLOG: database system was shut down at 2006-03-30 10:32:20 CST 2006-03-30 10:32:37 CSTLOG: checkpoint record is at 0/33B96C 2006-03-30 10:32:37 CSTLOG: redo record is at 0/33B96C; undo record is at 0/0; shutdown TRUE 2006-03-30 10:32:37 CSTLOG: next transaction ID: 5839; next OID: 16386 2006-03-30 10:32:37 CSTLOG: next MultiXactId: 1; next MultiXactOffset: 0 2006-03-30 10:32:37 CSTLOG: database system is ready 2006-03-30 10:32:37 CSTLOG: transaction ID wrap limit is 2147484146, limited by database "postgres" 2006-03-30 10:32:37 CSTLOG: autovacuum: processing database "template1" 2006-03-30 10:33:37 CSTLOG: autovacuum: processing database "postgres" 2006-03-30 10:33:42 CSTLOG: incomplete startup packet 2006-03-30 10:33:42 CSTLOG: received fast shutdown request 2006-03-30 10:33:42 CSTLOG: shutting down 2006-03-30 10:33:42 CSTLOG: database system is shut down 2006-03-30 10:33:42 CSTLOG: logger shutting down You can see they all have that line! Can you see what's may be the problem? Thank you!!! Kind regards, lro __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
