Here is the output from ps -A
13133 ?        00:00:00 bacula-fd
13141 ?        00:00:00 bacula-dir
10423 pts/1    00:11:54 ruby
31504 ?        00:00:00 drbd0_worker
31509 ?        00:00:00 drbd1_worker
31516 ?        00:00:00 drbd2_worker
31580 ?        00:00:00 drbd3_worker
31686 ?        00:00:00 drbd4_worker
31771 ?        00:00:00 drbd5_worker
31781 ?        00:00:00 drbd6_worker
31786 ?        00:00:00 drbd7_worker
31843 ?        00:00:00 drbd8_worker
31846 ?        00:00:00 drbd9_worker
31860 ?         00:00:00 drbd0_receiver
31862 ?        00:00:00 drbd1_receiver
31864 ?        00:00:00 drbd2_receiver
31866 ?        00:00:00 drbd3_receiver
31868 ?        00:00:00 drbd4_receiver
31870 ?        00:00:00 drbd5_receiver
31872 ?        00:00:00 drbd6_receiver
31874 ?        00:00:00 drbd7_receiver
31876 ?        00:00:00 drbd8_receiver
31878 ?        00:00:00 drbd9_receiver
22905 ?        00:00:00 sshd
23129 pts/3    00:00:00 bash
23460 ?        00:00:00 bacula-sd
27203 ?        00:00:00 crond
 
-------------- Original message --------------
From: <[EMAIL PROTECTED]>

> > 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 the machine running the director? Did you reboot the director
> machine or start the daemon manually?
>
> John

Reply via email to