Re: [Refdb-users] can't create database conn struct
Status: Beta
Brought to you by:
mhoenicka
|
From: Markus H. <mar...@mh...> - 2003-06-17 21:02:21
|
Hi Antti, Antti Vanne writes: > I'm using refdb1 as test database, since I haven't created the default > option libdbitest.. Or should the make check work with the defaults so > that libdbi creates the named database? > This looks all fine to me. The make check implementation of libdbi 0.6.7 is actually intended to be run on an existing database, so you've done the right thing. The upcoming versions of libdbi and libdbi-drivers will have an extended make check that creates it's own database. > [root@tappi115 libdbi-0.6.7]# refdbd -s -e0 -l7 > application server started > use /tmp/refdbd_fifo28926 as fifo > server waiting n_max_fd=4 > adding client on fd 5 > server waiting n_max_fd=5 > parent removing client on fd 5 > server waiting n_max_fd=4 > try to read from client > serving client on fd 5 with protocol version 1 > 201-10-06-64 > send pseudo-random string to client > viewstat -u root > dbi is up FYI: all that has happened until here is a call to dbi_initialize() which essentially allocates some memory for the infrastructure and creates a list of available drivers. All that can go wrong at this point is a wrong directory parameter. This should either be NULL (the default) or the directory that contains the libdbi drivers. Does it help to start refdbd with the "-Y /usr/local/lib/dbd" option? > 193.167.235.115 > root > > > 3306 > mysql > /usr/local/share/refdb/db > creating database connection structure failed All that happens here is a call to dbi_conn_new(), using "mysql" as the log shows. libdbi basically tries to find a driver with the internal name "mysql" in the list of the available drivers. If that's missing, you're screwed (but your other data clearly shows it's there). As you can see, there is no interaction with the database server yet. Except trying the -Y switch, I'm basically at a loss. I won't be able to figure this out without having access to a box where this error occurs. If the -Y switch doesn't help, is there any way to provide a ssh account to do some testing on the affected box? Or would you be willing to help out and run modified versions of libdbi and refdbd that provide additional debug output? regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |