Re: [Dbbalancer-users] dbbalancer-0.4.0.tar.gz
Status: Alpha
Brought to you by:
xperience
From: Andrew M. <an...@ca...> - 2001-11-03 07:10:09
|
On Sat, 2001-11-03 at 08:42, Daniel Varela Santoalla wrote: > Hello everybody. > > There's a new DBBalancer version available. It adds some functions and solves > some bugs. I'd like you all to try it. > > Change log is like this: > > 0.4.0: > - Solved password authentication bug when client doesn't supports it. > - "configure" improvements. Now tries libACE with ACE_gethrtime. > - Added parameter: daemon.dbname. Holds the dbname that the clients will have > to supply to connect. > - XML config file support definitely dropped. > - Changes in source directory structure. The "configure" script now is at top > dir. > - Documentation corrections and updates. > - UNIX (local) sockets support. You can only use UNIX "OR" TCP so far. Not > both simultaneously > - Now the tar packages and the daemon binary are lowercase to improve > standards compliancy with debian. > - Added SO_REUSEADDR to server socket to avoid errors when quickly restarting > daemon. I've uploaded a preliminary Debian package. The first problem I have encountered is that the socket location on Debian is in /var/run/postgresql, rather than in /tmp. Not exactly sure how you want to go about fixing that, but Debian does define the socket location in /usr/include/postgresql/config.h : #define DEFAULT_PGSOCKET_DIR "/var/run/postgresql" Do other installations define that value? If so, I believe DBPostgresBackend.cc and DBBalancerDaemon.cc should use it in preference to the hard-coded value. I have hacked in a: #include <postgresql/config.h> #ifndef DEFAULT_PGSOCKET_DIR #define DEFAULT_PGSOCKET_DIR "/var/run/postgresql" #endif and changed the "/tmp/.s.PGSQL.%d" into DEFAULT_PGSOCKET_DIR "/.s.PGSQL.%d" In the appropriate places. With these changes I now have dbbalancer working for me with local unix socket connections to the local database, but local connections to the pool still aren't working for me: (2051, 18:58:33.439053) (0::1) Handling connection. (2051) Wrong startup packet read (bad size or protocol version (must be 2.0). Hexdump follows. HEXDUMP 296 bytes 00 00 01 28 04 d2 16 2f 00 00 00 00 00 00 00 00 ...(.../........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 ........ (2051, 18:58:33.440190) Login process failed. (2051, 18:58:33.440256) DBPostgresPooledConnection: Login process failed. Which, considering Tom Lane's message to postgresql-hackers is presumably because the standard Debian php-pgsql is compiled with ssl support, and is attempting an SSL connection first. I'll keep hacking on it - had you had plans to fix that problem? Cheers, Andrew. -- -------------------------------------------------------------------- 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 |