On Wednesday 03 August 2005 11:42 am, Stack Stack wrote:
> Thanks, That at least fixed the problem on the Debian box. However,
> still the same error on the Red Hat box. I reinstalled the fd client
> on the Red Hat box. I also went through every bacula file that I could
> find on both boxes, and verified that the password was set properly.
>
> Still the same error on the Red Hat box. Any suggestions? I am
> beginning to think that the password isn't the problem, and that I
> have some other setting messed up.
>
> Thanks for the help,
> ~Stack~
>
> On 8/3/05, Danie Theron <[EMAIL PROTECTED]> wrote:
> > Stack Stack wrote:
> > >Hey Guys,
> > >Well I have Bacula running on my Debian box now. I have been toying
> > >with it for a few hours, and have figured out a lot. I got different
> > >folders, files, and drives being backed up. So I decided to test out
> > >adding another box.
> > >
> > >I am attempting to add a Red Hat 9 box. I installed the Client rpm,
> > >and setup the config files on both machines as I understand they
> > >should be according to the tutorial file.
> > >When I run a backup from the Debian box, I get this error:
> > >ERROR in authenticate.c:217 Unable to authenticate console
> > >"*UserAgent*" at client:/*IP addy*/:36131.
> > >
> > >Not certain what to do on that.
> > >
> > >When I run ./bconsole from the Red Hat box I get this error:
> > >Connecting to Director /*My IP*/:9102
> > >Director authorization problem.
> > >Most likely the passwords do not agree.
> > >Please see
> > > http://www.bacula.org/html-manual/faq.html#AuthorizationErrors for
> > > help.
> > >ERR=1999 Authorization failed.
> > >
> > >I checked the passwords, they are correct. I checked the port numbers,
> > >they are correct. So I went to the website, and its a dead link. I
> > >couldn't find any errors listed as 1999, so I am quite baffled as to
> > >what is going on.
> > >
> > >If I left something out, let me know. I appreciate any help.
> > >
> > >Thanks Guys,
> > >~Stack~
> >
> > You might want to add the RH box to your hosts file /etc/hosts. Hope
> > this helps
If the problem was solved by adding the RH system name to your
/etc/hosts
file on the Debian system, then the problem was a DNS resolver problem. Have
you tried adding the Debian system name to the /etc/hosts file on your RH
system? You're likely having the same DNS resolver problem there, as well.
cmr
--
Debian 'Sarge': Registered Linux User #241964
----
"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC
--------
-------------------------------------------------------
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_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
