The Knoppix 3.9 image (Debian 3.1-based) contains bacula-fd version 1.36.3 (the same version I'm running on my Dir/SD machine). After booting Knoppix on a client workstation and tweaking bacula-fd.conf for host name, password and working directory names, I start the fd with -f -d99, and see "listening on port 9102". If I try to do a client status using bconsole on my director/sd machine it complains about an authentication failure contacting the fd. The host and password in bacula-fd.conf are known to be good (the conf file was actually cloned from a working conf file on the same machine, one used successfully when the machine was natively booted without Knoppix, with only the local working directories changed). When the director's client status check failed, absolutely no debug messages were output by the fd -- the last one is still "listening". With a debug level of 99 should I see some fd debug messages when the console tries to status the client? Does the lack of messages mean fd never got the request (which I doubt, since it's an authentication error and not a connection error), or that the fd debugging level doesn't log any authentication attempts? What debugging steps can I take to try to pin down what's really going on?
--Gary Kopp ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
