Pokertracker 3 shuts down postgreSQL?

[fumblewumble]

I had problems with Pokertracker 3 being unable to connect to postgreSQL (Unable to begin feeder import process. Reason: Unable to login to database (PT3_2008_07_19_132148). 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?)

After searching for the problem here on the forum I've tried to 'start service' from the PostgreSQL startupfolder, 'stop service', rebooted. both with and without pokertracker running. I then reinstalled PostgreSQL from the FAQ on this forum, but the problem persists. I'm able to start PostgreSQL when Pokertracker isn't running, but as soon as I start PT, it takes a long time to start and postreg shuts down from the task list as soon as PT starts.

I'm running Pokertracker 3.00 build 3 and PostgreSQL 8.3 in Win XP

[kraada]

It shouldn't be doing that; try upgrading to Beta 23 (you'll want the without PostgreSQL version as you already have PostgreSQL installed) from our downlod page and see if that helps. Beta 23 fixes a wide variety of bugs since the Build 3 release.

[oracle3001]

This is the exact problem I am having and I am running the latest Alpha (with Windows XP, so fix on other forum no use). Support tickets have been submitted in the past, but told it wasn't a PT3 problem. I keep reading this same problem time and time again, in slightly different forms, but essentially the same problem, postgres becomes unable to connect to DB's after use of PT3, and only way to get everything restarted successfully is a restart of the machine (similar trying to restart the postgres server fails).

[kraada]

Oracle,

Try stopping the PostgreSQL server, then starting PT3 without restarting PostgreSQL; some people have found that doing that will result in things working properly as PT3 in Beta 23 (or the most recent alpha) will automatically start PostgreSQL, and I suspect the root cause for this issue lies in the way that PT3 checks to see if PostgreSQL is already running.

[oracle3001]

I will give it a try, but I doubt it will make any difference. I normally can't even stop the server properly. The command just times out when I ask it to stop, leaving a couple of postgres.exe's running and no way of shutting them down. As stated the only way I find to rectify the problem is to restart the machine, and when windows is shutting down I get a postgres.exe error dialog pop-up.

I also get the postgres DB unavailable problem occasionally after a crash/freeze while using PT3. It just freezes and I find that the only way to shut down PT3 is to kill off all the remaining pokertracker.exe and pokertrackerHUD.exe's using task manager. Following this I can never restart PT3 and the postgres DB's are unavailable through pgAdmin. Again a total restart is required. What I have noticed is that this normally occurs after a playing, having stopped auto-import (and thus also the HUD) and am reviewing session. I also notice that when this happens that there are numerous PokerTrackerHUD.exe still active in the task manager, which as far as I am aware regarding the operation of PT3 should have been killed off by PT3 when the auto-import was stopped.

I should say that I have been through this via support tickets, but the last one I got basically said no isn't PT3, has to be postgres, and somebody will get in touch for a remote session. That was over a week ago, and not heard anything since, but I just assumed Xmas/New Year shut down. I only posted because it just seemed to be an awful lot of people are reporting extremely similar problems in the past month, and that I had my current version of postgres installed for many months without ever having an issue like this with PT3 or any other app that uses postgres.

[kraada]

That sound like a deeper PostgreSQL problem then, the stop services (assuming PT3 is closed) really should stop all postgres processes.

You might want to try reinstalling PostreSQL.

[oracle3001]

I have reinstalled postgres from scratch as part of a support ticket suggestion (following the instructions given on the forums), deleted all my DB's, created new ones and no joy. Also as I said I was running the current installation of postgres on my machine unchanged for many month, I think actually when PT3 was first released, with absolutely no problems. Only stated happening maybe 3 weeks ago, since when I have noticed a large number of other people reporting exactly the same issues.

My current situation is that this unavailable to connect doesn't occur every single time I use PT3, or after every use, but at least once a day (after probably opening and closing PT3 / or stop/starting auto-import 3-4 times as and when I play sessions).

Also is it not a bug that PT3 doesn't always killing off all the PokerTrackerHud.exe's when I stop auto-import. Again this isn't something that happens during every start/stop auto-import cycle, but at least once/twice a day.

[kraada]

I'll ask the development team if they have any other suggestions.

[oracle3001]

I would suggest the remote session I was promised a week+ ago would be your best bet. I was told that my logs of both PT3 and postgres weren't even showing up the crashes I have described, let alone problems with the PokerTrackerHud.exe's still running and the postgres DB's becoming unavailable. I am more than happy to try and show one of the development team the problem I am experiencing, especially if it cures a problem that seems to be effecting quite a few users.

[kraada]

Did you create a ticket to schedule that remote session?