Re: [Dbbalancer-users] Re: Test failed

[Daniel V. S. <dv...@ar...>]

Hello.

The problem here seems to come from the fact that "dbbalancerd" may be us=
ing a=20
UNIX socket to listen when the clients spawned try to access via a TCP=20
socket. The dbbalancer daemon decides the type of the server socket depen=
ding=20
on the "daemon.host" parameter. If it is "local" or "localhost" it uses a=
=20
UNIX socket and else, a TCP.

BTW, which DBBalancer version are you using? I strongly encourage you to =
use=20
the latest one, since all others are... erm... "buggy".

The UNIX socket permission problems were solved in 0.4.1.

Regards
Daniel


On Mi=E9 06 Nov 2002 19:13, Andrew McMillan wrote:
> On Thu, 2002-11-07 at 02:10, Michael E. Labhard wrote:
> > Andrew:
> >
> > 	Thank you for the reply.  However, I don't see how the conf file you
> > have attached differs significantly from the one I am using.  Mine
> > appears below along with the output from the run_test.sh command.  An=
y
> > other ideas?
>
> Does the script try and do a TCP connection, or through a socket?  Are
> the permissions on the socket sufficient to allow the process to connec=
t
> to it?
>
> I know that in packaging DBBalancer for Debian I ran into a number of
> socket permission problems.
>
> Regards,
> 					Andrew.

> >
> > 6666 -> request 1: inf req/sProblem with the connection: could not
> > connect to server: Connection refused
> > 	Is the server running on host localhost and accepting
> > 	TCP/IP connections on port 6666?
> >
> >
> > 6666 -> request 1: inf req/sProblem with the connection: could not
> > connect to server: Connection refused
> > 	Is the server running on host localhost and accepting
> > 	TCP/IP connections on port 6666?

--=20

-----------------------------------------------------
Regards from Spain^H^H^H^H^H England.  Daniel Varela
-----------------------------------------------------

If you think education is expensive, try ignorance.
           -Derek Bok (Former Harvard President)