error general time-out (alarm signal)
-
- Posts: 74
- Joined: Thu Jan 25, 2018 1:13 am
error general time-out (alarm signal)
I have been getting this "error general time-out (alarm signal)" with few servers. This is just one server example. I tried to google to find the solution but nothing work.
- Attachments
-
- Service.txt
- Service
- (1.28 KiB) Downloaded 295 times
-
- host.txt
- Host
- (1.79 KiB) Downloaded 294 times
-
- Posts: 74
- Joined: Thu Jan 25, 2018 1:13 am
Re: error general time-out (alarm signal)
I have also uploaded check_command config
- Attachments
-
- test.txt
- (4.17 KiB) Downloaded 287 times
-
- command.txt
- check_command
- (919 Bytes) Downloaded 328 times
Re: error general time-out (alarm signal)
Please change your commands to these:
Then edit your /usr/local/nagios/etc/nagios.cfg and adjust your service_check_timeout to match:
Then restart the nagios service:
Let us know if that resolves the issue.
Thank you
Code: Select all
define command{
command_name check_snmp_storage_ux_root
command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -t 90 -C $ARG1$ -m / -r -q FixedDisk -w90 -c95 -G
}
define command{
command_name check_snmp_storage_ux_not_root
command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -t 90 -C $ARG1$ -m / -r -e -q FixedDisk -w90 -c95 -G
}
Code: Select all
service_check_timeout=90
Code: Select all
service nagios restart
Thank you
Re: error general time-out (alarm signal)
The commands that are failing are using snmp. Is the host configured to use snmp? Check to see if it is up and responding with:
nmap 10.180.50.100 -p 161 -sU
nmap 10.180.50.100 -p 161 -sU
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: error general time-out (alarm signal)
First thing to do is to verify that the Host has SNMP enabled in it and that the community string you are using in the commands are valid.
If the remote host is not setup for SNMP polling, it will cause the timeout.
Another thing, make sure the firewall allows inbound UDP connections on port 161. That is required.
And, you may need to specify the SNMP version for the check_snmp plugin's command line option.
If the remote host is not setup for SNMP polling, it will cause the timeout.
Another thing, make sure the firewall allows inbound UDP connections on port 161. That is required.
And, you may need to specify the SNMP version for the check_snmp plugin's command line option.
Code: Select all
-P, --protocol=[1|2c|3]
SNMP protocol version
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
- Posts: 74
- Joined: Thu Jan 25, 2018 1:13 am
Re: error general time-out (alarm signal)
It seems good to me.cdienger wrote:The commands that are failing are using snmp. Is the host configured to use snmp? Check to see if it is up and responding with:
nmap 10.180.50.100 -p 161 -sU
Code: Select all
[root@ams900 ~]# nmap 10.180.50.100 -p 161 -sU
Starting Nmap 7.01 ( https://nmap.org ) at 2019-01-09 09:22 CST
Nmap scan report for asftp900.enclave.local (10.180.50.100)
Host is up (0.00029s latency).
PORT STATE SERVICE
161/udp closed snmp
Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds
[root@ams900 ~]#
-
- Posts: 74
- Joined: Thu Jan 25, 2018 1:13 am
Re: error general time-out (alarm signal)
I made the changes whatever you recommended but it didn't work out. It threw error "Invalid timeout value...." you can see in the picturessax wrote:Please change your commands to these:
Then edit your /usr/local/nagios/etc/nagios.cfg and adjust your service_check_timeout to match:Code: Select all
define command{ command_name check_snmp_storage_ux_root command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -t 90 -C $ARG1$ -m / -r -q FixedDisk -w90 -c95 -G } define command{ command_name check_snmp_storage_ux_not_root command_line $USER1$/check_snmp_storage.pl -H $HOSTADDRESS$ -t 90 -C $ARG1$ -m / -r -e -q FixedDisk -w90 -c95 -G }
Then restart the nagios service:Code: Select all
service_check_timeout=90
Let us know if that resolves the issue.Code: Select all
service nagios restart
Thank you
Re: error general time-out (alarm signal)
The nmap command shows that the UDP port 161 is closed so that is not good.
Check that server and verify that it is running SNMP.
The timeout error for the plugin is caused by a too large of value for the -t option, set it to 60 seconds and that will fix that.
Check that server and verify that it is running SNMP.
The timeout error for the plugin is caused by a too large of value for the -t option, set it to 60 seconds and that will fix that.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
- Posts: 74
- Joined: Thu Jan 25, 2018 1:13 am
Re: error general time-out (alarm signal)
tgriep, I checked on the server and snmpd wasn't installed so I installed it. Snmpd service is running.tgriep wrote:First thing to do is to verify that the Host has SNMP enabled in it and that the community string you are using in the commands are valid.
If the remote host is not setup for SNMP polling, it will cause the timeout.
Another thing, make sure the firewall allows inbound UDP connections on port 161. That is required.
And, you may need to specify the SNMP version for the check_snmp plugin's command line option.Code: Select all
-P, --protocol=[1|2c|3] SNMP protocol version
- Attachments
-
- snmp.txt
- (4.03 KiB) Downloaded 327 times
Re: error general time-out (alarm signal)
Thanks for the update. All that is left to do is to fix the -t value to 60 on the command and to test it out.
Be sure to check out our Knowledgebase for helpful articles and solutions!