>>> bacula returns this error message:
>>>
>>> 06-juin 14:56 Bacula-dir JobId 1569 : Warning: bsock.c:129 impossible to
>>> connect at Storage daemon on 192.168.1.15:9103. ERR=3DConnection failed
>> What happens when you telnet 192.168.1.15 9103 ? Do you get a connection?
>it works only when i
On Wed, 6 Jun 2012 18:51:27 +0400
Konstantin Khomoutov wrote:
[...]
> 2) You can connect to that socket from a non-firewalled machine
>(on the same network). You can use netcat or even telnet for this:
>$ nc 192.168.1.15 9103
>or
>$ telnet 192.168.1.15 9103
>
>If you corr
Laurent MANCHON writes:
>bacula returns this error message:
>
>06-juin 14:56 Bacula-dir JobId 1569 : Warning: bsock.c:129 impossible to
>connect at Storage daemon on 192.168.1.15:9103. ERR=Connection failed
>
>i think i have a problem with my iptables rules but i don't know where,
>i need someb
On Wed, 06 Jun 2012 16:16:32 +0200
Laurent MANCHON wrote:
> --hi,
>
> bacula returns this error message:
>
> 06-juin 14:56 Bacula-dir JobId 1569 : Warning: bsock.c:129 impossible
> to connect at Storage daemon on 192.168.1.15:9103. ERR=Connection
> failed
>
> i think i have a problem with my i
--hi,
bacula returns this error message:
06-juin 14:56 Bacula-dir JobId 1569 : Warning: bsock.c:129 impossible to
connect at Storage daemon on 192.168.1.15:9103. ERR=Connection failed
i think i have a problem with my iptables rules but i don't know where,
i need somebody help to resolve this p
