Hello Marco,
Thanks for your answer.
I checked right away, and indeed: it is Nagios (run by check_mk)
checking the port.
Is there maybe something that Nagios on can send on the port which
returns something more or less static (like a http check) ? That way we
can still monitor bareos-{dir,fd,sd) over the network.
Otherwise, we can do something like described on
http://confluence.wartungsfenster.de/display/Adminspace/Check_MK+and+Bacula
, if that would also apply to bareos...
Best,
Arjen.
On 2016-01-27 15:05, Marco van Wieringen wrote:
On 01/26/16 09:10 AM, Arjen Van Drie wrote:
Hi list,
since yesterday I get in the logs:
26-Jan 09:57 backuptest01-dir: ERROR in socket_server.c:56 Connection request
from client failed.
every minute.
I see from a tcpdump that the client is one specific host, but when I capture
full packets they don't tell me much about what exactly is going on.
Thanks for pointing me in the right direction,
Looking at the code at that line it prints that if the recv() call returns 0 or
less e.g.
receive error on the socket. Maybe some monitoring is probing things and
creates a
socket and directly closes it. I would guess its some security test run in your
network
or some wrongly configured monitoring system. You could add a tcp wrapper rule
dropping
that particular host but that would mean you get it dropped earlier but still
being logged.
I think the better solution is to figure out what device is doing that in your
network
and get it to stop doing it.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
