When I do a ./bconsole and then status. I choose 4 and it says that all the daemons are running.
-- Original message -- From: <[EMAIL PROTECTED]> > > Are you certain that the storage daemon is actually running? 'ps -A' & > > look for a line with 'bacula-sd'. > > > Agree
yest it's in the host file
-- Original message -- From: <[EMAIL PROTECTED]> > > Director { > > Name = ninja3-mon > > Password = "170lKcTnVSAwDoqTiO7eZScbIXSYAjVtn5dKl6/CSPWI" > > Monitor = no > > } > Hmm. I have Monitor = yes here but I do not think this is your problem.
Didn't edit a thing except made sure all the passwords matched.
-- Original message -- From: <[EMAIL PROTECTED]> > I see all daemons are started. Could you post your bacula-sd.conf? And did you > edit > any of the .conf files after you started the daemons? > > John > > >
Here is the output from ps -A
13133 ? 00:00:00 bacula-fd13141 ? 00:00:00 bacula-dir10423 pts/1 00:11:54 ruby31504 ? 00:00:00 drbd0_worker31509 ? 00:00:00 drbd1_worker31516 ? 00:00:00 drbd2_worker31580 ? 00:00:00 drbd3_worker31686 ? 00:00:00 drbd4
SD File
torage { # definition of myself Name = ninja3-sd SDPort = 9103 # Director's port WorkingDirectory = "/var/bacula/working" Pid Directory = "/var/run" Maximum Concurrent Jobs = 20}
## List Directors who are permitted to contact Storage daem
I'm using one machine and all my files are in the /etc/bacula. I'm running 1.38.5. on linux fedora Core.
-- Original message -- From: <[EMAIL PROTECTED]> > > trust me, I've done all of that. > > > I have a few questions. What version of bacula are you running? What os /
trust me, I've done all of that.
-- Original message -- From: <[EMAIL PROTECTED]> > > Didn't edit a thing except made sure all the passwords matched. > > > The reason I asked that is any change at all in any of the .conf files with > bacula > running requires either bacu
Yes
-- Original message -- From: <[EMAIL PROTECTED]> > > When I do a ./bconsole and then status. I choose 4 and it says that all the > > daemons are running. > > That is odd because to generate the status it connects using the password. Are > you > using just one machine
> trust me, I've done all of that.
>
I have a few questions. What version of bacula are you running? What os /
version /
kernel are you running? And could you post your bacula-dir.conf? Als o are your
conf
files in /etc/bacula or /var/lib/bacula or somewhere else? Are you sure bacula
is
using
> Didn't edit a thing except made sure all the passwords matched.
>
The reason I asked that is any change at all in any of the .conf files with
bacula
running requires either bacula to be restarted (all daemons that are involved
in the
change) or you to execute reload in the the bconsole window
> Director {
> Name = ninja3-mon
> Password = "170lKcTnVSAwDoqTiO7eZScbIXSYAjVtn5dKl6/CSPWI"
> Monitor = no
> }
Hmm. I have Monitor = yes here but I do not think this is your problem.
I assume ninja3 is the name of the one machine that you are running bacula on.
Is
ninja3 in your /etc/hosts
I see all daemons are started. Could you post your bacula-sd.conf? And did you
edit
any of the .conf files after you started the daemons?
John
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?
> When I do a ./bconsole and then status. I choose 4 and it says that all the
> daemons are running.
That is odd because to generate the status it connects using the password. Are
you
using just one machine at the moment that has all the daemons installed?
> Are you certain that the storage daemon is actually running? 'ps -A' &
> look for a line with 'bacula-sd'.
>
Agreed, If you have the set the same password on the both machines this it is
highly
likely that the director is not running. Did you remember to add bacula to the
startup scripts on t
Every time I do a "run" and select client1 I get the following error messages:
01-Feb 12:58 ninja3-dir: *Console*.2006-02-01_12.51.37 Warning: bnet.c:853 Could not connect to Storage daemon on ninja3:9103. ERR=Connection refused
Retrying ...
01-Feb 13:03 ninja3-dir: *Console*.2006-02-01_12.
[EMAIL PROTECTED] wrote:
Every time I do a "run" and select client1 I get the following error
messages:
01-Feb 12:58 ninja3-dir: *Console*.2006-02-01_12.51.37 Warning:
bnet.c:853 Could not connect to Storage daemon on ninja3:9103.
ERR=Connection refused
All the passwords match is there ano
16 matches
Mail list logo
