Page 1 of 2
Killing Postgre process

Posted:
Mon Nov 03, 2008 8:31 am
by bugs
Hello, recently i`ve found that postgre process loads with the system on every boot, and that higly improves my cpu memory usage, so i decided to delete this process from auto-boot with autoruns software and successfully did that. After that when i tried to run pk3 i got connection to database error, and reload\start postgre process form start\programs\Postgre 8.3.4 doesnt help. So is there i can do despite reistalling posgre software? and if i dont, is it possible just to re-install, but not complete unintall-install process? Thanx
Re: Killing Postgre process

Posted:
Mon Nov 03, 2008 10:23 am
by kraada
You can try following the steps in
this post first as that might get PostgreSQL running for you.
If it doesn't, could you please either create a
support request containing the last few files in the C:\Program Files\PostgreSQL\8.3\data\pg_log\ folder or just post them here? You shouldn't need to reinstall PostgreSQL, and that data will tell us what's happening when PostgreSQL is trying to start.
(Though if you do want to just reinstall from scratch, you can follow
this tutorial to do so.)
Re: Killing Postgre process

Posted:
Tue Nov 04, 2008 5:42 am
by bugs
kraada tnx for answering my question.
I tried to do the first step u described, but there was no Postgre process in the services window.
And here are the last files from the log dir
postgresql-2008-10-30_235124.log
2008-10-30 23:51:24 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-30 23:51:24 MSK FATAL: the database system is starting up
2008-10-30 23:51:24 MSK LOG: database system was interrupted; last known up at 2008-10-30 11:24:48 MSK
2008-10-30 23:51:25 MSK LOG: database system was not properly shut down; automatic recovery in progress
2008-10-30 23:51:25 MSK LOG: record with zero length at 1E/F552BA68
2008-10-30 23:51:25 MSK LOG: redo is not required
2008-10-30 23:51:26 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-30 23:51:26 MSK FATAL: the database system is starting up
2008-10-30 23:51:27 MSK LOG: database system is ready to accept connections
2008-10-30 23:51:27 MSK LOG: autovacuum launcher started
2008-10-30 23:51:28 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-30 23:52:29 MSK LOG: statistics collector process (PID 384) exited with exit code 1
2008-10-30 23:52:32 MSK LOG: WAL writer process (PID 288) exited with exit code 1
2008-10-30 23:52:32 MSK LOG: terminating any other active server processes
2008-10-30 23:52:32 MSK LOG: all server processes terminated; reinitializing
2008-10-30 23:52:33 MSK FATAL: pre-existing shared memory block is still in use
2008-10-30 23:52:33 MSK HINT: Check if there are any old server processes still running, and terminate them.
postgresql-2008-10-31_001431.log
2008-10-31 00:14:32 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-31 00:14:32 MSK FATAL: the database system is starting up
2008-10-31 00:14:32 MSK LOG: database system was interrupted; last known up at 2008-10-30 23:51:26 MSK
2008-10-31 00:14:32 MSK LOG: database system was not properly shut down; automatic recovery in progress
2008-10-31 00:14:32 MSK LOG: record with zero length at 1E/F552BAB0
2008-10-31 00:14:32 MSK LOG: redo is not required
2008-10-31 00:14:34 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-31 00:14:34 MSK FATAL: the database system is starting up
2008-10-31 00:14:34 MSK LOG: database system is ready to accept connections
2008-10-31 00:14:35 MSK LOG: autovacuum launcher started
2008-10-31 00:14:35 MSK LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-10-31 00:14:44 MSK LOG: WAL writer process (PID 1432) exited with exit code 1
2008-10-31 00:14:44 MSK LOG: terminating any other active server processes
2008-10-31 00:14:44 MSK LOG: all server processes terminated; reinitializing
2008-10-31 00:14:45 MSK FATAL: pre-existing shared memory block is still in use
2008-10-31 00:14:45 MSK HINT: Check if there are any old server processes still running, and terminate them.
Re: Killing Postgre process

Posted:
Tue Nov 04, 2008 12:21 pm
by kraada
It sounds like things didn't get shut down properly at some point.
Try to shut down the process (Start --> Programs --> PostgreSQL --> Stop Services), then look for a postmaster.pid file and delete it if you can find it, then try restarting the service and see if that gets rid of the errors towards the end of the logs referencing prior processes that didn't shut down properly.
Re: Killing Postgre process

Posted:
Sat Nov 08, 2008 4:41 am
by bugs
well, i dont have postmaster.pid at all on my disk, and i tried to stop service, however it didnt help

Re: Killing Postgre process

Posted:
Sat Nov 08, 2008 10:12 am
by kraada
Press ctrl+alt+del, click Task Manager and go to the Processes tab. Look for a DrWatson process and kill it. Then try restarting PostgreSQL and it should work properly.
Re: Killing Postgre process

Posted:
Sun Nov 09, 2008 4:43 am
by bugs
kraada i dont have drwatson process runnig.. maybe i need to re-istall?
Re: Killing Postgre process

Posted:
Sun Nov 09, 2008 10:11 am
by kraada
That would certainly work, and probably be faster than trying to figure it out further at this point. I'd recommend following the steps of the [url=http://www.pokertracker.com/forums/viewtopic.php?f=45&t=8047]Total Uninstall/Reinstall FAQ{/url] in order to ensure that you've done everything properly.
Good luck!
Re: Killing Postgre process

Posted:
Fri Nov 14, 2008 5:23 pm
by bugs
when i try to backup database i get this error
Unable to login to database (PT3 DB). Reason: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?
Re: Killing Postgre process

Posted:
Fri Nov 14, 2008 6:10 pm
by kraada
That error message means that the database isn't running; given what's happened before that shouldn't be the most surprising.
You can try restarting it (with your firewall and a/v software disabled just in case they're the problem) by clicking Start --> Programs --> PostgreSQL --> Start Services