[Check_mk (english)] OMD distributed monitoring

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak it to your needs (at least port, user, server and server_args). After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!

Book your place now and be part of it.

October 18th-20th, 2015

http://mathias-kettner.de/conference

I did that, but now I have another error:

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

This is from OMD:

service livestatus

{

type = UNLISTED

socket_type = stream

protocol = tcp

port = 6557

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagiosadmin

server = /usr/bin/unixcat

server_args = /usr/local/nagios/var/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 172.16.212.9

----------------------------------------------------------

These parameters are handled and affected by OMD

Do not change anything beyond this point.

Disabling is done via omd config set LIVESTATUS_TCP [on/off].

Do not change this:

disable = no

TCP port number. Can be configure via LIVESTATUS_TCP_PORT

port = 6557

Paths and users. Manual changes here will break some omd

commands such as ‘cp’, ‘mv’ and ‘update’. Do not toutch!

user = monitoring

server = /omd/sites/monitoring/bin/unixcat

server_args = /omd/sites/monitoring/tmp/run/live

----------------------------------------------------------

}

This is from Nagios before i coppied it from OMD:

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = omdadmin

server = /usr/bin/unixcat

server_args = /var/lib/nagios/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

disable = no

}

···

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak it to your needs (at least port, user, server and server_args).
After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server
multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.de/conference

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

···

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:06 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

I did that, but now I have another error:

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

This is from OMD:

service livestatus

{

type = UNLISTED

socket_type = stream

protocol = tcp

port = 6557

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagiosadmin

server = /usr/bin/unixcat

server_args = /usr/local/nagios/var/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 172.16.212.9

----------------------------------------------------------

These parameters are handled and affected by OMD

Do not change anything beyond this point.

Disabling is done via omd config set LIVESTATUS_TCP [on/off].

Do not change this:

disable = no

TCP port number. Can be configure via LIVESTATUS_TCP_PORT

port = 6557

Paths and users. Manual changes here will break some omd

commands such as ‘cp’, ‘mv’ and ‘update’. Do not toutch!

user = monitoring

server = /omd/sites/monitoring/bin/unixcat

server_args = /omd/sites/monitoring/tmp/run/live

----------------------------------------------------------

}

This is from Nagios before i coppied it from OMD:

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = omdadmin

server = /usr/bin/unixcat

server_args = /var/lib/nagios/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

disable = no

}

~

~

And now it is the same as on OMD with error I mentioned in first sentence in this post…

I can’t find what’s wrong, probably those parameters you mentioned: server, server_args or user…

Kind regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 1:55 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak it to your needs (at least port, user, server and server_args).
After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server
multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.de/conference


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

I can start from scratch if only there is some step-by-step tutorial, but nowhere is mentioned what i actually need to install and
configure on remote site Nagios server.

All instructions are just simple change in OMD server configuration and everything works like a charm…

Regards,

Stjepan

···

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:14 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

From:
checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:06 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

I did that, but now I have another error:

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

This is from OMD:

service livestatus

{

type = UNLISTED

socket_type = stream

protocol = tcp

port = 6557

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagiosadmin

server = /usr/bin/unixcat

server_args = /usr/local/nagios/var/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 172.16.212.9

----------------------------------------------------------

These parameters are handled and affected by OMD

Do not change anything beyond this point.

Disabling is done via omd config set LIVESTATUS_TCP [on/off].

Do not change this:

disable = no

TCP port number. Can be configure via LIVESTATUS_TCP_PORT

port = 6557

Paths and users. Manual changes here will break some omd

commands such as ‘cp’, ‘mv’ and ‘update’. Do not toutch!

user = monitoring

server = /omd/sites/monitoring/bin/unixcat

server_args = /omd/sites/monitoring/tmp/run/live

----------------------------------------------------------

}

This is from Nagios before i coppied it from OMD:

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = omdadmin

server = /usr/bin/unixcat

server_args = /var/lib/nagios/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

disable = no

}

~

~

And now it is the same as on OMD with error I mentioned in first sentence in this post…

I can’t find what’s wrong, probably those parameters you mentioned: server, server_args or user…

Kind regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 1:55 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak it to your needs (at least port, user, server and server_args).
After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server
multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.de/conference


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:06 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de

Subject: Re: [Check_mk (english)] OMD distributed monitoring

I did that, but now I have another error:

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

This is from OMD:

service livestatus

{

    type            = UNLISTED
    socket_type     = stream
    protocol        = tcp
    port            = 6557
    wait            = no
    # limit to 100 connections per second. Disable 3 secs if above.
    cps             = 100 3
    # set the number of maximum allowed parallel instances of unixcat.
    # Please make sure that this values is at least as high as
    # the number of threads defined with num_client_threads in
    # etc/mk-livestatus/nagios.cfg
    instances       = 500
    # limit the maximum number of simultaneous connections from
    # one source IP address
    per_source      = 250
    # Disable TCP delay, makes connection more responsive
    flags           = NODELAY
    user            = nagiosadmin
    server          = /usr/bin/unixcat
    server_args     = /usr/local/nagios/var/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 172.16.212.9

----------------------------------------------------------

These parameters are handled and affected by OMD

Do not change anything beyond this point.

Disabling is done via omd config set LIVESTATUS_TCP [on/off].

Do not change this:

    disable         = no

TCP port number. Can be configure via LIVESTATUS_TCP_PORT

    port            = 6557

Paths and users. Manual changes here will break some omd

commands such as ‘cp’, ‘mv’ and ‘update’. Do not toutch!

    user            = monitoring
    server          = /omd/sites/monitoring/bin/unixcat
    server_args     = /omd/sites/monitoring/tmp/run/live

----------------------------------------------------------

}

This is from Nagios before i coppied it from OMD:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = omdadmin
    server          = /usr/bin/unixcat
    server_args     = /var/lib/nagios/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

    disable         = no

}

~

~

And now it is the same as on OMD with error I mentioned in first sentence in this post…

I can’t find what’s wrong, probably those parameters you mentioned: server, server_args or user…

Kind regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 1:55 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak it to your needs (at least port, user, server and server_args).
After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server
multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.de/conference


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

From:
checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:06 PM
To: Marcel Schulte;
checkmk-en@lists.mathias-kettner.de

Subject: Re: [Check_mk (english)] OMD distributed monitoring

I did that, but now I have another error:

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

This is from OMD:

service livestatus

{

    type            = UNLISTED
    socket_type     = stream
    protocol        = tcp
    port            = 6557
    wait            = no
    # limit to 100 connections per second. Disable 3 secs if above.
    cps             = 100 3
    # set the number of maximum allowed parallel instances of unixcat.
    # Please make sure that this values is at least as high as
    # the number of threads defined with num_client_threads in
    # etc/mk-livestatus/nagios.cfg
    instances       = 500
    # limit the maximum number of simultaneous connections from
    # one source IP address
    per_source      = 250
    # Disable TCP delay, makes connection more responsive
    flags           = NODELAY
    user            = nagiosadmin
    server          = /usr/bin/unixcat
    server_args     = /usr/local/nagios/var/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 172.16.212.9

----------------------------------------------------------

These parameters are handled and affected by OMD

Do not change anything beyond this point.

Disabling is done via omd config set LIVESTATUS_TCP [on/off].

Do not change this:

    disable         = no

TCP port number. Can be configure via LIVESTATUS_TCP_PORT

    port            = 6557

Paths and users. Manual changes here will break some omd

commands such as ‘cp’, ‘mv’ and ‘update’. Do not toutch!

    user            = monitoring
    server          = /omd/sites/monitoring/bin/unixcat
    server_args     = /omd/sites/monitoring/tmp/run/live

----------------------------------------------------------

}

This is from Nagios before i coppied it from OMD:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = omdadmin
    server          = /usr/bin/unixcat
    server_args     = /var/lib/nagios/rw/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

    disable         = no

}

~

~

And now it is the same as on OMD with error I mentioned in first sentence in this post…

I can’t find what’s wrong, probably those parameters you mentioned: server, server_args or user…

Kind regards,

Stjepan

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 1:55 PM
To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Hi Stjepan,

I guess you don’t have livestatus configured in xinetd on Nagios server, do you?

You can take the content of (on your OMD server) ~/etc/mk-livestatus/xinetd.conf, paste it to a xinetd conf file on your Nagios server (e.g. /etc/xinted.d/livestatus) and tweak
it to your needs (at least port, user, server and server_args). After a xinetd restart the connection to livestatus should work - as long as there are no other stones on your network way, e.g. lokal or network firewalls, routing, whatever…

HTH,

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 12:11 Uhr:

Hello,

I am having trouble setting up OMD Distributed monitoring multisite.

On one server I have clean instalation of OMD, on other server I have Nagios instalation with couple of devices being monitored.

What do I need to set up or install on Nagios Server for Distributed monitoring to work?!

What do I need to set up or install on OMD Server for Distributed monitoring to work?!

I did everything from OMD side (enable distributed monitoring, set up TCP port towards Nagios server IP address and port 6557, but every time get error:

Nagios server - Livestatus error

Cannot connect to ‘tcp:ipaddress_of_host:6557’: [Errno 103] Software caused connection abort

I am trying to make this work for couple of weeks, been installing check_mk, livestatus, etc. But nothing helps, every time sam error and no second nagios hosts in OMD.

Checking for TCP connection between OMD and Nagios host works just fine, I have tested it.

This is configuration part on OMD server
multisite.mk

sites = {

connect to local Nagios

“monitoring” : {

“alias” : “monitoring”

},

connect to remote site

“scnag”: {

“alias”: “Nagios Server”,

“socket”: “tcp: ipaddress_of_host:6557”,

“url_prefix”: “http:// ipaddress_of_host /”,

},

}

Regards,

Stjepan


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim.
Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite
posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.de/conference


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim.
Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite
posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Now I have

broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/lib/nagios/mk-livestatus/live

in nagios.cfg, and

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = sysadmin

server = /usr/lib/nagios

server_args = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

disable = no

}

In /etc/xinetd.d/livestatus on Nagios server.

Now I get different error, which is certainly step forward. Error is:

Livestatus error

[Errno 104] Connection reset by peer

Regards,

Stjepan

···

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:48 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 2:27 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

Maybe your user param is still wrong… What about the livestatus socket owner?

ls - l /usr/lib/nagios/mk-livestatus/live

Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:01:

Now I have

broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/lib/nagios/mk-livestatus/live

in nagios.cfg, and

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = sysadmin
    server          = /usr/lib/nagios
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

    disable         = no

}

In /etc/xinetd.d/livestatus on Nagios server.

Now I get different error, which is certainly step forward. Error is:

Livestatus error

[Errno 104] Connection reset by peer

Regards,

Stjepan

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:48 PM

To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 2:27 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Also, this is my active connection… I don’t know if this is right:

Nagios server:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name Timer

tcp 0 0 0.0.0.0:6557 0.0.0.0:*
LISTEN 9043/xinetd off (0.00/0/0)

···

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:48 PM
To: Marcel Schulte; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 2:27 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

Will try another user.

root@scnag:~# ls -l /usr/lib/nagios/mk-livestatus/live

total 0

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:01:

Now I have

broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/lib/nagios/mk-livestatus/live

in nagios.cfg, and

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = sysadmin
    server          = /usr/lib/nagios
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

    disable         = no

}

In /etc/xinetd.d/livestatus on Nagios server.

Now I get different error, which is certainly step forward. Error is:

Livestatus error

[Errno 104] Connection reset by peer

Regards,

Stjepan

From:
checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:48 PM

To: Marcel Schulte;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 2:27 PM
To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:11:

Will try another user.

root@scnag:~# ls -l /usr/lib/nagios/mk-livestatus/live

total 0

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:09 PM

To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Maybe your user param is still wrong… What about the livestatus socket owner?

ls - l /usr/lib/nagios/mk-livestatus/live

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:01:

Now I have

broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/lib/nagios/mk-livestatus/live

in nagios.cfg, and

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = sysadmin
    server          = /usr/lib/nagios
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44

    disable         = no

}

In /etc/xinetd.d/livestatus on Nagios server.

Now I get different error, which is certainly step forward. Error is:

Livestatus error

[Errno 104] Connection reset by peer

Regards,

Stjepan

From:
checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Stjepan Vučić
Sent: Thursday, May 28, 2015 2:48 PM

To: Marcel Schulte;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

root@scnag:~# ls -l /usr/local/nagios/var/rw/live

total 0

root@scnag:~# echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live: Connection refused.

It seems something is not installed correctly on livestatus on Nagios server

Regards,

Stjepan

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 2:27 PM
To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Which Nagios version is your Nagios server using? On Nagios server do a “ls -l /usr/local/nagios/var/rw/live” and the owner should be the user param for xinetd. Restart xinetd after reconfiguration.

If it still fails try this as livestatus user (remember the param from above) in Nagios server terminal:

echo -e “GET hosts\n” | /usr/bin/unixcat /usr/local/nagios/var/rw/live

HTH,
Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 14:14:

Maybe I need to patch Nagios for livestatus to work?

I got information that it might be the case, I don’t know…

Regards,

Stjepan

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

disable = no

}

Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

···

From: Stjepan Vučić
Sent: Thursday, May 28, 2015 3:29 PM
To: ‘Marcel Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

limit to 100 connections per second. Disable 3 secs if above.

cps = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

instances = 500

limit the maximum number of simultaneous connections from

one source IP address

per_source = 250

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

disable = no

}

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

server_args param must be your livestatus socket. You must find that socket yourself, nobody can know where yours can be found. As far as I remember you posted some mails ago not to have /usr/lib/nagios/mk-livestatus/live so this is wrong configuration for server_args.

All these problems (“I cannot find this or that”, “my files have wrong permissions” etc.) are the reasons why we have OMD - only right permissions, everyone has same locations, no crappy configuration…

Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:31: > Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

From: Stjepan Vučić

Sent: Thursday, May 28, 2015 3:29 PM

To: ‘Marcel Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

    disable         = no

}

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM

To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Well, I am following this tutorial, and it says:

After setting up Livestatus and restarting Nagios, two things should happen:

The socket file is created. (Check by navigating to /usr/local/nagios/var/rw. The socket file live should have been created.)

I have created that file because I can find it on my server, it was created during setup.

I put that path to server_args and to nagios.cfg.

I get this error now:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live/: Connection refused.

Can you tell where or what could be the cause of connection refused?

I am no table to have OMD on this server, unfortunatelly. This server has a loto f hosts and services, and I just need to connect it
to my OMD on a remote server.

I would be the happiest personi n the world if this would work, the instructions seem to be so simple, but I don’t know where is a
mistake in configuration.

Regards,

Stjepan

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:31:

Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

From: Stjepan
Vučić

Sent: Thursday,
May 28, 2015 3:29 PM

To: ‘Marcel
Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

    disable         = no

}

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM

To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

If the live socket is/was not there you cannot simply create it, it must get auto created during setup.

How did you install and setup livestatus? We need an exact(!) step-by-step report to have a clue where the fault lies.

Marcel

···

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 20:36 Uhr: > Well, I am following this tutorial, and it says:

After setting up Livestatus and restarting Nagios, two things should happen:

The socket file is created. (Check by navigating to /usr/local/nagios/var/rw. The socket file live should have been created.)

I have created that file because I can find it on my server, it was created during setup.

I put that path to server_args and to nagios.cfg.

I get this error now:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live/: Connection refused.

Can you tell where or what could be the cause of connection refused?

I am no table to have OMD on this server, unfortunatelly. This server has a loto f hosts and services, and I just need to connect it
to my OMD on a remote server.

I would be the happiest personi n the world if this would work, the instructions seem to be so simple, but I don’t know where is a
mistake in configuration.

Regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:41 PM

To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

server_args param must be your livestatus socket. You must find that socket yourself, nobody can know where yours can be found. As far as I remember you posted some mails ago not to have /usr/lib/nagios/mk-livestatus/live so this is wrong configuration for
server_args.

All these problems (“I cannot find this or that”, “my files have wrong permissions” etc.) are the reasons why we have OMD - only right permissions, everyone has same locations, no crappy configuration…

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:31: > > Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

From: Stjepan
Vučić

Sent: Thursday,
May 28, 2015 3:29 PM

To: ‘Marcel
Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

    disable         = no

}

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM

To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Marcel,

This is step by step tutorial i followed:

https://nnfailagutan.wordpress.com/2012/01/20/how-to-install-mk-livestatus-in-centos-5/

Regards,

Stjepan

···

If the live socket is/was not there you cannot simply create it, it must get auto created during setup.

How did you install and setup livestatus? We need an exact(!) step-by-step report to have a clue where the fault lies.

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 um 20:36 Uhr:

Well, I am following this tutorial, and it says:

After setting up Livestatus and restarting Nagios, two things should happen:

The socket file is created. (Check by navigating to /usr/local/nagios/var/rw. The socket file live should have been created.)

I have created that file because I can find it on my server, it was created during setup.

I put that path to server_args and to nagios.cfg.

I get this error now:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live/: Connection refused.

Can you tell where or what could be the cause of connection refused?

I am no table to have OMD on this server, unfortunatelly. This server has a loto f hosts and services,
and I just need to connect it to my OMD on a remote server.

I would be the happiest personi n the world if this would work, the instructions seem to be so simple,
but I don’t know where is a mistake in configuration.

Regards,

Stjepan

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:41 PM

To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

server_args param must be your livestatus socket. You must find that socket yourself, nobody can know where yours can be found. As far as I remember you posted some mails ago not to have /usr/lib/nagios/mk-livestatus/live so this is wrong configuration for
server_args.

All these problems (“I cannot find this or that”, “my files have wrong permissions” etc.) are the reasons why we have OMD - only right permissions, everyone has same locations, no crappy configuration…

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:31:

Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

From: Stjepan
Vučić

Sent: Thursday,
May 28, 2015 3:29 PM

To: ‘Marcel
Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

    disable         = no

}

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM

To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

connection refused for livestatus is usually either
xinetd
or
local firewall

If xinetd is not configured for a port, I think you get
a connection refused response.

I would check for a tcp listener on port 6557 on the host.

    netstat -an | grep LISTEN | grep 6557

If you don't see anything listening on port 6557, then
either xinetd is misconfigured or you didn't restart
xinetd after the configuration was changed.

    /etc/init.d/xinetd restart
···

On 05/28/2015 02:36 PM, Stjepan Vučić
wrote:

        Well,

I am following this tutorial, and it says:

        After

setting up Livestatus and restarting Nagios, two things
should happen:

  1.      The
    

socket file is created. (Check by navigating to
/usr/local/nagios/var/rw. The socket file live should have
been created.)

        I

have created that file because I can find it on my server,
it was created during setup.

        I

put that path to server_args and to nagios.cfg.

        I

get this error now:

        root@scnag:~#

echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

        Couldn't

connect to UNIX-socket at /usr/local/nagios/var/rw/live/:
Connection refused.

        Can

you tell where or what could be the cause of connection
refused?

        I

am no table to have OMD on this server, unfortunatelly. This
server has a loto f hosts and services, and I just need to
connect it to my OMD on a remote server.

        I

would be the happiest personi n the world if this would
work, the instructions seem to be so simple, but I don’t
know where is a mistake in configuration.

Regards,

Stjepan

From: Marcel Schulte

Thursday, May 28, 2015 3:41 PM
Stjepan Vučić;
Re: [Check_mk (english)] OMD distributed
monitoring

      server_args param must be your livestatus socket. You must

find that socket yourself, nobody can know where yours can be
found. As far as I remember you posted some mails ago not to
have /usr/lib/nagios/mk-livestatus/live so this is wrong
configuration for server_args.

      All these problems ("I cannot find this or that", "my files

have wrong permissions" etc.) are the reasons why we have OMD

  • only right permissions, everyone has same locations, no
    crappy configuration…

Marcel

Stjepan Vučić <Stjepan.Vucic@sedamit.hr >
schrieb am Do., 28. Mai 2015 15:31:

                Still

not working, but having another error:

                Livestatus

error

                Unhandled

exception: Malformed output. Livestatus TCP socket
might be unreachable.

Regards,

Stjepan

From: Stjepan Vučić

Sent: Thursday, May 28, 2015 3:29 PM

To: ‘Marcel Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD
distributed monitoring

                Sorry

for this, Marcel.

                I

can’t get to fix this and it is frustrating.

                I

did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

                I

am not sure about server :confused:

                So,

this is configuration:

                service

livestatus

{

type = UNLISTED

port = 6557

socket_type = stream

protocol = tcp

wait = no

                #

limit to 100 connections per second. Disable 3 secs
if above.

cps = 100 3

                #

set the number of maximum allowed parallel instances
of unixcat.

                #

Please make sure that this values is at least as
high as

                #

the number of threads defined with
num_client_threads in

                #

etc/mk-livestatus/nagios.cfg

instances = 500

                #

limit the maximum number of simultaneous connections
from

                #

one source IP address

per_source = 250

                #

Disable TCP delay, makes connection more responsive

flags = NODELAY

user = nagios

server = /usr/bin/unixcat

server_args = /usr/lib/nagios/mk-livestatus/live

                #

configure the IP address(es) of your Nagios server
here:

                #      

only_from = 127.0.0.1 10.0.20.1 10.0.20.2
10.7.11.44 172.16.212.9

disable = no

}

From: Marcel Schulte [mailto:schulte.marcel@gmail.com ]
Sent: Thursday, May 28, 2015 3:20 PM

                **To:** Stjepan Vučić;
                  checkmk-en@lists.mathias-kettner.de
                **Subject:** Re: [Check_mk (english)] OMD

distributed monitoring

              Stjepan, do me a favour and do not reply until you've

found your livestatus socket. It’s hell trying to help
when you never have the right information…

              So find your socket, get its owner, set that

information configured in xinetd config and reply if
it works or not.

Marcel

              Napomena: Ova poruka sadrzi podatke povjerljive

prirode, iskljucivo namijenjene osobama oznacenima kao
primateljima te se pristup od strane bilo koje druge
osobe smatra neovlastenim. Ukoliko niste oznaceni
primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo
zabranjeno i smatra se protuzakonitim. Ukoliko ste
dobili ovu poruku, a niste oznaceni primatelj, molimo
Vas da sto prije obavijestite posiljatelja poruke i
unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na
postojanje racunalnih virusa.

              Disclaimer: The information in this email is

confidential and it is intended solely for the
addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient,
any distribution, copying, duplication or disclosure
is prohibited and may be unlawful. If you have
received this email in error, please notify the sender
immediately and destroy it, and all copies of it. This
footnote also confirms that this email message has
been swept for the presence of computer viruses.


    Napomena: Ova poruka sadrzi podatke povjerljive prirode,

iskljucivo namijenjene osobama oznacenima kao primateljima te se
pristup od strane bilo koje druge osobe smatra neovlastenim.
Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje,
umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo
zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu
poruku, a niste oznaceni primatelj, molimo Vas da sto prije
obavijestite posiljatelja poruke i unistite sve postojece
kopije. Ova napomena takodjer potvrdjuje da je ova elektronicka
poruka testirana na postojanje racunalnih virusa.

    Disclaimer: The information in this email is confidential and it

is intended solely for the addressee. Access to this email by
anyone else is unauthorized. If you are not the intended
recipient, any distribution, copying, duplication or disclosure
is prohibited and may be unlawful. If you have received this
email in error, please notify the sender immediately and destroy
it, and all copies of it. This footnote also confirms that this
email message has been swept for the presence of computer
viruses.




_______________________________________________
checkmk-en mailing list
We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015

mailto:schulte.marcel@gmail.com
Sent:
**To:**checkmk-en@lists.mathias-kettner.de
Subject:

checkmk-en@lists.mathias-kettner.dehttp://lists.mathias-kettner.de/mailman/listinfo/checkmk-enhttp://mathias-kettner.de/conference

Before I tried to set up some different path and got this message:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/lib/nagios/mk-livestatus/live

No UNIX socket /usr/lib/nagios/mk-livestatus/live existing

So this must be the right socket now:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live/: Connection refused.

But for some reason it refuses connection…

Regards,

Stjepan

···

From: checkmk-en-bounces@lists.mathias-kettner.de
[mailto:checkmk-en-bounces@lists.mathias-kettner.de] On Behalf Of Jam Mulch
Sent: Thursday, May 28, 2015 8:47 PM
To: checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

connection refused for livestatus is usually either
xinetd
or
local firewall

If xinetd is not configured for a port, I think you get
a connection refused response.

I would check for a tcp listener on port 6557 on the host.

netstat -an | grep LISTEN | grep 6557

If you don’t see anything listening on port 6557, then
either xinetd is misconfigured or you didn’t restart
xinetd after the configuration was changed.

/etc/init.d/xinetd restart

On 05/28/2015 02:36 PM, Stjepan Vučić wrote:

Well, I am following this tutorial, and it says:

After setting up Livestatus and restarting Nagios, two things should happen:

The socket file is created. (Check by navigating to /usr/local/nagios/var/rw. The socket file live should have been created.)

I have created that file because I can find it on my server, it was created during setup.

I put that path to server_args and to nagios.cfg.

I get this error now:

root@scnag:~# echo ‘GET hosts’ | unixcat /usr/local/nagios/var/rw/live/

Couldn’t connect to UNIX-socket at /usr/local/nagios/var/rw/live/: Connection refused.

Can you tell where or what could be the cause of connection refused?

I am no table to have OMD on this server, unfortunatelly. This server has a loto f hosts and services, and I just need to connect it
to my OMD on a remote server.

I would be the happiest personi n the world if this would work, the instructions seem to be so simple, but I don’t know where is a
mistake in configuration.

Regards,

Stjepan

From: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:41 PM
To: Stjepan Vučić; checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

server_args param must be your livestatus socket. You must find that socket yourself, nobody can know where yours can be found. As far as I remember you posted some mails ago not to have /usr/lib/nagios/mk-livestatus/live so this is wrong configuration for
server_args.

All these problems (“I cannot find this or that”, “my files have wrong permissions” etc.) are the reasons why we have OMD - only right permissions, everyone has same locations, no crappy configuration…

Marcel

Stjepan Vučić Stjepan.Vucic@sedamit.hr schrieb am Do., 28. Mai 2015 15:31:

Still not working, but having another error:

Livestatus error

Unhandled exception: Malformed output. Livestatus TCP socket might be unreachable.

Regards,

Stjepan

From: Stjepan
Vučić

Sent: Thursday,
May 28, 2015 3:29 PM

To: ‘Marcel
Schulte’; checkmk-en@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] OMD distributed monitoring

Sorry for this, Marcel.

I can’t get to fix this and it is frustrating.

I did it by this tutorial.

http://stackoverflow.com/questions/16102832/how-to-install-mk-livestatus-on-nagios

    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

I am not sure about server :confused:

So, this is configuration:

service livestatus

{

    type            = UNLISTED
    port            = 6557
    socket_type     = stream
    protocol        = tcp
    wait            = no

limit to 100 connections per second. Disable 3 secs if above.

    cps             = 100 3

set the number of maximum allowed parallel instances of unixcat.

Please make sure that this values is at least as high as

the number of threads defined with num_client_threads in

etc/mk-livestatus/nagios.cfg

    instances       = 500

limit the maximum number of simultaneous connections from

one source IP address

    per_source      = 250

Disable TCP delay, makes connection more responsive

    flags           = NODELAY
    user            = nagios
    server          = /usr/bin/unixcat
    server_args     = /usr/lib/nagios/mk-livestatus/live

configure the IP address(es) of your Nagios server here:

only_from = 127.0.0.1 10.0.20.1 10.0.20.2 10.7.11.44 172.16.212.9

    disable         = no

}

From: Marcel
Schulte [mailto:schulte.marcel@gmail.com]
Sent: Thursday, May 28, 2015 3:20 PM

To: Stjepan Vučić;
checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] OMD distributed monitoring

Stjepan, do me a favour and do not reply until you’ve found your livestatus socket. It’s hell trying to help when you never have the right information…

So find your socket, get its owner, set that information configured in xinetd config and reply if it works or not.

Marcel

Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija, kopiranje, umnozavanje
ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije. Ova napomena takodjer
potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.


Napomena: Ova poruka sadrzi podatke povjerljive prirode, iskljucivo namijenjene osobama oznacenima kao primateljima te se pristup od strane bilo koje druge osobe smatra neovlastenim. Ukoliko niste oznaceni primatelj, svaka distribucija,
kopiranje, umnozavanje ili otkrivanje sadrzaja trecim osobama je strogo zabranjeno i smatra se protuzakonitim. Ukoliko ste dobili ovu poruku, a niste oznaceni primatelj, molimo Vas da sto prije obavijestite posiljatelja poruke i unistite sve postojece kopije.
Ova napomena takodjer potvrdjuje da je ova elektronicka poruka testirana na postojanje racunalnih virusa.

Disclaimer: The information in this email is confidential and it is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any distribution, copying, duplication or disclosure is prohibited
and may be unlawful. If you have received this email in error, please notify the sender immediately and destroy it, and all copies of it. This footnote also confirms that this email message has been swept for the presence of computer viruses.

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
We’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
[http://mathias-kettner.de/conference](http://mathias-kettner.de/conference)