Re: [Bacula-users] Baculum error Status SD Remote

2019-12-02 Thread Marcin Haba
Hello Jose, Thanks for providing those outputs. I was able to reproduce the issue. It is a bug. It will be fixed in the new release. Thanks for reporting this problem here. This way Baculum becomes better. Best regards, Marcin Haba (gani) On Mon, 2 Dec 2019 at 16:12, Jose Alberto wrote: > > s

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Josh Fisher
On 12/2/2019 11:46 AM, Mac wrote: Hi Josh Thank you for your suggestion This vm is a web server and all sites use remote DNS - everything else is working as expected. interfaces - is all correct. So I do not this is an ip address issue. Then are there iptables rules on the VM blocking

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Martin Simmons
Sorry, I meant 9102 of course: nc -l ...ip.address... 9102 __Martin > On Mon, 2 Dec 2019 17:18:36 GMT, Martin Simmons said: > > You could check if nc can bind it: > > nc -l ...ip.address... 10243 > > That gives the "Cannot assign requested address" error for me if the ip > address is not

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Martin Simmons
You could check if nc can bind it: nc -l ...ip.address... 10243 That gives the "Cannot assign requested address" error for me if the ip address is not local. Also, if selinux is enabled then maybe that is blocking it? __Martin > On Mon, 2 Dec 2019 17:02:19 + (GMT), Mac said: > > Hi

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Mac
Hi Martin Thank you for your reply It is setup to use an ip address I have Webmin running on this vm and those ports are working as expected Everything else seems to be working as expected websites ,mail etc. Kind Regards Brad - Original Message - step 3.: "Martin Simmons" To: "Ma

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Mac
Hi Josh Thank you for your suggestion This vm is a web server and all sites use remote DNS - everything else is working as expected. interfaces - is all correct. So I do not this is an ip address issue. Jose This is an unmanaged vps from a host - I have two vps's from them and the oth

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Martin Simmons
If it works with the ip address hardwired to localhost, then I strongly suspect some misconfiguration of the ip address (or name lookup if you configured it as a name). The segv is caused by the "Cannot bind port" error so I don't think the btrackback will be useful afterall. __Martin > On

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Josh Fisher
On 12/2/2019 7:49 AM, Mac wrote: Hi Martin Thank you for your reply and suggestion. Yes I do have the ip address hardwired - No it has not changed. Does 'ip addr show' show that that IP address is bound to the (correct) interface? The vm configuration is also not unique and I have

Re: [Bacula-users] Baculum error Status SD Remote

2019-12-02 Thread Jose Alberto
show storage=MSL4048 Autochanger: name=MSL4048 address=10.30.2.5 SDport=9103 MaxJobs=4 NumJobs=0 DeviceName=Hp4048 MediaType=LTO5 StorageId=6 Autochanger=1 AC group=6 ShareStore=*none* bsdjson -r Autochanger [ { "Autochanger": { "Name": "Hp6000", "Device": ["Drive-4", "Drive-

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Jose Alberto
If nothing has been modified in the operating system. What last changes do they have? and the hypervisor something they ran? On Mon, Dec 2, 2019 at 7:14 AM Mac wrote: > Hi there > > I have a client on a Debian 9 vm that has been working perfectly for 18 > months. > > I have just received an erro

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Mac
Hi Martin Thank you for your help. Yes the error is shown when the service is started independently of the vm Replacing the hardwired ip with localhost - allows the service to start without error. This is the content of the .traceback file * /usr/sbin/btraceback: 60: /usr/sbin/btr

Re: [Bacula-users] SD fails to create new volumes: trace included

2019-12-02 Thread Dan Langille
Resending. Sorry, the previous email was incomplete. On Tue, Jan 9, 2018, at 3:29 PM, Dan Langille wrote: > > On Jan 9, 2018, at 3:07 PM, Dan Langille wrote: > > > >> On Jan 9, 2018, at 3:01 PM, Dan Langille wrote: > >> > >> I wonder if this line is related: > >> > >> > >> bacula-sd-01-sd:

Re: [Bacula-users] SD fails to create new volumes: trace included

2019-12-02 Thread Dan Langille
On Tue, Jan 9, 2018, at 3:29 PM, Dan Langille wrote: > > On Jan 9, 2018, at 3:07 PM, Dan Langille wrote: > > > >> On Jan 9, 2018, at 3:01 PM, Dan Langille wrote: > >> > >> I wonder if this line is related: > >> > >> > >> bacula-sd-01-sd: mount.c:663-269534 No autolabel because polling. > >>

[Bacula-users] How to verify copy job written on cartridge ?

2019-12-02 Thread Frédéric F .
Hello, I have a problem with my verifies jobs. I backup servers in a file pool then I copy them to cartridges pool (L). I created this job : Job { Name = "Verify LTO_021app_L" JobDefs = "Verify Migration" VerifyJob = "Backup L_021app" *(The backup job)* Schedule = "Verif-Full-

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Martin Simmons
Does it fail with the "Cannot bind port 9102: ERR=Cannot assign requested address" message if you start the bacula-fd.service manually when the vm is running? Try removing the hardwired ip address if you can to see if that makes a difference. Also, the look for "*.traceback" files in the bacula-f

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Mac
Hi Martin Thank you for your reply and suggestion. Yes I do have the ip address hardwired - No it has not changed. The vm configuration is also not unique and I have a few other vm all configured the same way who's Bacula clients are all working as expected. Anything else I can look at?

Re: [Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Martin Simmons
> On Mon, 2 Dec 2019 10:52:56 + (GMT), Mac said: > > Hi there > > I have a client on a Debian 9 vm that has been working perfectly for 18 > months. > > I have just received an error on bconsole that the scheduled backup failed. > > I have done all the standard operations including

[Bacula-users] Sudden error on Bacula client 7.4.4

2019-12-02 Thread Mac
Hi there I have a client on a Debian 9 vm that has been working perfectly for 18 months. I have just received an error on bconsole that the scheduled backup failed. I have done all the standard operations including full reboot of the vm. The Client come online after a restart for a short ti