Suffering a postgres lock problem

[oracle3001]

Never had this problem until about 2-3 days ago. I am finding that if I run PT3 once it is no problem. Then if I shut it down, and try to restart at a later time it fails.

Looking in the log, as suspected PT3 seems to get stuck trying to access my DB

2008/12/02 23:44:06.140: [00001832][PostgresConnection] Connecting to database: PT3 DB

And never manages to get past this.

After killing PokerTracker.exe using Task Manager, I noticed a postgres.exe hanging around. When, I try to shutdown the PostgresSql service, it won't stop properly, the single instance of postgres.exe still hangs around. If I try to kill it directly using Task Manager it says it is locked and can't be killed off that way. If I try and do a restart of postgres (using the command prompt) I get the following error

"could not create lock file "postmaster.pid": Permission denied

The only way I seem to be able to go again, is rebotting the whole machine. Is there any reason why my postgres DB is getting locked and can't be accessed or shut down? Until 2-3 days ago I have never had these problems before. Is there anything PT3 could be doing which is locking access? (using A94 btw).

[WhiteRider]

Stopping PT3 doesn't stop postgres, so you will always still see postgres processes - there should be more than one, though.
If it "could not create lock file "postmaster.pid": Permission denied" that normally means the file already exists - this means that postgres closed down incorrectly and you will need to delete the postmaster.pid file.

After you have this problem, select the last few files in C:\Program Files\PostgreSQL\8.3\data\pg_log (they're dated so just pick the recent ones), right-click and choose 'Send To Compressed/zipped Folder', then attach the zip file to a ticket on the Support system, and link to this thread in the reference field of the ticket so that we can investigate.

[oracle3001]

Ticket submitted:- 42014

Just to confirm I included the postgres logs, plus 3 PT3 logs of my attempt to play a session. I had two PT3 freezes / crashes and then a failure to start-up.

Just out of interest, something I haven't noticed before. When I start-up PT3, I notice it is spawning 2 x PokerTracker.Exe (and yes I have made sure all have been killed before I attempt a new start-up). I don't remember with previous releases this been the case, but I haven't been watching the Task Manager that closely for PokerTracker.exe's. Is this suppose to happen?

[kraada]

You should also check to make sure, if you're running Vista, that you are running PT3 as Administrator; otherwise it won't have the rights to write files in the Program Files directory tree.

There have been two PokerTracker.exe processes for quite a while now, one is much larger (in RAM usage) than the other. I wouldn't worry about that.

[APerfect10]

Two PokerTracker.exe processes is standard. One is the main application and the other is for licensing...

Best regards,

Derek