I do not have a firewall running on either system at this time, and am
able to connect to each system by ssh.
I mentioned before that these were software test boxes before we made
any drastic changes to the production machines. Well one of the tests
we were running, just borked up the RH box. On t
On Wednesday 03 August 2005 01:47 pm, Stack Stack wrote:
> Once I saw that it worked on one system(Debian), I made sure that it
> was implemented on the other (Red Hat).
>
> I am going to attempt a client install on another system. Hopefully
> this will point out which box is having the problem.
>
Once I saw that it worked on one system(Debian), I made sure that it
was implemented on the other (Red Hat).
I am going to attempt a client install on another system. Hopefully
this will point out which box is having the problem.
Thanks for the suggestion,
~Stack~
On 8/3/05, Mike Reinehr <[EMAIL
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 ve
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
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.