:-) At first I thought you were trolling me a little, but then I looked and
sure enough, my Director has died.
How can I find out what happened?
Thanks,
Shon
On Mon, Jun 10, 2013 at 2:06 PM, Radosław Korzeniewski <
rados...@korzeniewski.net> wrote:
> Hello,
>
> 2013/6/10 Mingus Dew <shon.steph...@gmail.com>
>
>> Dear All,
>> I'm having an issue with bconsole not being able to connect to the
>> Director
>>
>> bconsole[18490]: [ID 702911 daemon.error] bsock.c:138 Unable to connect
>> to Director daemon on mt-back4.mentora.:9101. ERR=Connection refused
>>
>> I *think* what has happened is that so many jobs are in queue that I've
>> exceeded the number of connections the Directory allows? This actually
>> happened to me a couple weeks ago after an incredibly large backup job
>> backed up the queue.
>>
>> I was wondering how to more accurately troubleshoot this, if I can
>> recover without killing, etc...
>>
>> PLEASE - do not respond about authentication, etc... This is not an
>> authentication issue.
>>
>
> Yes, you are right. It is not an authorization issue, because the error
> is: "ERR=Connection refused". :)
>
> There is no Bacula Director listening at: mt-back4.mentora.:9101. Check it.
>
> best regards
> --
> Radosław Korzeniewski
> rados...@korzeniewski.net
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
