PokerTracker

I need some help with this.
I'm running wine on ubuntu 8.10

I installed pt3 beta 24 w/o postgresql under wine

then I installed postgresql and postgresql-client packages and I changed the postgres pwd

Then i followed the instructions found on winehq and I've done:

* #wget http://www.kegel.com/wine/winetricks
* #chmod +x winetricks
* #./ winetricks fakeie6
* #./winetricks mdac28

and

* go to http://www.postgresql.org/ftp/odbc/versions
* Choose Msi
* Choose the "good" file and Download it, in my case I chose psqlodbc_08_03_100.zip (I choose the same)
* Unzip
* #wine msiexec /i psqlodbc.msi

now when I run pt3 shows up the "configure postgresql server" window. What should I write in the boxes?
I've tried with:

Server: localhost
Port:5432 (I checked and postgresql is using this port)
database user: postgres (tried also with \c postgres)
password: the password I changed at the beginning

but I have this error msg:

"Unable to connect to this database. Please check the configuration"

Is PostgreSQL actually currently running on your system? (ps auxw | grep -i post) If not, sudo /etc/init.d/postgresql-8.3 start and then try again, your settings sound good (I'll have to try this out in a bit and see if I can get PT3 working in this fashion . . . given that I'm already running Ubuntu 8.10 it hopefully shouldn't be that hard

here you are the output (forgot to say that I've already done the postgresql start stuff):

postgres 14428 0.0 0.1 42088 5192 ? S 18:33 0:01 /usr/lib/postgresql/8.3/bin/postgres -D /var/lib/postgresql/8.3/main -c config_file=/etc/postgresql/8.3/main/postgresql.conf
postgres 14431 0.0 0.0 42088 1496 ? Ss 18:33 0:00 postgres: writer process
postgres 14432 0.0 0.0 42088 1308 ? Ss 18:33 0:00 postgres: wal writer process
postgres 14433 0.0 0.0 42220 1544 ? Ss 18:33 0:00 postgres: autovacuum launcher process
postgres 14434 0.0 0.0 13408 1292 ? Ss 18:33 0:00 postgres: stats collector process
davide 19628 0.0 0.0 3236 824 pts/0 R+ 20:07 0:00 grep -i post


I don't know anything about postgresql so I don't know how to read this

The short answer is that it means postgres is running.

The longer answer is that PostgreSQL splits up its different major functions into different processes in order to improve performance. On your list, the top is the master process, the 2nd writes to the database, the 3rd is the write ahead log (think disk cache), the 4th is the autvacuum daemon (which PT3 doesn't really benefit from but that's ok), the 5th is the stats collector for database analysis purposes.

With postgresql running things should be working using localhost / 5432 / postgres / postgres's database password, but try editing the pg_hba.conf file and changing md5 for 127.0.0.1 (localhost) to trust; this will remove the need for a password for the postgres user when connecting from your own machine. Restart the PostgreSQL process (sudo /etc/init.d/postgres-8.3 restart) and try to connect again and see if it works now.

What should I change exactly? This is my .conf file:


# Database administrative login by UNIX sockets
local all postgres ident sameuser

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# "local" is for Unix domain socket connections only
local all all ident sameuser
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5

kraada wrote:(I'll have to try this out in a bit and see if I can get PT3 working in this fashion . . . given that I'm already running Ubuntu 8.10 it hopefully shouldn't be that hard

I hope you try it soon I couldn't get beta 23 (or 21/22, don't recall) to do anything but hang on the "pt3" banner graphic (comes up grayed out and that's where the fun stops; tried different "windows version" in winecfg but didn't matter).

with pt2 his final reg scheme appears incompatible w/wine (0.9.57 and 1.x) so have to stick to 2.16.x or something; is pt3 phoning home or something when that banner comes up? and maybe that's why it too hangs?

Eriol wrote:# IPv4 local connections:
host all all 127.0.0.1/32 md5

he's saying to change "md5" to "trust", restart pgsql and try pt3 again. ipv6 entry shouldn't matter.

I don't know everything that happens during that time but I do know one thing is checking for PostgreSQL running. Which is why I figure if you're being prompted for the database connections you should be okay as you're past that point . . . I'll try and check in a little bit and see what I get.

Okay, the key is you need to enable PostgreSQL to over the network, then you need to use your IP address on your local network instead.

Edit the pg_hba.conf file (located in /etc/postgresql/8.3/main) as explained in this tutorial.

You can find your local ip by running ifconfig at the command prompt it'll be listed as inet addr under your first ethernet card (by default, that'd be eth0 and the first thing listed). Most likely it'll be something like 192.168.1.100.

Put that in instead of "localhost" or "127.0.0.1" and it should connect fine. I think what's going on is that when you use localhost wine looks within the virtual windows image -- which of course isn't running the PostgreSQL server -- so you need to point PT3 at your IP address as if it's going over the network and then it'll work fine.

I was able to connect up to my own DB and see my stats, but I haven't tested importing or anything else -- I suspect they should work fine though.

I'm kind of anxious to hear if Eriol gets it going but in my case anyway, pgsql has long been enabled for private ip use I've had this problem with windows apps in the past (whether in vmware or under wine) while running pgsql 'remotely' so always use my private ip instead. but this isn't helping pt3 (just tried again w/beta 24 a few minutes ago). wrt your post what's curious is that following a fresh install of pt3 I've found it's perfectly happy using "localhost" to successfully connect to and init a brand-new db (i.e., it had been dropped and pt creates a new one itself) ; don't know if that's a clue or something.

so pt3 comes up, inits db (using localhost or private ip), displays db info panel upon completion, goes to "pt3" banner (grayed out) and that's it. it's possible from my first trial awhile back that some setting got buried in wine and is being perpetuated (like a reg entry it initialized but never updates) so maybe at some point in the future I'll erase wine, reinstall both and try again (yes, when I uninstall pt3 I remove the prog dir if necessary). it's also possible this is something related only to trial versions which I assume you aren't using. or maybe it's even just the rev of wine I'm using.

one final thing that could be a factor (but shouldn't be I wouldn't think) is that I don't use postgres user for poker dbs but the initial (successful) connection pt3 makes I mention above I give it the correct role/pw and it uses it there np (and psql says that role owns the "PT3 DB" db so pt3 did indeed use it).

anyway I realize none of this is supported so mostly just saying.