Can someone help me this this issue?

[Ruggedman]

I am sorry as I do not know what is wrong so I don't know what to make the subject of this thread. I start up PT3 and first see this:


To get it to "work." I have to stop Postgres 8.1 (Which I had for PT2).. Why is Postgres 8.1 starting up when I start PT3??? Why is postgres 8.1 even involved here.


So once i stop it I hit refresh and I see this:

Now note that PT3 was working for me earlier and this happens here n there. This program is pissing me off because its inconsistant and doesnt work 100% of the time. Also.. my DB is huge.. and I haven't clustered and vacuumed in awhile.. Probably 100-150k hands or so. I posted THAT problem in another thread.. in that I tried to do the whole works (all the house keeping features) and by the 50 minute mark I wasn't even 1% complete clustering.

I have tried rebooting and messing with the stop and start services for both 8.1 and 8.3 postgres.

[Ruggedman]

I forgot to say... after I stop Postgres 8.1 service.. I have to start 8.3 service (should be obvious) or else I get another error

[Ruggedman]

Another thing that I should note is that I just installed beta 17 today and I dont think i have had this problem often before. On the release notes you see: If the PostgreSQL service stops, PT3 attempts to restart it and reconnect. Does that have something to do with it? And where can I DL beta 16?

[WhiteRider]

It sounds like you have postgres 8.1 configured to run at startup instead of 8.3. I don't know how to change this, but I'm sure one of the postgres experts will tell you if you can't work it out for yourself.
Alternatively, just stop 8.1 and start 8.3 when you boot up.

Have you tried restarting PT3 after starting 8.3?
I suspect there may be some complications if the postgres version changes while it's running.
If you still get the error then, Please enable logging, reproduce the problem and submit your PokerTracker.log file to the Support system , and link to this thread in the reference field of the ticket so that we can investigate.

[Ruggedman]

I reinstalled PT3 beta 17 and I know no longer have the problem.. If i get it again then I will post back in this thread

[Ruggedman]

Bumping. I still have this issue. I fixed it for the time being by reinstalling beta 17 w/ postgres but I had to do this everytime I restarted my computer (because starting PT3 would give me this error). However since I DL'd beta 18 I still have this problem. Reinstalling it does not work, and anyways I am sick of doing that and its a bit sketchy.

[thebeasta]

im also getting 008/09/26 03:45:00: Unable to begin feeder import process. Reason: Unable to login to database (PT3 DB). Reason: FATAL: password authentication failed for user "postgres"

i have no postgres 8.1 only 8.3 its new laptop. any ideas? ty

[prajna]

im also getting 008/09/26 03:45:00: Unable to begin feeder import process. Reason: Unable to login to database (PT3 DB). Reason: FATAL: password authentication failed for user "postgres"

i have no postgres 8.1 only 8.3 its new laptop. any ideas? ty

Run this tutorial How To: Remove PostgreSQL Password, then try again. This will fix that for you.

[WhiteRider]

Bumping. I still have this issue. I fixed it for the time being by reinstalling beta 17 w/ postgres but I had to do this everytime I restarted my computer (because starting PT3 would give me this error). However since I DL'd beta 18 I still have this problem. Reinstalling it does not work, and anyways I am sick of doing that and its a bit sketchy.

You should be able to have 8.3 start up instead of 8.1.
Open Control Panel -> Administrative Tools -> Services.
Find Postgres in the list.
I guess you'll probably have 2 entries, for both 8.1 and 8.3?
If so, make sure that 8.3 is set to start automatically instead of 8.1