Handling Nagios Client Monitoring System - Revision history

Steve: /* UPDATE.xWG */

2021-06-06T05:07:08Z

UPDATE.xWG

Arvind: /* The NEOSYS process IS running on the server but still cannot connect to NAGIOS */

2019-12-30T08:12:06Z

The NEOSYS process IS running on the server but still cannot connect to NAGIOS

← Older revision		Revision as of 08:12, 30 December 2019
Line 100:		Line 100:
	If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.		If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.

	Check if Internet Explorer can reach Nagios by using the below ~~links~~. The check is successful if you get the Nagios login request shown in the image below.		Check if Internet Explorer can reach Nagios by using the below link. The check is successful if you get the Nagios login request shown in the image below.
	*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428~~</pre>~~		https://monitor.hosts.neosys.com:4428
	*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com</pre>

	[[image:nagios_access.png]]		[[image:nagios_access.png]]

Arvind: /* The NEOSYS process IS running on the server but still cannot connect to NAGIOS */

2019-12-30T08:10:34Z

The NEOSYS process IS running on the server but still cannot connect to NAGIOS

← Older revision		Revision as of 08:10, 30 December 2019
Line 101:		Line 101:

	Check if Internet Explorer can reach Nagios by using the below links. The check is successful if you get the Nagios login request shown in the image below.		Check if Internet Explorer can reach Nagios by using the below links. The check is successful if you get the Nagios login request shown in the image below.
	*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428~~/monitor.php~~</pre>		*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428</pre>
	*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com~~/monitor.php~~</pre>		*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com</pre>

	[[image:nagios_access.png]]		[[image:nagios_access.png]]

Joel: /* The NEOSYS process IS running on the server but still cannot connect to NAGIOS */

2019-12-30T07:23:34Z

The NEOSYS process IS running on the server but still cannot connect to NAGIOS

← Older revision		Revision as of 07:23, 30 December 2019
Line 100:		Line 100:
	If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.		If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.

	Check if Internet Explorer can reach Nagios by using the ~~following link:~~		Check if Internet Explorer can reach Nagios by using the below links. The check is successful if you get the Nagios login request shown in the image below.
	*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428/monitor.php</pre>		*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428/monitor.php</pre>
	*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com/monitor.php</pre>		*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com/monitor.php</pre>

			[[image:nagios_access.png]]

	======If Internet Explorer CANNOT connect to Nagios======		======If Internet Explorer CANNOT connect to Nagios======

Joel: /* Fixing “NEOSYS has not checked in” error message */

2018-12-17T13:19:38Z

Fixing “NEOSYS has not checked in” error message

← Older revision		Revision as of 13:19, 17 December 2018
Line 109:		Line 109:

	If outbound access to monitor.hosts.neosys.com on port 4428 has not been enabled, then Nagios will not be able to update the status of the host and will show the error "NEOSYS not checked in".		If outbound access to monitor.hosts.neosys.com on port 4428 has not been enabled, then Nagios will not be able to update the status of the host and will show the error "NEOSYS not checked in".

			If port 4428 cannot be used, then Support can manually configure the network to use standard port 443 in the [http://userwiki.neosys.com/index.php/System_Configuration_File#Monitor_Port_No. system configuration file.]

			This requires that the client's IP number is added to the list of allowed IP numbers on nl10r router since Nagios https server gets multiple probes a day on port 443 if it is left open to everyone.

	======If Internet Explorer CAN connect to Nagios======		======If Internet Explorer CAN connect to Nagios======
Line 171:		Line 175:

	Refer [[Troubleshooting_NEOSYS_Generally#NEOSYS_process_window_displays_message_.22Upgrade_Downloading.22 \| here]]		Refer [[Troubleshooting_NEOSYS_Generally#NEOSYS_process_window_displays_message_.22Upgrade_Downloading.22 \| here]]

	~~===== Client network is blocking most outgoing ports including default port 4428 =====~~

	~~If a client network appears to be blocking port 4428, then NEOSYS will not be able to update Nagios normally.~~

	~~In that case, you can manually configure the network to use standard port 443 in the [http://userwiki.neosys.com/index.php/System_Configuration_File#Monitor_Port_No. system configuration file.]~~

	~~This requires that the client's IP number is added to the list of allowed IP numbers on nl10r router since Nagios https server gets multiple probes a day on port 443 if it is left open to everyone.~~

	===Fixing "Cannot make SSL connection" error===		===Fixing "Cannot make SSL connection" error===

Arvind: /* Fixing “NEOSYS has not checked in” error message */

2018-12-17T08:07:21Z

Fixing “NEOSYS has not checked in” error message

Joel: /* Fixing “NEOSYS has not checked in” error message */

2018-12-16T12:07:08Z

Fixing “NEOSYS has not checked in” error message

← Older revision		Revision as of 12:07, 16 December 2018
Line 77:		Line 77:

	==== Error Message Explained ====		==== Error Message Explained ====
	~~You notice a problem on~~ NAGIOS ~~indicating that '''''~~NEOSYS ~~not checked in''' on~~ a particular client server~~. This happens because NEOSYS is not updating NAGIOS~~.
			NAGIOS reports this error when it is is not able to update the status of NEOSYS for a particular client server.

	==== Possible Causes & Solutions ====		==== Possible Causes & Solutions ====
	#The maintenance window is left open. Make sure ~~the~~ maintenance window ~~has not been~~ left open in the server.
	#Hung process on server. e.g.:- Fatal Error in Rev Restart. Follow steps in troubleshooting [[Troubleshooting_NEOSYS_Generally#Troubleshooting_Hung_processes\| hung process]].		=====The maintenance window is left open=====
	=====The NEOSYS process is NOT running on the server=====
			Make sure that there isn't any maintenance window left open in the server.

			=====Hung process on server=====

			Check if there are any hung processes on the server e.g. Fatal Error in Rev Restart. Follow steps in troubleshooting [[Troubleshooting_NEOSYS_Generally#Troubleshooting_Hung_processes\| hung process]].

			=====The NEOSYS process IS NOT running on the server=====

	Start the NEOSYS process and wait for 10 mins for NEOSYS to check into NAGIOS.		Start the NEOSYS process and wait for 10 mins for NEOSYS to check into NAGIOS.
	~~<BR>~~

	=====The NEOSYS process IS running on the server but still cannot connect to NAGIOS=====		=====The NEOSYS process IS running on the server but still cannot connect to NAGIOS=====

	NEOSYS connects to NAGIOS using http~~. NEOSYS~~ automatically detects and uses any http proxy configuration configured in Internet Explorer. ~~If the Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.~~		NEOSYS connects to NAGIOS using http and automatically detects and uses any http proxy configuration configured in Internet Explorer.

	~~First check if Internet Explorer in the server can reach NAGIOS. Type the following link into the Internet Explorer in the server:~~

	~~New versions of NEOSYS (as of 25/7/2017) need the server to be able reach:~~

	~~https://monitor~~.~~hosts.neosys.com:4428/monitor.php~~		If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.

	Older versions of NEOSYS need the server to be able to reach:		Check if Internet Explorer can reach NAGIOS by using the following link:
			#New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428/monitor.php</pre>
			#Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com/monitor.php</pre>

	~~http://monitor.hosts.neosys.com/monitor.php~~		======If Internet Explorer CANNOT connect to NAGIOS======

	~~i.e.~~ outbound ~~port~~ 4428 ~~is required instead of port 80 on later versions on~~ NEOSYS.		The client's IT must enable outbound access preferably on all ports or at least 4428 to our NEOSYS server at monitor.hosts.neosys.com.

	If ~~you are asked~~ to ~~login~~ then ~~the Internet Explorer is working OK. You do~~ not ~~need~~ to ~~login. Just cancel~~ and ~~move on to~~ the ~~next step~~.		If outbound access to monitor.hosts.neosys.com on port 4428 has not been enabled, then NAGIOS will not be able to update the status of the host and will show the error "NEOSYS not checked in".

	If Internet Explorer ~~CANNOT~~ connect to NAGIOS ~~then resolving that fundamental issue will probably solve the NAGIOS connection issue too.~~		======If Internet Explorer CAN connect to NAGIOS======

	View the Internet Explorer proxy configuration as follows:		View the Internet Explorer proxy configuration as follows:
Line 111:		Line 116:
	[[image:ieproxy.png]]		[[image:ieproxy.png]]

	~~If Internet Explorer CAN connect to NAGIOS then check~~ if there is an issue with NEOSYS's http proxy server configuration as follows:		<br>Check if there is an issue with NEOSYS' http proxy server configuration as follows:

	#Search for UPDATE.$WG file located in the neosys\neosys. folder and open it using notepad or wordpad.		#Search for UPDATE.$WG file located in the neosys\neosys. folder and open it using notepad or wordpad.

Joel: /* Troubleshooting NAGIOS generally */

2018-12-04T10:32:10Z

Troubleshooting NAGIOS generally

← Older revision		Revision as of 10:32, 4 December 2018
Line 74:		Line 74:
	These steps can be carried out even when users are active.		These steps can be carried out even when users are active.

	====Fixing “NEOSYS has not checked in” error message====		===Fixing “NEOSYS has not checked in” error message===

	==== Error Message Explained ====		==== Error Message Explained ====

Gregory: /* Nagios services */

2018-08-08T13:04:59Z

Nagios services

← Older revision		Revision as of 13:04, 8 August 2018
Line 20:		Line 20:
	Nagios Configuration files:		Nagios Configuration files:

	* Commands to check different services ~~= <b>~~ ~/etc/nagios3/commands.cfg ~~</b>~~		* Commands to check different services. ~/etc/nagios3/commands.cfg
	* Contacts where support2@neosys.com is configured. Emails from nagios will be sent to the email ID configured here. ~~<b>~~ /etc/nagios3/conf.d.backups/contacts.cfg ~~</b>~~		* Contacts where support2@neosys.com is configured. Emails from nagios will be sent to the email ID configured here. /etc/nagios3/conf.d.backups/contacts.cfg
	* For Oman Client. Unclear of purpose. ~~<b>~~ /etc/nagios3/conf.d.backups/dtme.cfg ~~</b>~~		* For Oman Client. Unclear of purpose. /etc/nagios3/conf.d.backups/dtme.cfg
	* Fully commented file of generic hostgroup definitions ~~<b>~~ /etc/nagios3/conf.d.backups/hostgroups_nagios2.cfg ~~</b>~~		* Fully commented file of generic hostgroup definitions. /etc/nagios3/conf.d.backups/hostgroups_nagios2.cfg
	* Host group definition ~~<b>~~ /etc/nagios3/conf.d.backups/linux.cfg ~~</b>~~		* Host group definition. /etc/nagios3/conf.d.backups/linux.cfg
	* Files where all the neosys hosts and hostgroups are defined ~~<b>~~ /etc/nagios3/conf.d.backups/neosysclients.cfg ~~</b>~~		* Files where all the neosys hosts and hostgroups are defined. /etc/nagios3/conf.d.backups/neosysclients.cfg
	* Config for monitor.neosys.com ~~<b>~~ /etc/nagios3/conf.d.backups/monitor.cfg ~~</b>~~		* Config for monitor.neosys.com. /etc/nagios3/conf.d.backups/monitor.cfg

	==How to handle a service error==		==How to handle a service error==

Gregory: /* Nagios services */

2018-08-08T13:02:12Z

Nagios services

@@ Line 17: / Line 17: @@
 * Clients hosted on a NEOSYS cloud server might not have services such as SSH or PING as this is monitored as part of the internal server service.
 * Nagios sends out email alerts to support2@neosys.com (which is forwarded to support@neosys.com) from 8 am to 12 midnight on all Dubai working days (Sun-Thu). No alerts are sent out on Fri and Sat, unless they are for NEOSYS internal servers.
 ==How to handle a service error==

← Older revision		Revision as of 08:07, 17 December 2018
Line 78:		Line 78:
	==== Error Message Explained ====		==== Error Message Explained ====

	~~NAGIOS~~ reports this error when it is is not able to update the status of NEOSYS for a particular client server.		Nagios reports this error when it is is not able to update the status of NEOSYS for a particular client server.

	==== Possible Causes & Solutions ====		==== Possible Causes & Solutions ====
Line 84:		Line 84:
	=====The maintenance window is left open=====		=====The maintenance window is left open=====

	Make sure that there ~~isn't any~~ maintenance window left open in the server.		Make sure that there is no maintenance window left open in the server.

	=====Hung process on server=====		=====Hung process on server=====
Line 92:		Line 92:
	=====The NEOSYS process IS NOT running on the server=====		=====The NEOSYS process IS NOT running on the server=====

	~~Start~~ the NEOSYS process and wait ~~for 10 mins~~ for NEOSYS to check into ~~NAGIOS~~.		If there are no NEOSYS processes running, then start the NEOSYS process and wait for NEOSYS to check into Nagios, or force Nagios to re-check the status of NEOSYS service.

	=====The NEOSYS process IS running on the server but still cannot connect to NAGIOS=====		=====The NEOSYS process IS running on the server but still cannot connect to NAGIOS=====

	NEOSYS connects to ~~NAGIOS~~ using http and automatically detects and uses any http proxy configuration configured in Internet Explorer.		NEOSYS connects to Nagios using http and automatically detects and uses any http proxy configuration configured in Internet Explorer.

	If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.		If Internet Explorer in the server can reach the internet then NEOSYS should be able to update to NAGIOS via the same proxy.

	Check if Internet Explorer can reach ~~NAGIOS~~ by using the following link:		Check if Internet Explorer can reach Nagios by using the following link:
	#New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428/monitor.php</pre>		*New versions of NEOSYS need to reach the below URL. (Outbound port 4428 is required instead of port 80 on later versions on NEOSYS) <br> <pre>https://monitor.hosts.neosys.com:4428/monitor.php</pre>
	#Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com/monitor.php</pre>		*Older versions of NEOSYS need the server to be able to reach the below URL. <br> <pre>http://monitor.hosts.neosys.com/monitor.php</pre>

	======If Internet Explorer CANNOT connect to ~~NAGIOS~~======		======If Internet Explorer CANNOT connect to Nagios======

	The client's IT must enable outbound access preferably on all ports or at least 4428 to our NEOSYS server at monitor.hosts.neosys.com.		The client's IT must enable outbound access preferably on all ports or at least 4428 to our NEOSYS server at monitor.hosts.neosys.com.

	If outbound access to monitor.hosts.neosys.com on port 4428 has not been enabled, then ~~NAGIOS~~ will not be able to update the status of the host and will show the error "NEOSYS not checked in".		If outbound access to monitor.hosts.neosys.com on port 4428 has not been enabled, then Nagios will not be able to update the status of the host and will show the error "NEOSYS not checked in".

	======If Internet Explorer CAN connect to ~~NAGIOS~~======		======If Internet Explorer CAN connect to Nagios======

	View the Internet Explorer proxy configuration as follows:		View the Internet Explorer proxy configuration as follows: