Your message dated Sun, 29 May 2016 21:26:53 +0200
with message-id <[email protected]>
and subject line Re: bacula-sd: bsock.c: 135 Unable to connect to Storage
daemon on ...
has caused the Debian Bug report #613494,
regarding bacula-sd: bsock.c: 135 Unable to connect to Storage daemon on ...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
613494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613494
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bacula
Version: 5.0.2-2.2
Severity: wishlist
I got no answer if I use the command >status sto<.
Solution:
SDAdress 127.0.0.1 must be changed to FQDN in bacula-sd.conf
-- System Information:
Debian Release: 6.0
APT prefers squeeze-updates
APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bacula depends on:
ii bacula-client 5.0.2-2.2 network backup, recovery and verif
ii bacula-common 5.0.2-2.2+b1 network backup, recovery and verif
ii bacula-server 5.0.2-2.2 network backup, recovery and verif
bacula recommends no packages.
Versions of packages bacula suggests:
pn bacula-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.0.5+dfsg-4
Dear Helmut,
thank you for your bug report, and please excuse the long delay before
someone answered it.
You reported on version 5.0.2-2.2:
> I got no answer if I use the command >status sto<.
>
> Solution:
> SDAdress 127.0.0.1 must be changed to FQDN in bacula-sd.conf
For security reasons, the daemons are configured to listen only on
127.0.0.1. Since at least version 7.0.5+dfsg-4 this works after a
default installation. It probably already worked in 5.2.6.
For more complex setups, especially involving more than one host, the
administrator needs to do the configuration herself.
Carsten
--- End Message ---
