Did you run the failing bconsole command while the bacula-dir and the remote bacula-fd were running with these command line args? That should make it print more debug information for both of them.
__Martin >>>>> On Thu, 2 May 2019 11:15:16 +0530, preash raj said: > > Hi Guys, > > I've tried debugging after stopping the services, please check the server > and client results below. Any clue? > > > Bacula Server: > ============= > [root@bacula ~]# bacula-dir -f -d 100 > bacula-dir: dird.c:223-0 Debug level = 100 > bacula-dir: jcr.c:140-0 read_last_jobs seek to 192 > bacula-dir: jcr.c:147-0 Read num_items=10 > bacula-dir: dir_plugins.c:160-0 Load dir plugins > bacula-dir: dir_plugins.c:162-0 No dir plugin dir! > bacula-dir: mysql.c:709-0 db_init_database first time > bacula-dir: mysql.c:177-0 mysql_init done > bacula-dir: mysql.c:202-0 mysql_real_connect done > bacula-dir: mysql.c:204-0 db_user=bacula db_name=bacula > db_password=admin@123 > bacula-dir: mysql.c:227-0 opendb ref=1 connected=1 db=5578f76a53a0 > bacula-dir: mysql.c:249-0 closedb ref=0 connected=1 db=5578f76a53a0 > bacula-dir: mysql.c:256-0 close db=5578f76a53a0 > bacula-dir: dird.c:1215-0 Unlink: > /var/spool/bacula/bacula-dir.bacula-dir.1653251192.mail > bacula-dir: pythonlib.c:102-0 No script dir. prog=DirStartUp > bacula-dir: bnet_server.c:112-0 Addresses host[ipv4:127.0.0.1:9101] > bacula-dir: job.c:1334-0 wstorage=File > bacula-dir: job.c:1343-0 wstore=File where=Job resource > bacula-dir: job.c:1034-0 JobId=0 created > Job=*JobMonitor*.2019-05-02_01.37.47_01 > > [root@bacula ~]# bacula-sd -f -d 100 > bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon > bacula-sd: jcr.c:140-0 read_last_jobs seek to 192 > bacula-sd: jcr.c:147-0 Read num_items=10 > bacula-sd: stored.c:564-0 calling init_dev /bacula/backup > bacula-sd: bnet_server.c:112-0 Addresses host[ipv4:<server IP>:9103] > bacula-sd: dev.c:318-0 init_dev: tape=0 dev_name=/bacula/backup > bacula-sd: stored.c:566-0 SD init done /bacula/backup > > [root@bacula ~]# bacula-fd -f -d 100 > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > bacula-fd: jcr.c:140-0 read_last_jobs seek to 192 > bacula-fd: jcr.c:147-0 Read num_items=10 > bacula-fd: pythonlib.c:102-0 No script dir. prog=FDStartUp > bacula-fd: filed.c:276-0 filed: listening on port 9102 > bacula-fd: bnet_server.c:112-0 Addresses host[ipv4:0.0.0.0:9102] > > > Bacula Client: > ============= > root@client [~]# bacula-fd -f -d 100 > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > staff.hostdime.in-fd: jcr.c:140-0 read_last_jobs seek to 192 > staff.hostdime.in-fd: jcr.c:147-0 Read num_items=0 > staff.hostdime.in-fd: pythonlib.c:104-0 No script dir. prog=FDStartUp > staff.hostdime.in-fd: filed.c:275-0 filed: listening on port 9102 > staff.hostdime.in-fd: bnet_server.c:96-0 Addresses host[ipv4: > 103.13.242.170:9102] > > > On Wed, May 1, 2019 at 7:43 PM Martin Simmons <[email protected]> wrote: > > > The output says: "bacula-dir is already running" -- you need to stop the > > existing process first. > > > > __Martin > > > > > > >>>>> On Wed, 1 May 2019 17:44:53 +0530, preash raj said: > > > > > > Hi, > > > > > > I've tried running the Bacula in debug mode and got the below results; > > I've > > > checked with the DB and make sure the passwords are correct. Can you guys > > > please guide me through this. > > > The bacula files are located under /etc/bacula > > > ===================================================== > > > [root@bacula]# bacula-dir -f -d 100 > > > bacula-dir: dird.c:223-0 Debug level = 100 > > > 01-May 08:12 bacula-dir: ERROR TERMINATION at bsys.c:484 > > > bacula-dir is already running. pid=571 > > > Check file /var/run/bacula-dir.9101.pid > > > > > > [root@bacula]# bacula-sd -f -d 100 > > > bacula-sd: stored_conf.c:704-0 Inserting director res: bacula-mon > > > 01-May 08:12 bacula-sd: ERROR TERMINATION at bsys.c:484 > > > bacula-sd is already running. pid=32149 > > > Check file /var/run/bacula-sd.9103.pid > > > > > > [root@bacula]# bacula-fd -f -d 100 > > > bacula-fd: filed_conf.c:452-0 Inserting director res: bacula-mon > > > 01-May 08:12 bacula-fd: ERROR TERMINATION at bsys.c:484 > > > bacula-fd is already running. pid=32119 > > > Check file /var/run/bacula-fd.9102.pid > > > ===================================================== > > > > > > On Wed, May 1, 2019 at 3:43 AM Dimitri Maziuk via Bacula-users < > > > [email protected]> wrote: > > > > > > > On 4/30/19 11:42 AM, William Muriithi wrote: > > > > > Heitor, > > > > > > > > > > He is using Centos, and version 5.2.13 ended up being whats shipped > > by > > > > RedHat. Very understandable > > > > > > > > > > Do you know why RedHat does ship something newer? Like even version > > 7? > > > > > > > > RedHat gets paid for supporting their customers. Presumably they have > > > > reasons for not supporting newer bacula versions. At least 5.2.13 is > > > > still in base, there have been several instances where they dropped > > > > software supported by other commercial entities altogether. DRBD, for > > > > example. > > > > > > > > Of course on centos you needn't care about RH support terms so you may > > > > as well install from upstream repo. > > > > > > > > -- > > > > Dimitri Maziuk > > > > Programmer/sysadmin > > > > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > > > > > > > _______________________________________________ > > > > Bacula-users mailing list > > > > [email protected] > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > > > > > _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
