I tried this but trying to login via « distributed monitoring », I got the following:
_ Internal error: Your request timed out after 110 seconds. This issue may be related to a local configuration problem or a request which works with a too large number of objects. But if you think this issue is a bug, please send a crash
report.
Traceback (most recent call last):
File “/omd/sites/monitoring/share/check_mk/web/htdocs/wato.py”, line 9332, in _action_login
secret = do_site_login(login_id, name, passwd)
File “/omd/sites/monitoring/share/check_mk/web/htdocs/watolib.py”, line 3679, in do_site_login
response = get_url(url, site.get(‘insecure’, False), auth=(name, password), data=post_data).strip()
File “/omd/sites/monitoring/share/check_mk/web/htdocs/watolib.py”, line 3700, in get_url
files=files,
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/api.py”, line 110, in post
return request(‘post’, url, data=data, json=json, **kwargs)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/api.py”, line 56, in request
return session.request(method=method, url=url, **kwargs)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/sessions.py”, line 488, in request
resp = self.send(prep, **send_kwargs)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/sessions.py”, line 609, in send
r = adapter.send(request, **kwargs)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/adapters.py”, line 423, in send
timeout=timeout
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/packages/urllib3/connectionpool.py”, line 600, in urlopen
chunked=chunked)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/packages/urllib3/connectionpool.py”, line 356, in _make_request
conn.request(method, url, **httplib_request_kw)
File “/omd/sites/monitoring/lib/python2.7/httplib.py”, line 1042, in request
self._send_request(method, url, body, headers)
File “/omd/sites/monitoring/lib/python2.7/httplib.py”, line 1082, in _send_request
self.endheaders(body)
File “/omd/sites/monitoring/lib/python2.7/httplib.py”, line 1038, in endheaders
self._send_output(message_body)
File “/omd/sites/monitoring/lib/python2.7/httplib.py”, line 882, in _send_output
self.send(msg)
File “/omd/sites/monitoring/lib/python2.7/httplib.py”, line 844, in send
self.connect()
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/packages/urllib3/connection.py”, line 166, in connect
conn = self._new_conn()
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/packages/urllib3/connection.py”, line 141, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File “/omd/sites/monitoring/lib/python/requests-2.13.0-py2.7.egg/requests/packages/urllib3/util/connection.py”, line 73, in create_connection
sock.connect(sa)
File “/omd/sites/monitoring/lib/python2.7/socket.py”, line 228, in meth
return getattr(self.sock,name)(*args)
File “/omd/sites/monitoring/share/check_mk/web/htdocs/htmllib.py”, line 2930, in handle_request_timeout
self.request_timeout())
RequestTimeout: Your request timed out after 110 seconds. This issue may be related to a local configuration problem or a request which works with a too large number of objects. But if you think this issue is a bug, please send a crash report.
Can help me to troubleshoot which config is not ok ?
Eric
···
From: Arno Wijnhoven [mailto:arnow@vsnsystemen.nl]
Sent: mardi 27 mars 2018 14:56
To: Eric Lecocq Eric.Lecocq@prodata-systems.be; checkmk-en@lists.mathias-kettner.de
Subject: RE: Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
https://mathias-kettner.com/cms_distributed_monitoring.html
Scroll down to ‘2.4 Tethering existing instances’. I’ve never done this, but this is what you need.
Arno Wijnhoven
T: 2580
From: Eric Lecocq [mailto:Eric.Lecocq@prodata-systems.be]
Sent: dinsdag 27 maart 2018 14:47
To: Arno Wijnhoven arnow@vsnsystemen.nl;
checkmk-en@lists.mathias-kettner.de
Subject: RE: Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
Hello,
Thank you for your answer. I made the error.
By using option “push to slave”, I erase the configs of my slaves…. Then it’s normal that there is nothing to show.
But I didn’t know that push to slave will erase everything.
Is there a way to “migrate” a site without option “push config to smave” without erasing everything ?
Best regards,
Eric
From: Arno Wijnhoven [mailto:arnow@vsnsystemen.nl]
Sent: lundi 26 mars 2018 15:10
To: Eric Lecocq Eric.Lecocq@prodata-systems.be;
checkmk-en@lists.mathias-kettner.de
Subject: RE: Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
Hi Eric,
If you mean the ‘Master Control’ dashlet, then everything seems to be fine.
I’m afraid I can’t help you with this issue, perhaps someone else can.
Although this probably won’t help you, I’ll share my working 1.4.0p26 ‘Distributed Monitoring’ settings just for reference.
Livestatus settings:
Connection: ‘Connect via TCP’, Host: ‘’ Port: ‘6557’
Connection Timeout: ‘10’
Persistent connection: yes
URL prefix: ‘http:///’
Status host: blank
Disable: no
Configuration replication:
Replication method: ‘Slave: push configuration to this site’
Multisite-URL: ‘http:////check_mk/’
WATO: disable configuration -> yes
SSL: blank
Direct login: yes
Sync: ‘Sync users with all connections’
Event Console: replicate -> yes
Extensions: replicate -> yes
Arno
From: Eric Lecocq [mailto:Eric.Lecocq@prodata-systems.be]
Sent: maandag 26 maart 2018 14:20
To: Arno Wijnhoven arnow@vsnsystemen.nl;
checkmk-en@lists.mathias-kettner.de
Subject: RE: Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
Hello,
Adding slaves is not an issue. The issue is: The hosts and services on those slaves are not showing on the main check_mk. On the main page, dashlet with sites is fully green.
Best regards,
Eric
From: Arno Wijnhoven [mailto:arnow@vsnsystemen.nl]
Sent: lundi 26 mars 2018 13:58
To: Eric Lecocq Eric.Lecocq@prodata-systems.be;
checkmk-en@lists.mathias-kettner.de
Subject: RE: Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
Just checking if I understand your problem correctly:
When you are logged in to your main system you can’t see your slaves’ hosts under ‘WATO – Hosts’?
What happens if you add a new host on your main system?
Can you select one of the slave sites for monitoring (“Monitored on site”)?
Although your problem doesn’t sound like a sync issue, kindly check if the time isn’t drifting on your slaves. Syncing won’t work if the time differs too much.
Other than that I’ve never had any issues with multisite. I started out with empty slave sites and added hosts from the main site - this worked like a charm.
Arno Wijnhoven
From: checkmk-en [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Eric Lecocq
Sent: maandag 26 maart 2018 13:05
To: checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] Check_mk 1.4.0.p25/27 - multisite - site on-line but no data coming in …
Hello,
In a multisite check_mk 1.4.0p25, I have the following: i begin to test some of the options in “new connection” and now, the data from he slaves are not visible anymore…
Any clue ?
I have a backup. I made a brand new site with the latest version and problem still present.
Thank you for your help
Eric