-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry fo rm yenglish. There is no answer to an existing thread. I think,the LDAP-stuff may be the reason for the postgre/tryton-connection problem. It's just an idea, because I'm running out of them.
> Am 09.07.2010 16:08, schrieb Cédric Krier: >> On 09/07/10 15:13 +0200, Ralf Peschke wrote: >>> Hi, >>> >>> I am trying to restore a tryton-database that was pg_dumped on a >>> customers server. ( pg_dump -Fc). >>> With pg_restore I can restore the database succesfully on my server. >>> The owner is set to tryton, everything seems okay. >>> Just the tryton-client refuses to connect to the tryton-server at all: I >>> can't connect to any of the other databases: Of course, after deleting >>> the customers database, everything is okay again. >>> Restoring the customers database with the tryton-included >>> database-facility results always in an "connection pool exhausted" >>> error, regardless of the max number of connections. >>> >>> Problem of the restored database could be the configured >>> LDAP-connection. For sure, the customers LDAP-server is not reachable! >>> Could this be the reason of the problems or are there any other ideas/hints? > >> I have no idea. LDAP module should failed back to standard authentification. > >> But could you please start a new thread instead of answering to an existing. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw3O80ACgkQb2+5ZL6Nh6EJCACgpAJCJprYk+SRr5g4YHJ1VWNd coUAni3WwvrkSqXiYyKy56YIYVGwm2mG =dFTo -----END PGP SIGNATURE----- -- [email protected] mailing list
