Re: [Dbbalancer-users] WG: Please help ! Connection troubles

[Andrew M. <an...@ca...>]

On Thu, 2003-12-04 at 04:46, Alexander Goldybin wrote:
> =EF=BB=BF=20
> Hi Daniel,
> =20
> first of all, thank you very much for this wonderful peace of software
> !!!
> Now about our problem - we have tried to integrate DBBalancer,
> everything is fine, the balancer and replicator can be started,
> connects themselves to the databases located on 2 different servers,
> simply great, BUT we can not connect neither to balancer nor to
> replicator at all :(...

I believe that PostgreSQL 7.4 uses a new wire protocol.  I have not
built dbbalancer against a PostgreSQL 7.4 version, I believe.

I can try and build it for you and see if that helps...

Cheers,
					Andrew.
> =20
> We have the following system:
> =20
> Debian 3 (2.4.22 kernel)
> PostgreSQL 7.4
> DBBalancer 0.4.4 - fetched per apt-get, because of compiling troubles
> connect through PHP4 and psql
> =20
> Now to our dbbalancer.conf -=20
> ------
> daemon.user =3D balancer
> daemon.host =3D <IP> (we have tried localhost too, with the same
> "success")
> daemon.auth-method =3D trust (password was tried too)
> =20
> 2 machines with successful connects
> -------
> =20
> Now our debug log if we trying to connect to user "balancer" on the
> reader port (in our case 5442):
> =20
>        =20
>         (32771, 16:39:44.736893) (01::01) Handling connection.
>         (32771, 16:39:44.736960) Processing new conection. Receiving
>         login data. (socket: 28)
>         (32771, 16:39:44.737045) Starting client connection process.
>         (32771) Error reading startup packet: Success
>         (32771, 16:39:44.737228) Login process failed.
>         (32771, 16:39:44.737296) DBPostgresPooledConnection: Login
>         process failed.
>        =20
>        =20
> psql says:=20
>        =20
>         psql: server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>        =20
>        =20
> in the postgresql.conf we can find the following:
>        =20
>         LOG: unexpected EOF on client connection
>        =20
>        =20
> :( So what could it be ? The replicator/balancer itself can connect to
> all databases perfectly, but no connects to balancer in any case :(
> ...

This is the PostgreSQL sub process dying, from the look of things.  I'm
sure the PostgreSQL folks would like to see a backtrace of that, if
that's the case - any chance of building PostgreSQL with debugging
enabled?

Or is that DBBalancer dying?

Cheers,
					Andrew.
=20
> Thank you very much in advance !!! This topic is really important for
> us, I would be very grateful if you could answer to this email as soon
> as possible. Thank you !!
> =20
> =20
> Kind regards,
> Alexander Goldybin
> =20
-------------------------------------------------------------------------
Andrew @ Catalyst .Net .NZ  Ltd,  PO Box 11-053,  Manners St,  Wellington
WEB: http://catalyst.net.nz/             PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201       MOB: +64(21)635-694      OFFICE: +64(4)499-2267
        The truth is rarely pure, and never simple. - Oscar Wilde
-------------------------------------------------------------------------