On Monday 04 July 2005 20:55, Gary Kopp wrote: > Thinking about this some more... > > You say I should see the "hello" transmission in the fd debug output. What > explanation could there be for the director reporting a fd connection and > then a cram failure and all the while the fd has not reported a hello > message (or anything else)?
Your Director is trying to talk to the wrong machine, or there is no connection between the machines. > > -----Original Message----- > From: Kern Sibbald [mailto:[EMAIL PROTECTED] > Sent: Monday, July 04, 2005 11:15 AM > To: bacula-users@lists.sourceforge.net > Cc: Gary Kopp > Subject: Re: [Bacula-users] Knoppix bacula-fd authentication debugging? > > Hello, > > If you set the debug level to 50 or greater both on the FD and the DIR, you > should get debug output at almost every stage of the authentication > process. If you do not, then it means there was no connection. > > See specific comments below. > > On Monday 04 July 2005 18:49, Gary Kopp wrote: > > 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? > > Yes > > > 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? > > Yes, the lack of messages probably means that no connection was made, but > it definitely means that the FD did not receive any input. The first > transmission (a Hello) from the DIR should print. > > > What debugging > > steps can I take to try to pin down what's really going on? > > Turn on debug on the DIR. > Try pinging the FD from the DIR and vice-versa using *exactly* the same > address that is in the Dir's conf file. > > > --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Ìk > > _______________________________________________ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Best regards, Kern ("> /\ V_V ------------------------------------------------------- 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
