Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
Hello Justin, On 7/17/22 19:31, Justin Case wrote: I eventually removed the 9.X FD (from the Debian standard repos) from this Debian machine and installed the 13.X FD (from the Community Edition Debs). Running it manually works fine, it connects to the Director (11.x) and the backup job runs successfully. There is one thing still unclear to me: From the Debian standard repos there is still the /etc/init.d/bacula-fd script to start and stop the FD. However, the pathes in the script fit where the standard repos install the FD (/usr/sbin/bacula-fd) and its configuration (/etc/bacula/bacula-fd). Surely I can edit /etc/init.d/bacula-fd to put in where the Community Edition Debs put the FD and config. My questions is this: does a proper bacula-fd service script for /etc/init.d usually come with the Community Edition Debian Debs? (in my case it did not seem so) The good old SysV scripts are still in the source tree, but now that the debian distro (and the others) have switched to systemd, the package will no longer setup the sysv scripts. I believe that the bacula-ctl-fd/dir/sd scripts are still provided with the package, and they can be used to manage the services. Note that I would not mix systemd and scripts at the same time, but you can probably use them. Hope it helps! Best Regards, Eric All the best, J/C On 19. Jun 2022, at 14:36, Justin Case wrote: The Debian FDs are 9.x, the DIR and SD are 11.x. It is just 1 Debian FD that needs ConnectToDirector, so I guess I just need to upgrade the FD on this one host. On 19. Jun 2022, at 13:49, Josh Fisher wrote: Debs are available from the www.bacula.org website. You can build from source. I'm not sure what version is in the normal Debian repositories, but I think it must be older than 11.0. You can see the version by running bacula-fd -? from the command line. But to use the ConnectToDirector feature, you will have to upgrade to version 11.x on all clients and Director and Storage daemons. On 6/17/22 17:35, Justin Case wrote: That is the normal debian package “bacula-client”. Which other package would I use instead? On 17. Jun 2022, at 21:08, Josh Fisher wrote: You must have an old version of bacula-fd on the client. The ConnectToDirector was implemented in version 11.0. On 6/17/22 10:00, Justin Case wrote: Yes, I tried to make sense of this error message, but there is no other directive above director in this config file (see my other email, I have attached the config file there). On 17. Jun 2022, at 14:16, Josh Fisher wrote: Did you follow the error message's suggestion? "Perhaps you left the trailing brace off of the previous resource" (or A previous resource in the bacula-fd.conf file) We would need to see the entire bacula-fd.conf file in order to help. ___ 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] Q: ConnectToDirector not working as documented for FD Director directive
I eventually removed the 9.X FD (from the Debian standard repos) from this Debian machine and installed the 13.X FD (from the Community Edition Debs). Running it manually works fine, it connects to the Director (11.x) and the backup job runs successfully. There is one thing still unclear to me: From the Debian standard repos there is still the /etc/init.d/bacula-fd script to start and stop the FD. However, the pathes in the script fit where the standard repos install the FD (/usr/sbin/bacula-fd) and its configuration (/etc/bacula/bacula-fd). Surely I can edit /etc/init.d/bacula-fd to put in where the Community Edition Debs put the FD and config. My questions is this: does a proper bacula-fd service script for /etc/init.d usually come with the Community Edition Debian Debs? (in my case it did not seem so) All the best, J/C > On 19. Jun 2022, at 14:36, Justin Case wrote: > > The Debian FDs are 9.x, the DIR and SD are 11.x. > It is just 1 Debian FD that needs ConnectToDirector, so I guess I just need > to upgrade the FD on this one host. > >> On 19. Jun 2022, at 13:49, Josh Fisher wrote: >> >> Debs are available from the www.bacula.org website. You can build from >> source. I'm not sure what version is in the normal Debian repositories, but >> I think it must be older than 11.0. You can see the version by running >> bacula-fd -? from the command line. But to use the ConnectToDirector >> feature, you will have to upgrade to version 11.x on all clients and >> Director and Storage daemons. >> >> >> On 6/17/22 17:35, Justin Case wrote: >>> That is the normal debian package “bacula-client”. Which other package >>> would I use instead? >>> On 17. Jun 2022, at 21:08, Josh Fisher wrote: You must have an old version of bacula-fd on the client. The ConnectToDirector was implemented in version 11.0. On 6/17/22 10:00, Justin Case wrote: > Yes, I tried to make sense of this error message, but there is no other > directive above director in this config file (see my other email, I have > attached the config file there). > >> On 17. Jun 2022, at 14:16, Josh Fisher wrote: >> >> Did you follow the error message's suggestion? "Perhaps you left the >> trailing brace off of the previous resource" (or A previous resource >> in the bacula-fd.conf file) We would need to see the entire >> bacula-fd.conf file in order to help. >> > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
The Debian FDs are 9.x, the DIR and SD are 11.x. It is just 1 Debian FD that needs ConnectToDirector, so I guess I just need to upgrade the FD on this one host. > On 19. Jun 2022, at 13:49, Josh Fisher wrote: > > Debs are available from the www.bacula.org website. You can build from > source. I'm not sure what version is in the normal Debian repositories, but I > think it must be older than 11.0. You can see the version by running > bacula-fd -? from the command line. But to use the ConnectToDirector feature, > you will have to upgrade to version 11.x on all clients and Director and > Storage daemons. > > > On 6/17/22 17:35, Justin Case wrote: >> That is the normal debian package “bacula-client”. Which other package would >> I use instead? >> >>> On 17. Jun 2022, at 21:08, Josh Fisher wrote: >>> >>> You must have an old version of bacula-fd on the client. The >>> ConnectToDirector was implemented in version 11.0. >>> >>> >>> On 6/17/22 10:00, Justin Case wrote: Yes, I tried to make sense of this error message, but there is no other directive above director in this config file (see my other email, I have attached the config file there). > On 17. Jun 2022, at 14:16, Josh Fisher wrote: > > Did you follow the error message's suggestion? "Perhaps you left the > trailing brace off of the previous resource" (or A previous resource > in the bacula-fd.conf file) We would need to see the entire > bacula-fd.conf file in order to help. > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
Debs are available from the www.bacula.org website. You can build from source. I'm not sure what version is in the normal Debian repositories, but I think it must be older than 11.0. You can see the version by running bacula-fd -? from the command line. But to use the ConnectToDirector feature, you will have to upgrade to version 11.x on all clients and Director and Storage daemons. On 6/17/22 17:35, Justin Case wrote: That is the normal debian package “bacula-client”. Which other package would I use instead? On 17. Jun 2022, at 21:08, Josh Fisher wrote: You must have an old version of bacula-fd on the client. The ConnectToDirector was implemented in version 11.0. On 6/17/22 10:00, Justin Case wrote: Yes, I tried to make sense of this error message, but there is no other directive above director in this config file (see my other email, I have attached the config file there). On 17. Jun 2022, at 14:16, Josh Fisher wrote: Did you follow the error message's suggestion? "Perhaps you left the trailing brace off of the previous resource" (or A previous resource in the bacula-fd.conf file) We would need to see the entire bacula-fd.conf file in order to help. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
That is the normal debian package “bacula-client”. Which other package would I use instead? > On 17. Jun 2022, at 21:08, Josh Fisher wrote: > > You must have an old version of bacula-fd on the client. The > ConnectToDirector was implemented in version 11.0. > > > On 6/17/22 10:00, Justin Case wrote: >> Yes, I tried to make sense of this error message, but there is no other >> directive above director in this config file (see my other email, I have >> attached the config file there). >> >>> On 17. Jun 2022, at 14:16, Josh Fisher wrote: >>> >>> Did you follow the error message's suggestion? "Perhaps you left the >>> trailing brace off of the previous resource" (or A previous resource in >>> the bacula-fd.conf file) We would need to see the entire bacula-fd.conf >>> file in order to help. > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
You must have an old version of bacula-fd on the client. The ConnectToDirector was implemented in version 11.0. On 6/17/22 10:00, Justin Case wrote: Yes, I tried to make sense of this error message, but there is no other directive above director in this config file (see my other email, I have attached the config file there). On 17. Jun 2022, at 14:16, Josh Fisher wrote: Did you follow the error message's suggestion? "Perhaps you left the trailing brace off of the previous resource" (or A previous resource in the bacula-fd.conf file) We would need to see the entire bacula-fd.conf file in order to help. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
Yes, I tried to make sense of this error message, but there is no other directive above director in this config file (see my other email, I have attached the config file there). > On 17. Jun 2022, at 14:16, Josh Fisher wrote: > > Did you follow the error message's suggestion? "Perhaps you left the trailing > brace off of the previous resource" (or A previous resource in the > bacula-fd.conf file) We would need to see the entire bacula-fd.conf file in > order to help. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
Thanks for picking this up. This is the complete bacula-fd.conf:
# File daemon Name to
#
#
# Copyright (C) 2000-2020 Kern Sibbald
# License: BSD 2-Clause; see file LICENSE-FOSS
#
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = bacula-dir
Password = “redacted"
# DirPort = 9101
Address = bacula-dir.lan.net
ConnectToDirector = yes
ReconnectionTime = 40 min
}
#
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
#
#Director {
# Name = bacula-mon
# Password = “redacted"
# Monitor = yes
#}
#
# "Global" File daemon configuration specifications
#
FileDaemon { # this is me
Name = redacted-fd
# FDport = 9102 # where we listen for the director
WorkingDirectory = /var/lib/bacula
Pid Directory = /run/bacula
Maximum Concurrent Jobs = 20
Plugin Directory = /usr/lib/bacula
# FDAddress = 127.0.0.1
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = bacula-dir = all, !skipped, !restored
}
> On 17. Jun 2022, at 14:16, Josh Fisher wrote:
>
> Did you follow the error message's suggestion? "Perhaps you left the trailing
> brace off of the previous resource" (or A previous resource in the
> bacula-fd.conf file) We would need to see the entire bacula-fd.conf file in
> order to help.
>
> On 6/15/22 22:36, Justin Case wrote:
>> Hi there,
>>
>> I have a client behind a firewall and the director is unable to connect to
>> this client, but the client may connect to the director and to the SD.
>>
>> In the main manual is documented that one should to this:
>>
>> on the Director side in the Client directive:
>> AllowFDConnections = yes
>>
>> on the FD side in the Director directive:
>> Director {
>> Name = bacula-dir
>> Password = “redacted”
>> # DirPort = 9101
>> Address = bacula-dir.lan.net
>> ConnectToDirector = yes
>> ReconnectionTime = 40 min
>> }
>>
>> I have done this, but the bacula-fd complains:
>>
>> bacula-fd: ERROR TERMINATION at parse_conf.c:1157
>> Config error: Keyword "ConnectToDirector" not permitted in this resource.
>> Perhaps you left the trailing brace off of the previous resource.
>> : line 22, col 20 of file /etc/bacula/bacula-fd.conf
>> ConnectToDirector = yes
>>
>> Actually it would also complain about DirPort in the same way if I remove
>> the comment character.
>>
>> It looks like the documentation does not fit the behaviour of the Debian
>> bacula-client package.
>>
>> What can I do now?
>>
>> Best
>> J/C
>>
>>
>>
>> ___
>> 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
Re: [Bacula-users] Q: ConnectToDirector not working as documented for FD Director directive
Did you follow the error message's suggestion? "Perhaps you left the
trailing brace off of the previous resource" (or A previous resource
in the bacula-fd.conf file) We would need to see the entire
bacula-fd.conf file in order to help.
On 6/15/22 22:36, Justin Case wrote:
Hi there,
I have a client behind a firewall and the director is unable to connect to this
client, but the client may connect to the director and to the SD.
In the main manual is documented that one should to this:
on the Director side in the Client directive:
AllowFDConnections = yes
on the FD side in the Director directive:
Director {
Name = bacula-dir
Password = “redacted”
# DirPort = 9101
Address = bacula-dir.lan.net
ConnectToDirector = yes
ReconnectionTime = 40 min
}
I have done this, but the bacula-fd complains:
bacula-fd: ERROR TERMINATION at parse_conf.c:1157
Config error: Keyword "ConnectToDirector" not permitted in this resource.
Perhaps you left the trailing brace off of the previous resource.
: line 22, col 20 of file /etc/bacula/bacula-fd.conf
ConnectToDirector = yes
Actually it would also complain about DirPort in the same way if I remove the
comment character.
It looks like the documentation does not fit the behaviour of the Debian
bacula-client package.
What can I do now?
Best
J/C
___
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] Q: ConnectToDirector not working as documented for FD Director directive
Hi there,
I have a client behind a firewall and the director is unable to connect to this
client, but the client may connect to the director and to the SD.
In the main manual is documented that one should to this:
on the Director side in the Client directive:
AllowFDConnections = yes
on the FD side in the Director directive:
Director {
Name = bacula-dir
Password = “redacted”
# DirPort = 9101
Address = bacula-dir.lan.net
ConnectToDirector = yes
ReconnectionTime = 40 min
}
I have done this, but the bacula-fd complains:
bacula-fd: ERROR TERMINATION at parse_conf.c:1157
Config error: Keyword "ConnectToDirector" not permitted in this resource.
Perhaps you left the trailing brace off of the previous resource.
: line 22, col 20 of file /etc/bacula/bacula-fd.conf
ConnectToDirector = yes
Actually it would also complain about DirPort in the same way if I remove the
comment character.
It looks like the documentation does not fit the behaviour of the Debian
bacula-client package.
What can I do now?
Best
J/C
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
