[pkg-bacula-devel] Bug#783083: Bug#783083: bacula-director-common: Bacula director has problems with kernel linux-image-3.16.0-0.bpo.4-amd64 (v3.16.7-ckt7-1~bpo70+1)

[Artur Linhart]

Hello, more detailed description of my situation and conclustions to
which I came:
    The director runs on virtual server. I have connected to bacula
director on this server with the BAT (Administration Console) from
another host. The initial connection was OK, there came the message from
the director to BAT about the successfull establishment of the
connection. But in the next second, when there are sent internally other
commands to director for populating the masks of BAT, the BAT has
frozen, waiting endlesly on the remote director.
    I have restarted the director service on the server and from this
time point the director did not start the listening port - so
    netstat -a -n -p
    shows no "bacula-director" process even if
    /etc/init.d/bacula-director status
    reports the process is running and is also wisible with the
htop/top/ps statements - the process does not open the desired port 9101
for listening, in the list of ports can be seen only the 9102 for
bacula-fd, which also runs on the server with the director.
    Even after the next restart
    /etc/init.d/bacula-director restart
    everything looks well and there are no error messages in the logs or
on the screen (I guess, I had the debug level 150 turned on), but
netstat still reports the TCP Port 9101 is not open.
    After the restart of the whole virtual machine (still with the newer
kernel) I have seen the bacula-director on TCP 9101 in netstat, but
after the connection from BAT this was the same story again and then
after the restart only of the director service the director never starts
to listen on 9101 again, even if restarted repeatedly or just shut down
and started. Only the restart of the whole virtual machine made it
possible to see the bacula-director process in netstat on TCP 9101

    If I have simply shut down the virtual machine and specified other
older kernel for the virtual machine, then the director with this old
kernel behaves correctly according to the BAT, and also the restarts
lead to correct behavior, port 9101 is always open like it should be if
the service is running.

    with best regards, Artur Linhart
   
Dne 21.4.2015 v 22:30 Geert Stappers napsal(a):
> On Tue, Apr 21, 2015 at 09:38:11PM +0200, Artur Linhart wrote:
>> Package: bacula-director-common
>> Version: 5.2.6+dfsg-9
>> Severity: normal
>>
>> The director is not able under some circumstances communicate with Bacula
>> communication console, after (service) restart it is not able to listen on the
>> specified configured port even if the service seems to be running.
> What to do to reproduce the "not able to listen"?
>
>
> Please elaborate.
>
>
>
> Groeten
> Geert Stappers