Stable ? LOL ?

[Walkman_]

I wouldn't call a product stable which cannot even do the most basic and essential thing: log in to a preinstalled database...
You really expect people to pay money for this ? And they really do ? Unbelievable !

And even don't quit after the unsuccesful try with no gui... nice... !

[kraada]

We have tens of thousands of people using PT4 - it should definitely connect to existing PostgreSQL databases. What operating system are you running?

[Parket]

Nice trolling .
I never have problems with having PT4 connect to a database. Then again, I use 5 braincells to do so, so it might be a challenge for you .

[Walkman_]

We have tens of thousands of people using PT4 - it should definitely connect to existing PostgreSQL databases. What operating system are you running?

I have Ubuntu linux with PostgreSQL 9.1 which have all kinds of databases (PT3, multiple HEM, etc) on a separate machine in a local network.

I gave the same credentials to PT4 trial as I use with all of those other trackers (HEM for ex.) but all I got is this tiny little window "can't connect"... How am I suppose to debug what is happening ?

[PJs Ronin]

I am also running a Ubuntu server with Windoze in a VM and have had no probs getting postgres/PT4 to play nice.

Couple of things you might like to try. First, install postgres 9.0.x and use it instead of 9.1.x. Both the PT and HM teams don't recommend using 9.1.x as there are some issues that may cause data corruption (if I remember correctly). Secondly, when PT4 gives the error message on boot, check to see if it's listing an IP address of where it thinks the databases are/might be. The standard IP is either 'localhost' or 127.0.0.x, however your system has probably got the Ubuntu server at 10.0.0.x (or similar). On the Linux side open a terminal and type 'ifconfig' to see what the Ubuntu IP is.

Hope that helps, and welcome to the forum.

[kraada]

In addition to making sure you're using the right IP address also make sure you enabled PostgreSQL to accept incoming connections from the network by setting listen_addresses = '*' in postgres.conf - if that's commented out or set to localhost or some such PostgreSQL won't accept connections from elsewhere.

[Walkman_]

In addition to making sure you're using the right IP address also make sure you enabled PostgreSQL to accept incoming connections from the network by setting listen_addresses = '*' in postgres.conf - if that's commented out or set to localhost or some such PostgreSQL won't accept connections from elsewhere.

yea, yea, always the user is stupid (I have a small network here and you think I can't configure a simple thing like this. I appreciate your effort, but I ALREADY WROTE, that with other software everything works perfectly...)
so I shouldn't get this window either, it's MY fault, heh ?

So after 15 hours of importing (500k hands) I get this... on "View stats tab"
Error messages should say something about the type of error you know...
I definetly won't buy this ***** ** ****. Maybe I wait for PT 5 LOL

[kraada]

That error should definitely never happen. Could you at least try restarting PT4 to see if our crash reporter appears? We have integrated a crash reporter into PT4 to tell us when things go wrong what happened immediately beforehand so that we can figure out the problem and fix it.

[Walkman_]

That error should definitely never happen. Could you at least try restarting PT4 to see if our crash reporter appears? We have integrated a crash reporter into PT4 to tell us when things go wrong what happened immediately beforehand so that we can figure out the problem and fix it.

I restarted several times, no crash reporter, just the same window...

[WhiteRider]

Are you now using PostgreSQL 9.0 as suggested above? Newer versions have known problems and are not yet supported.

If you are, please report your problem so that we can check your logs and look into what is causing the crash.