Sebastian Stark wrote:
Am 03.03.2006 um 01:00 schrieb Erik P. Olsen:Sebastian Stark wrote:On 01.03.2006, at 11:09, Erik P. Olsen wrote:What happens when you enter 'use bacula'?mysql> use bacula; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changedApparently I can open and use bacula database from the command line and bacula can't. I don't see any "no permission" messages so I believe the necessary permissions are in place. Could it be that a special link between bacula and mysql has not been set up and thus is missing?I am a total loss on this problem and don't know what to do other than a total reinstall of both bacula and mysql. Insidentally, both bacula-fd and bacula-sd start up without problems it is "only" bacula-dir which causes problems.Any chance that you linked bacula to a different libmysqlclient? I can see you're using mysqld 4.1, if you used 4.0 headers/libs to compile bacula this could be the problem.I don't know how I can see that. Bacula was configured using --with- mysql=/usr/local/mysql which is where I put mysql. I suppose this is the way to let bacula know which mysql to use and where to find the necessary mysql files. Or should I have done otherwise?Under Linux you can check by running ldd on the bacula binaries.Just check if you have more than one version of mysql on your machine or old files lying around (files that are left from older installations for instance). If not then this should not be a problem. It could also be problematic if you compile on another machine and then run the binary elsewhere.Something else: If bacula is not running as root, does it have enough permissions to access the unix socket (like /tmp/mysql.sock) it needs for communicating with mysql?
Maybe mysql is listening to another socket?
Can you check with strace (again, if you use Linux) what is happening?
Please see attached list. -- Regards, Erik P. Olsen
bacula-dir.lst.gz
Description: GNU Zip compressed data
