Dennis Sweben [23.03.2017 11:03]:
> Hi Werner,
> “I'm not sure, but do you reach the client at all? Is xinetd running, is
> /etc/xinetd.d/check_mk active?”
> 
> I can’t even get it to run on the client iself ☺

How that? AFAIK all checks are run via xinetd. xinetd listens at port
6556, and a "telnet localhost 6556" should show you the agent's output,
if /etc/xinetd.d/check_mk has the correct data.

If this does not happen:

# rcxinetd status
Checking for service xinetd:           running

if not: # rcxinetd start

if xinetd doesn't run, look at the logs why it won't start. As a test,
you can enable the services "daytime" and "time", it should start then.
Best use YaST for that :)

BTW, my /etc/xinetd.d/check_mk contains a commentary and
---snip----
service check_mk
{
        type           = UNLISTED
        port           = 6556
        socket_type    = stream
        protocol       = tcp
        wait           = no
        user           = root
        server         = /usr/bin/check_mk_agent

        # If you use fully redundant monitoring and poll the client
        # from more then one monitoring servers in parallel you might
        # want to use the agent cache wrapper:
        #server         = /usr/bin/check_mk_caching_agent

        # configure the IP address(es) of your Nagios server here:
        #only_from      = 127.0.0.1 10.0.20.1 10.0.20.2

        # Don't be too verbose. Don't log every check. This might be
        # commented out for debugging. If this option is commented out
        # the default options will be used for this service.
        log_on_success =

        disable        = no
}
---pins---

If there are missing dependencies for check_mk, a check_mk-agent
installation from the repo I mentionend in the last post might cure that ;)

Werner

-- 


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
omd-users mailing list
[email protected]
http://lists.mathias-kettner.de/mailman/listinfo/omd-users

Reply via email to