[Refdb-users] difficulty with refdba
Status: Beta
Brought to you by:
mhoenicka
|
From: Matt P. <mat...@ut...> - 2004-01-19 22:37:36
|
Hi there, u, I'm having a little trouble getting refdba to work with the current refdb prerelease. I'm using mysql and and had no trouble creating the refdb1 database; refdbd starts up fine; and I can connect just fine to refdb1 using the mysql command-line: mysql -u matt refdb1 -p I've edited /etc/refdbarc to include my user name and password, and I've looked at refdbdrc and everything looks ok there (though I'm not absolutely sure which port my mysql server runs on, I haven't messed with it so I assume that's not a problem. refdbd starts up fine, fand using the switches suggested in the manual for installaiton testing, I get the following output: [root@anarres<520>/etc/refdb]$ refdbd -s -e 0 -l 7 dbi_driver_dir went to: dbi is up using default driver dir Available libdbi database drivers: sqlite mysql pgsql application server started use /tmp/refdbd_fifo15971 as fifo server waiting n_max_fd=4 --------------------- I then switch to another terminal to run refdba refdba -u matt Please enter your password: refdba: set serverip 127.0.0.1 port 9734 verbose f pager stdout username matt timeout 60 logfile /var/log/refdba.log logdest 2 loglevel 6 refdblib refdba: viewstat could not connect to database server ----------------------- looking in the refdbd window, I see: 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-89-34-90 send pseudo-random string to client viewstat -u matt -w 093092109054059125064105 dbi is up localhost matt <password deleted> 3306 mysql refdb failed to connect to database server command processing done, finish dialog now child finished client on fd 5 child exited with code 0 server waiting n_max_fd=4 ------------------------- obviously there's some problem with the connectin, but I'm not sure how to figure out what it is. mysql seems to be up and accepting tcp requests: $ netstat -tlnp | grep -i mysql tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1486/mysqld ... so I assume the problem is somewhere in my refdb set up. I know this should be simple, but if someone can help me with debugging &c I'd be grateful! thanks, matt |