beta 4 - auto import problems

[BillyTheBull]

After uninstalling everything yesterday (PT3b3 and Postgre), I downloaded and installed the new beta 4 and Postgre and re-populated my database. Everything seemed to be ok, but after playing a tournament on PS today, I re-started "auto-import" in PT3 and it crashed (completely stopped responding). After manually shutting PT3 down and re-starting it, auto-import seemed to start ok (it shows "running" in the status column and the little "wheel" is spinning), but I encountered an error message that has never occurred with the beta 3 version. Here is what it looks like:

2008/02/18 16:03:09: Auto-Import beginning
2008/02/18 16:03:09: Auto-Import beginning
2008/02/18 16:03:09: PokerStars: Starting auto-import.
2008/02/18 16:03:09: PokerStars: Loading hand history file: D:\PokerStars\HandHistory\Rose-Buur\HH20080218 T77206796 No Limit Hold'em $1 + $0.10.txt
2008/02/18 16:03:09: Unable to begin feeder import process. Reason: Unable to login to database (PT3 Beta DB1). 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?

I do not know how to check whether or not the "server is running on host", etc. -- although I don't see why it wouldn't be running -- so help in that regard is appreciated. Also, please let me know if you need additional info from me (screen shot, etc.) and I'll be happy to provide it. Thanks!

[APerfect10]

CTRL-ALT-DELETE. Do you see "postgres.exe" listed in your Processes tab? If not, the database is not started.

Go Start->Program Files->PostgreSQL 8.3->Start Service

See if the server starts then...

Best regards,

Derek

[BillyTheBull]

That worked, thanks!

However, now I am showing between 6 and 10 instances of "postgres.exe" in my task manager -- is that normal? Also, I am wondering why the service stopped running in the first place, as I did not reboot my computer between yesterday and today, and, as a matter of fact, PT3 was also running the whole time. . . .

[Josh]

The multiple postgres.exe processes is normal. PostgreSQL spawns a new process for each connection.