Maybe a silly question but do the addresses match at the client and director. Does the name client.hostname from client configuration resolve to the address of the client system? If its a different system the ditector cant connect to the file daemon. Plus is i rember correctly the file daemon should be able to reach the director and the storage daemon in version 5.x. Ditector is listening on 127.0.0.1:9101
Pieter > Op 2 mei 2019 om 11:40 heeft preash raj <preash....@gmail.com> het volgende > geschreven: > > I've also tried debbuging bconsole too; please find the result attached. > > # bconsole -d 100 -dt > Connecting to Director localhost:9101 > 02-May-2019 05:30:42 bconsole: bsock.c:236-0 Current host[ipv6:::1:9101] All > host[ipv6:::1:9101] host[ipv4:127.0.0.1:65535] > 02-May-2019 05:30:42 bconsole: bsock.c:236-0 Current > host[ipv4:127.0.0.1:9101] All host[ipv6:::1:9101] host[ipv4:127.0.0.1:9101] > 02-May-2019 05:30:42 bconsole: bsock.c:157-0 who=Director daemon > host=localhost port=9101 > 02-May-2019 05:30:42 bconsole: cram-md5.c:131-0 cram-get received: auth > cram-md5 <282828203.1556789442@bacula-dir> ssl=0 > 02-May-2019 05:30:42 bconsole: cram-md5.c:150-0 sending resp to challenge: > QT/fB9/mn9woD+IqY5+XlD > 02-May-2019 05:30:42 bconsole: cram-md5.c:79-0 send: auth cram-md5 > <1502355591.1556789442@bconsole> ssl=0 > 02-May-2019 05:30:42 bconsole: cram-md5.c:98-0 Authenticate OK > yw+DUAdzxH/MeD9/58+PXB > 02-May-2019 05:30:42 bconsole: authenticate.c:150-0 >dird: 1000 OK auth > 02-May-2019 05:30:42 bconsole: authenticate.c:157-0 <dird: 1000 OK: > bacula-dir Version: 5.2.13 (19 February 2013) > 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013) > 02-May-2019 05:30:42 bconsole: console.c:1208-0 Opened connection with > Director daemon > Enter a period to cancel a command. > *status client > The defined Client resources are: > 1: bacula-fd > 2: <client1>-fd > 3: <client2>-fd > Select Client (File daemon) resource (1-3): 02-May-2019 05:30:48 bconsole: > console.c:329-0 Got poll BNET_SUB_PROMPT > 2 > Connecting to Client <client1>-fd at <client1>:9102 > Failed to connect to Client <client1>-fd. > ==== > You have messages. > 02-May-2019 05:31:12 bconsole: console.c:329-0 Got poll BNET_EOD > > > # bconsole > Connecting to Director localhost:9101 > 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013) > Enter a period to cancel a command. > *setdebug level=100 All > Connecting to Storage daemon File at <bacula-server>:9103 > 3000 OK setdebug=100 > Connecting to Client bacula-fd at localhost:9102 > 2000 OK setdebug=100 trace=0 hangup=0 > Connecting to Client <client1>-fd at <client1>:9102 > Failed to connect to Client. > Connecting to Client <client2>-fd at <client2:ip>:9102 > Failed to connect to Client. > > >> On Thu, May 2, 2019 at 11:15 AM preash raj <preash....@gmail.com> wrote: >> 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 <mar...@lispworks.com> 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 < >>> > bacula-users@lists.sourceforge.net> 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 >>> > > Bacula-users@lists.sourceforge.net >>> > > https://lists.sourceforge.net/lists/listinfo/bacula-users >>> > > >>> > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
