subject:"\[Bacula\-users\] Failed to connect to Client \-fd"

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-08 Thread Martin Simmons

The manual says that snapshot backups are supported in Bacula 7.2, but I've
never tried them.

__Martin


> On Wed, 8 May 2019 17:56:22 +0530, preash raj said:
> 
> Hi Martin,
> 
> Thank you for pointing this out; it's fixed now, excellent!
> 
> Just a heads up, can we create a snapshot backup in Bacula? let me know if
> that works even in a upgraded version.
> 
> On Fri, May 3, 2019 at 10:04 PM Martin Simmons  wrote:
> 
> > Yes, that's what I meant.
> >
> > It shows an error from the remote fd:
> >
> > Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> >
> > It looks like the Director > Name in the bacula-fd.conf on the remote fd
> > does
> > not match the Director > Name in the bacula-dir.conf.
> >
> > __Martin
> >
> >
> > > On Fri, 3 May 2019 17:20:34 +0530, preash raj said:
> > >
> > > Hi Martin,
> > >
> > > >> while the bacula-dir and the remote
> > > bacula-fd were running with these command line args?
> > >
> > > You mean starting the bacula-dir in debug mode while I check the 'status
> > > client' in bconsole?
> > > It shows the below error while try to connect the clients using bconsole.
> > > the passwords looks fine, Please let me know if you have any clue on
> > this.
> > >
> > > ==
> > > Server: bacula-dir
> > > =
> > > bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=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=-Console-.2019-05-03_04.51.02_02
> > > bacula-dir: cram-md5.c:72-0 send: auth cram-md5
> > <1917691640.1556873462@bacula-dir> ssl=0
> > > bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5
> > <1594513444.1556873462@bconsole> ssl=0
> > > bacula-dir: cram-md5.c:150-0 sending resp to challenge:
> > s5xs1Ct7B+/C/R+/d7+hcB
> > > bacula-dir: ua_status.c:142-0 status:status client:
> > > bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All
> > host[ipv4:103.13.242.170:9102]
> > > bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd host=
> > staff.hostdime.in port=9102
> > > bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon
> > > bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling
> > > bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100
> > Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> > > bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100
> > Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> > > bacula-dir: authenticate.c:218-0 cram_get_auth failed for
> > Client:staff.hostdime.in-fd
> > > bacula-dir: authenticate.c:222-0 Director and File daemon passwords or
> > names not the same.
> > > bacula-dir: bsys.c:79-0 safe_unlink unlinking:
> > /var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail
> > >
> > > ==
> > >
> > >
> > >
> > > On Fri, May 3, 2019 at 12:17 AM Martin Simmons 
> > wrote:
> > >
> > > > 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 ~]#

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-08 Thread preash raj

Hi Martin,

Thank you for pointing this out; it's fixed now, excellent!

Just a heads up, can we create a snapshot backup in Bacula? let me know if
that works even in a upgraded version.

On Fri, May 3, 2019 at 10:04 PM Martin Simmons  wrote:

> Yes, that's what I meant.
>
> It shows an error from the remote fd:
>
> Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
>
> It looks like the Director > Name in the bacula-fd.conf on the remote fd
> does
> not match the Director > Name in the bacula-dir.conf.
>
> __Martin
>
>
> > On Fri, 3 May 2019 17:20:34 +0530, preash raj said:
> >
> > Hi Martin,
> >
> > >> while the bacula-dir and the remote
> > bacula-fd were running with these command line args?
> >
> > You mean starting the bacula-dir in debug mode while I check the 'status
> > client' in bconsole?
> > It shows the below error while try to connect the clients using bconsole.
> > the passwords looks fine, Please let me know if you have any clue on
> this.
> >
> > ==
> > Server: bacula-dir
> > =
> > bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=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=-Console-.2019-05-03_04.51.02_02
> > bacula-dir: cram-md5.c:72-0 send: auth cram-md5
> <1917691640.1556873462@bacula-dir> ssl=0
> > bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5
> <1594513444.1556873462@bconsole> ssl=0
> > bacula-dir: cram-md5.c:150-0 sending resp to challenge:
> s5xs1Ct7B+/C/R+/d7+hcB
> > bacula-dir: ua_status.c:142-0 status:status client:
> > bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All
> host[ipv4:103.13.242.170:9102]
> > bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd host=
> staff.hostdime.in port=9102
> > bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon
> > bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling
> > bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100
> Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> > bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100
> Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> > bacula-dir: authenticate.c:218-0 cram_get_auth failed for
> Client:staff.hostdime.in-fd
> > bacula-dir: authenticate.c:222-0 Director and File daemon passwords or
> names not the same.
> > bacula-dir: bsys.c:79-0 safe_unlink unlinking:
> /var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail
> >
> > ==
> >
> >
> >
> > On Fri, May 3, 2019 at 12:17 AM Martin Simmons 
> wrote:
> >
> > > 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::9103]
> > > > bacula-sd: dev.c:318-0 init_dev: tape=0 dev_name=/bacula/backup

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-03 Thread Martin Simmons

Yes, that's what I meant.

It shows an error from the remote fd:

Connection from unknown Director bacula-dir at 109.73.166.242 rejected.

It looks like the Director > Name in the bacula-fd.conf on the remote fd does
not match the Director > Name in the bacula-dir.conf.

__Martin


> On Fri, 3 May 2019 17:20:34 +0530, preash raj said:
> 
> Hi Martin,
> 
> >> while the bacula-dir and the remote
> bacula-fd were running with these command line args?
> 
> You mean starting the bacula-dir in debug mode while I check the 'status
> client' in bconsole?
> It shows the below error while try to connect the clients using bconsole.
> the passwords looks fine, Please let me know if you have any clue on this.
> 
> ==
> Server: bacula-dir
> =
> bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=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=-Console-.2019-05-03_04.51.02_02
> bacula-dir: cram-md5.c:72-0 send: auth cram-md5 
> <1917691640.1556873462@bacula-dir> ssl=0
> bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5 
> <1594513444.1556873462@bconsole> ssl=0
> bacula-dir: cram-md5.c:150-0 sending resp to challenge: s5xs1Ct7B+/C/R+/d7+hcB
> bacula-dir: ua_status.c:142-0 status:status client:
> bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All 
> host[ipv4:103.13.242.170:9102]
> bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd 
> host=staff.hostdime.in port=9102
> bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon
> bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling
> bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100 Connection 
> from unknown Director bacula-dir at 109.73.166.242 rejected.
> bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100 
> Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
> bacula-dir: authenticate.c:218-0 cram_get_auth failed for 
> Client:staff.hostdime.in-fd
> bacula-dir: authenticate.c:222-0 Director and File daemon passwords or names 
> not the same.
> bacula-dir: bsys.c:79-0 safe_unlink unlinking: 
> /var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail
> 
> ==
> 
> 
> 
> On Fri, May 3, 2019 at 12:17 AM Martin Simmons  wrote:
> 
> > 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::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:

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-03 Thread preash raj

Hi Martin,

>> while the bacula-dir and the remote
bacula-fd were running with these command line args?

You mean starting the bacula-dir in debug mode while I check the 'status
client' in bconsole?
It shows the below error while try to connect the clients using bconsole.
the passwords looks fine, Please let me know if you have any clue on this.

==
Server: bacula-dir
=
bacula-dir: bnet.c:766-0 who=client host=127.0.0.1 port=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=-Console-.2019-05-03_04.51.02_02
bacula-dir: cram-md5.c:72-0 send: auth cram-md5
<1917691640.1556873462@bacula-dir> ssl=0
bacula-dir: cram-md5.c:131-0 cram-get received: auth cram-md5
<1594513444.1556873462@bconsole> ssl=0
bacula-dir: cram-md5.c:150-0 sending resp to challenge:
s5xs1Ct7B+/C/R+/d7+hcB
bacula-dir: ua_status.c:142-0 status:status client:
bacula-dir: bsock.c:236-0 Current host[ipv4:103.13.242.170:9102] All
host[ipv4:103.13.242.170:9102]
bacula-dir: bsock.c:157-0 who=Client: staff.hostdime.in-fd host=
staff.hostdime.in port=9102
bacula-dir: fd_cmds.c:109-0 Opened connection with File daemon
bacula-dir: authenticate.c:196-0 Sent: Hello Director bacula-dir calling
bacula-dir: cram-md5.c:131-0 cram-get received: authenticate.c:100
Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
bacula-dir: cram-md5.c:136-0 Cannot scan challenge: authenticate.c:100
Connection from unknown Director bacula-dir at 109.73.166.242 rejected.
bacula-dir: authenticate.c:218-0 cram_get_auth failed for Client:
staff.hostdime.in-fd
bacula-dir: authenticate.c:222-0 Director and File daemon passwords or
names not the same.
bacula-dir: bsys.c:79-0 safe_unlink unlinking:
/var/spool/bacula/bacula-dir.-Console-.2019-05-03_04.51.02_02.-1027011464.mail

==

On Fri, May 3, 2019 at 12:17 AM Martin Simmons  wrote:

> 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::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]

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Martin Simmons

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::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  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
> > >

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Alfred Weintoegl


Try:

netstat -lnp |grep 910
(oder ss -lntp |less -S)


...should show on the Server something like:

... your ip-addr: 9101  ...LISTEN...(bacula-dir)
... 0.0.0.0:9102 ...LISTEN... (bacula-fd)
... 0.0.0.0:9103 ...LISTEN.. .(bacula-sd)


and on the Client (at the other maschine):

... 0.0.0.0:9102 ...LISTEN...

(Listening on 0.0.0.0 means listening from anywhere)

If there is a: "127.0.0.1:9102", then you have to comment out

FDAddress = 127.0.0.1

in bacula-fd.conf  (/etc/bacula/bacula.conf)

(listening on 127.0.0.1 means only listen from this very computer).

And then:
systemctl restart bacula-fd.service


Regards
Alfred


Am 02.05.2019 um 13:47 schrieb Pieter Sybesma via Bacula-users:
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 > 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 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: -fd
 3: -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 -fd at :9102
Failed to connect to Client -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 :9103
3000 OK setdebug=100
Connecting to Client bacula-fd at localhost:9102
2000 OK setdebug=100 trace=0 hangup=0
Connecting to Client -fd at :9102
Failed to connect to Client.
Connecting to Client -fd at :9102
Failed to connect to Client.


On Thu, May 2, 2019 at 11:15 AM preash raj > 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

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread Pieter Sybesma via Bacula-users

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  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  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: -fd
>  3: -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 -fd at :9102
> Failed to connect to Client -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 :9103
> 3000 OK setdebug=100
> Connecting to Client bacula-fd at localhost:9102
> 2000 OK setdebug=100 trace=0 hangup=0
> Connecting to Client -fd at :9102
> Failed to connect to Client.
> Connecting to Client -fd at :9102
> Failed to connect to Client.
> 
> 
>> On Thu, May 2, 2019 at 11:15 AM preash raj  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::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:

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-02 Thread preash raj

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 -fd
 3: -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 -fd at :9102
Failed to connect to Client -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 :9103
3000 OK setdebug=100
Connecting to Client bacula-fd at localhost:9102
2000 OK setdebug=100 trace=0 hangup=0
Connecting to Client -fd at :9102
Failed to connect to Client.
Connecting to Client -fd at :9102
Failed to connect to Client.


On Thu, May 2, 2019 at 11:15 AM preash raj  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::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 
> 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
>> > =
>> >

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread preash raj

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::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  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
> > >

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread Martin Simmons

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

Re: [Bacula-users] Failed to connect to Client -fd

2019-05-01 Thread preash raj

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

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Dimitri Maziuk via Bacula-users

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

signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread William Muriithi

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?

Regards,
William


From: Heitor Faria 
Sent: April 30, 2019 12:35:25 PM
To: preash raj
Cc: bacula-users
Subject: Re: [Bacula-users] Failed to connect to Client -fd

Hello Preash,

I strongly recommend using the newer 9.4.x versions from the Bacula.org 
project: 
http://bacula.us/script-installation-bacula-community-9-x-official-packages/
The 5.x versions do not really have any kind of support anymore.

Regards,


From: "preash raj" 
To: "bacula-users" 
Sent: Tuesday, April 30, 2019 2:46:25 AM
Subject: [Bacula-users] Failed to connect to Client -fd

Hi,

I've installed and configured the free Bacula version 5.2.13, but I'm not able 
to establish the connection with remote client the local backup works fine. IP 
and port has been allowed in the firewall and telnet in both machines works 
fine. All the configurations are done as per the document: 
https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7

  *   OS: CentOS Linux release 7.6.1810 (Core)
  *   Bacula Version: 5.2.13

=

[root@baculaserver ~]# bconsole
Connecting to Director localhost:9101
1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
Enter a period to cancel a command.
*status client
The defined Client resources are:
 1: bacula-fd
 2: client1.hostname-fd
 3: client2.hostname-fd
Select Client (File daemon) resource (1-3): 2
Connecting to Client client1.hostname-fd at client1.hostname:9102
Failed to connect to Client client1.hostname-fd.

You have messages.
=

# tail -f /var/log/bacula/bacula.log

28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
28-Apr 23:10 bacula-dir JobId 71: End auto prune.

28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob 
"/usr/libexec/bacula/delete_catalog_backup"
29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to authenticate with File 
daemon at "client1.hostname:9102". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see 
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
 for help.

=

# vi /etc/bacula/conf.d/clients.conf

Client {
  Name = client1.hostname-fd
  Address = client1.hostname
  FDPort = 9102
  Catalog = MyCatalog
  Password = "mypassword"  # password for Remote FileDaemon
  File Retention = 30 days# 30 days
  Job Retention = 6 months# six months
  AutoPrune = yes # Prune expired Jobs/Files
}

Job {
  Name = "Backupclient1.hostname"
  JobDefs = "DefaultJob"
  Client = client1.hostname-fd
  Pool = RemoteFile
  FileSet="Home and Etc"
}
=
# cat /etc/bacula/bacula-fd.conf


Director {
  Name = servername-dir
  Password = "mypassword"
}

Director {
  Name = bacula-mon
  Password = "mypassword"
  Monitor = yes
}

FileDaemon {  # this is me
  Name = client1.hostname-fd
  FDAddress = 
  FDport = 9102  # where we listen for the director
  WorkingDirectory = /var/spool/bacula
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
}

# Send all messages except skipped files back to Director
Messages {
  Name = Standard
  director = servername-dir = all, !skipped, !restored
}
=

kindly update me any solution for this, let me know if you require any further 
details.


Regards,

Preash.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

--

MSc Heitor Faria
CEO Bacula LATAM
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220
[linkedin icon]<https://www.linkedin.com/in/msc-heitor-faria-5ba51b3>


[logo]

América Latina
bacula.lat<http://bacula.lat> | bacula.com.br<http://www.bacula.com.br>





___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Heitor Faria

Hello Preash, 

I strongly recommend using the newer 9.4.x versions from the Bacula.org 
project: 
http://bacula.us/script-installation-bacula-community-9-x-official-packages/ 
The 5.x versions do not really have any kind of support anymore. 

Regards, 

> From: "preash raj" 
> To: "bacula-users" 
> Sent: Tuesday, April 30, 2019 2:46:25 AM
> Subject: [Bacula-users] Failed to connect to Client -fd

> Hi,

> I've installed and configured the free Bacula version 5.2.13, but I'm not able
> to establish the connection with remote client the local backup works fine. IP
> and port has been allowed in the firewall and telnet in both machines works
> fine. All the configurations are done as per the document: [
> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
> |
> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
> ]

> * OS: CentOS Linux release 7.6.1810 (Core)
> * Bacula Version: 5.2.13

> =

> [root@baculaserver ~]# bconsole
> Connecting to Director localhost:9101
> 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
> Enter a period to cancel a command.
> *status client
> The defined Client resources are:
> 1: bacula-fd
> 2: client1.hostname-fd
> 3: client2.hostname-fd
> Select Client (File daemon) resource (1-3): 2
> Connecting to Client client1.hostname-fd at client1.hostname:9102
> Failed to connect to Client client1.hostname-fd.
> 
> You have messages.
> =

> # tail -f /var/log/bacula/bacula.log

> 28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
> 28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
> 28-Apr 23:10 bacula-dir JobId 71: End auto prune.

> 28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
> "/usr/libexec/bacula/delete_catalog_backup"
> 29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to authenticate with File
> daemon at "client1.hostname:9102". Possible causes:
> Passwords or names not the same or
> Maximum Concurrent Jobs exceeded on the FD or
> FD networking messed up (restart daemon).
> Please see [
> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
> |
> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
> ] for help.

> =

> # vi /etc/bacula/conf.d/clients.conf

> Client {
> Name = client1.hostname-fd
> Address = client1.hostname
> FDPort = 9102
> Catalog = MyCatalog
> Password = "mypassword" # password for Remote FileDaemon
> File Retention = 30 days # 30 days
> Job Retention = 6 months # six months
> AutoPrune = yes # Prune expired Jobs/Files
> }

> Job {
> Name = "Backupclient1.hostname"
> JobDefs = "DefaultJob"
> Client = client1.hostname-fd
> Pool = RemoteFile
> FileSet="Home and Etc"
> }
> =
> # cat /etc/bacula/bacula-fd.conf

> Director {
> Name = servername-dir
> Password = "mypassword"
> }

> Director {
> Name = bacula-mon
> Password = "mypassword"
> Monitor = yes
> }

> FileDaemon { # this is me
> Name = client1.hostname-fd
> FDAddress = 
> FDport = 9102 # where we listen for the director
> WorkingDirectory = /var/spool/bacula
> Pid Directory = /var/run
> Maximum Concurrent Jobs = 20
> }

> # Send all messages except skipped files back to Director
> Messages {
> Name = Standard
> director = servername-dir = all, !skipped, !restored
> }
> =

> kindly update me any solution for this, let me know if you require any further
> details.

> Regards,

> Preash.

> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 

MSc Heitor Faria 
CEO Bacula LATAM 
mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ] 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Martin Simmons

Sorry, I don't know what other command line arguments your system needs.

Use

ps -efww | grep bacula

to find the command lines for the current processes and add -f -d 100 to the
end.

__Martin

> On Tue, 30 Apr 2019 19:04:55 +0530, preash raj said:
> 
> Hi Martin,
> 
> >> You could try running the director and remote client with debug level
> 100 to
> print more information (add the command line arguments -f -d 100).
> 
> Could you please let me know the exact full command for a debug run?
> 
> On Tue, Apr 30, 2019 at 6:42 PM preash raj  wrote:
> 
> > Sure! will do.
> >
> > On Tue, Apr 30, 2019 at 6:39 PM Martin Simmons 
> > wrote:
> >
> >> Please CC bacula-users with replies.
> >>
> >> __Martin
> >>
> >>
> >> > On Tue, 30 Apr 2019 18:35:38 +0530, preash raj said:
> >> >
> >> > Hi Martin,
> >> >
> >> > thank you for the quick response! the bacula client version is  5.0.0,
> >> I'll
> >> > try to debug as you specified and will update you soon.
> >> >
> >> > Regards,
> >> > Preash
> >> >
> >> >
> >> > On Tue, Apr 30, 2019 at 5:41 PM Martin Simmons 
> >> wrote:
> >> >
> >> > > > On Tue, 30 Apr 2019 11:16:25 +0530, preash raj said:
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > I've installed and configured the free Bacula version 5.2.13, but
> >> I'm not
> >> > > > able to establish the connection with remote client the local backup
> >> > > works
> >> > > > fine. IP and port has been allowed in the firewall and telnet in
> >> both
> >> > > > machines works fine. All the configurations are done as per the
> >> document:
> >> > > >
> >> > >
> >> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
> >> > > >
> >> > > >- OS: CentOS Linux release 7.6.1810 (Core)
> >> > > >- Bacula Version: 5.2.13
> >> > > >
> >> > > > =
> >> > > >
> >> > > > [root@baculaserver ~]# bconsole
> >> > > > Connecting to Director localhost:9101
> >> > > > 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
> >> > > > Enter a period to cancel a command.
> >> > > > *status client
> >> > > > The defined Client resources are:
> >> > > >  1: bacula-fd
> >> > > >  2: client1.hostname-fd
> >> > > >  3: client2.hostname-fd
> >> > > > Select Client (File daemon) resource (1-3): 2
> >> > > > Connecting to Client client1.hostname-fd at client1.hostname:9102
> >> > > > Failed to connect to Client client1.hostname-fd.
> >> > > > 
> >> > > > You have messages.
> >> > > > =
> >> > > >
> >> > > > # tail -f /var/log/bacula/bacula.log
> >> > > >
> >> > > > 28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
> >> > > > 28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
> >> > > > 28-Apr 23:10 bacula-dir JobId 71: End auto prune.
> >> > > >
> >> > > > 28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
> >> > > > "/usr/libexec/bacula/delete_catalog_backup"
> >> > > > 29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to
> >> authenticate with
> >> > > > File daemon at "client1.hostname:9102". Possible causes:
> >> > > > Passwords or names not the same or
> >> > > > Maximum Concurrent Jobs exceeded on the FD or
> >> > > > FD networking messed up (restart daemon).
> >> > > > Please see
> >> > > >
> >> > >
> >> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
> >> > > > for help.
> >> > >
> >> > > Is the remote client also running Bacula version 5.2.13?  If not,
> >> which
> >> > > version?
> >> > >
> >> > > You could try running the director and remote client with debug level
> >> 100
> >> > > to
> >> > > print more information (add the command line arguments -f -d 100).
> >> > >
> >> > > __Martin
> >> > >
> >> >
> >>
> >
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread preash raj

Hi Martin,

>> You could try running the director and remote client with debug level
100 to
print more information (add the command line arguments -f -d 100).

Could you please let me know the exact full command for a debug run?

On Tue, Apr 30, 2019 at 6:42 PM preash raj  wrote:

> Sure! will do.
>
> On Tue, Apr 30, 2019 at 6:39 PM Martin Simmons 
> wrote:
>
>> Please CC bacula-users with replies.
>>
>> __Martin
>>
>>
>> > On Tue, 30 Apr 2019 18:35:38 +0530, preash raj said:
>> >
>> > Hi Martin,
>> >
>> > thank you for the quick response! the bacula client version is  5.0.0,
>> I'll
>> > try to debug as you specified and will update you soon.
>> >
>> > Regards,
>> > Preash
>> >
>> >
>> > On Tue, Apr 30, 2019 at 5:41 PM Martin Simmons 
>> wrote:
>> >
>> > > > On Tue, 30 Apr 2019 11:16:25 +0530, preash raj said:
>> > > >
>> > > > Hi,
>> > > >
>> > > > I've installed and configured the free Bacula version 5.2.13, but
>> I'm not
>> > > > able to establish the connection with remote client the local backup
>> > > works
>> > > > fine. IP and port has been allowed in the firewall and telnet in
>> both
>> > > > machines works fine. All the configurations are done as per the
>> document:
>> > > >
>> > >
>> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
>> > > >
>> > > >- OS: CentOS Linux release 7.6.1810 (Core)
>> > > >- Bacula Version: 5.2.13
>> > > >
>> > > > =
>> > > >
>> > > > [root@baculaserver ~]# bconsole
>> > > > Connecting to Director localhost:9101
>> > > > 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
>> > > > Enter a period to cancel a command.
>> > > > *status client
>> > > > The defined Client resources are:
>> > > >  1: bacula-fd
>> > > >  2: client1.hostname-fd
>> > > >  3: client2.hostname-fd
>> > > > Select Client (File daemon) resource (1-3): 2
>> > > > Connecting to Client client1.hostname-fd at client1.hostname:9102
>> > > > Failed to connect to Client client1.hostname-fd.
>> > > > 
>> > > > You have messages.
>> > > > =
>> > > >
>> > > > # tail -f /var/log/bacula/bacula.log
>> > > >
>> > > > 28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
>> > > > 28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
>> > > > 28-Apr 23:10 bacula-dir JobId 71: End auto prune.
>> > > >
>> > > > 28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
>> > > > "/usr/libexec/bacula/delete_catalog_backup"
>> > > > 29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to
>> authenticate with
>> > > > File daemon at "client1.hostname:9102". Possible causes:
>> > > > Passwords or names not the same or
>> > > > Maximum Concurrent Jobs exceeded on the FD or
>> > > > FD networking messed up (restart daemon).
>> > > > Please see
>> > > >
>> > >
>> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
>> > > > for help.
>> > >
>> > > Is the remote client also running Bacula version 5.2.13?  If not,
>> which
>> > > version?
>> > >
>> > > You could try running the director and remote client with debug level
>> 100
>> > > to
>> > > print more information (add the command line arguments -f -d 100).
>> > >
>> > > __Martin
>> > >
>> >
>>
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

2019-04-30 Thread Martin Simmons

> On Tue, 30 Apr 2019 11:16:25 +0530, preash raj said:
> 
> Hi,
> 
> I've installed and configured the free Bacula version 5.2.13, but I'm not
> able to establish the connection with remote client the local backup works
> fine. IP and port has been allowed in the firewall and telnet in both
> machines works fine. All the configurations are done as per the document:
> https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7
> 
>- OS: CentOS Linux release 7.6.1810 (Core)
>- Bacula Version: 5.2.13
> 
> =
> 
> [root@baculaserver ~]# bconsole
> Connecting to Director localhost:9101
> 1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
> Enter a period to cancel a command.
> *status client
> The defined Client resources are:
>  1: bacula-fd
>  2: client1.hostname-fd
>  3: client2.hostname-fd
> Select Client (File daemon) resource (1-3): 2
> Connecting to Client client1.hostname-fd at client1.hostname:9102
> Failed to connect to Client client1.hostname-fd.
> 
> You have messages.
> =
> 
> # tail -f /var/log/bacula/bacula.log
> 
> 28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
> 28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
> 28-Apr 23:10 bacula-dir JobId 71: End auto prune.
> 
> 28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
> "/usr/libexec/bacula/delete_catalog_backup"
> 29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to authenticate with
> File daemon at "client1.hostname:9102". Possible causes:
> Passwords or names not the same or
> Maximum Concurrent Jobs exceeded on the FD or
> FD networking messed up (restart daemon).
> Please see
> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
> for help.

Is the remote client also running Bacula version 5.2.13?  If not, which
version?

You could try running the director and remote client with debug level 100 to
print more information (add the command line arguments -f -d 100).

__Martin


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Failed to connect to Client -fd

2019-04-29 Thread preash raj

Hi,

I've installed and configured the free Bacula version 5.2.13, but I'm not
able to establish the connection with remote client the local backup works
fine. IP and port has been allowed in the firewall and telnet in both
machines works fine. All the configurations are done as per the document:
https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7

   - OS: CentOS Linux release 7.6.1810 (Core)
   - Bacula Version: 5.2.13

=

[root@baculaserver ~]# bconsole
Connecting to Director localhost:9101
1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
Enter a period to cancel a command.
*status client
The defined Client resources are:
 1: bacula-fd
 2: client1.hostname-fd
 3: client2.hostname-fd
Select Client (File daemon) resource (1-3): 2
Connecting to Client client1.hostname-fd at client1.hostname:9102
Failed to connect to Client client1.hostname-fd.

You have messages.
=

# tail -f /var/log/bacula/bacula.log

28-Apr 23:10 bacula-dir JobId 71: Begin pruning Files.
28-Apr 23:10 bacula-dir JobId 71: No Files found to prune.
28-Apr 23:10 bacula-dir JobId 71: End auto prune.

28-Apr 23:10 bacula-dir JobId 71: shell command: run AfterJob
"/usr/libexec/bacula/delete_catalog_backup"
29-Apr 07:49 bacula-dir JobId 0: Fatal error: Unable to authenticate with
File daemon at "client1.hostname:9102". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026
for help.

=

# vi /etc/bacula/conf.d/clients.conf

Client {
  Name = client1.hostname-fd
  Address = client1.hostname
  FDPort = 9102
  Catalog = MyCatalog
  Password = "mypassword"  # password for Remote FileDaemon
  File Retention = 30 days# 30 days
  Job Retention = 6 months# six months
  AutoPrune = yes # Prune expired Jobs/Files
}

Job {
  Name = "Backupclient1.hostname"
  JobDefs = "DefaultJob"
  Client = client1.hostname-fd
  Pool = RemoteFile
  FileSet="Home and Etc"
}
=
# cat /etc/bacula/bacula-fd.conf


Director {
  Name = servername-dir
  Password = "mypassword"
}

Director {
  Name = bacula-mon
  Password = "mypassword"
  Monitor = yes
}

FileDaemon {  # this is me
  Name = client1.hostname-fd
  FDAddress = 
  FDport = 9102  # where we listen for the director
  WorkingDirectory = /var/spool/bacula
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
}

# Send all messages except skipped files back to Director
Messages {
  Name = Standard
  director = servername-dir = all, !skipped, !restored
}
=

kindly update me any solution for this, let me know if you require any
further details.


Regards,

Preash.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

Re: [Bacula-users] Failed to connect to Client -fd

[Bacula-users] Failed to connect to Client -fd

18 matches

Site Navigation

Mail list logo

Footer information