Re: [Bacula-users] Failed to connect to Client -fd
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
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]
[logo]
América Latina
bacula.lat | 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
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
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
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
> 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] bacula and SQLite
On Monday 2019-04-29 14:36:07 Dimitri Maziuk via Bacula-users wrote: > On 4/29/19 1:57 PM, Josip Deanovic wrote: > > Because of the reasons Kern already wrote. > > Yes, but they have nothing to do with the question. It does. It implies that it is not supported by the authors/maintainers of the Bacula and therefore such setup is not future-proof. Not that I wouldn't like to see the SQLite continue although I don't use it (I like to have as many options as possible) but if it complicates maintenance and authors/maintainers are not ready to continue it, I don't see any other option but discontinue as it would only hurt people who try to use it and rely on it in the future while the support breaks again and there will be nobody to fix it (the last good people from Debian jumped in and made it work again). Maybe an effort is needed to help people to move from the SQLite to mysql/postgres. E.g. some migration scripts or something. I am not sure if those exist already. I think somebody said that they don't exist. Regards! -- Josip Deanovic ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
