Martin Simmons wrote:
> > On Thu, 19 Apr 2018 17:05:33 +, Steve Garcia said:
> >
> > Martin Simmons wrote:
> > >
> > > The director sends the address (in bacula-dir.conf) of the storage daemon
> > > to
> > > the client, which
> On Thu, 19 Apr 2018 17:05:33 +, Steve Garcia said:
>
> Martin Simmons wrote:
> >
> > The director sends the address (in bacula-dir.conf) of the storage daemon to
> > the client, which then makes its own connection to the storage daemon.
> > There
> > is a
On 4/19/2018 11:27 AM, Martin Simmons wrote:
... public ip for localhost ...
I've often wondered: is there a good reason for doing that in the hosts file?
Last I heard linux kernel was supposed to figure it out and route
connections to self locally regardless of the ip. IOW no, and bacula is
Steve Garcia
Ignorance killed the cat, curiosity was framed.
Martin Simmons wrote:
> > On Tue, 17 Apr 2018 17:53:12 +, Steve Garcia said:
> >
> > OK, in the process of writing out the details of my connection problem for
> > this list, I solved my problem,
> On Tue, 17 Apr 2018 17:53:12 +, Steve Garcia said:
>
> OK, in the process of writing out the details of my connection problem for
> this list, I solved my problem, but I thought I'd document it here.
>
> The problem was that all of a sudden my backups started failing with a
>
Hello,
2018-04-17 19:53 GMT+02:00 Steve Garcia :
>
> And it seems that the storage daemon isn't listening on the localhost
> interface. This is a configuration directive, but the comments in the
> default config file, on Debian at least, say "Do not use localhost here."
> So
OK, in the process of writing out the details of my connection problem for this
list, I solved my problem, but I thought I'd document it here.
The problem was that all of a sudden my backups started failing with a
Warning: bsock.c:107 Could not connect to Storage daemon on