-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service time out #27
Comments
Hi, is this a recent thing and it was ok before? Also I take it you have already changed the service_check_timeout in core config from 60 to 90.? Cheers Will. |
Nope not a recent issue, Also updated the IBMi Plugin however no good.
Yeh we changed the setting to 90.
Regards,
Rajat Dhuria, IBMi (AS400) Team
Marsh & McLennan Companies
Global Technology Infrastructure (MGTI) | Centralized Operations
Desk: +1 8557 628 279 EXTN 4161840 | Mobile +91 831898813 | ***@***.******@***.***>
www.mmc.com<http://www.mmc.com/>
***@***.***
***@***.***
From: williamlea1 ***@***.***>
Sent: Tuesday, April 12, 2022 1:16 PM
To: IBM/nagios-for-i ***@***.***>
Cc: Dhuria, Rajat ***@***.***>; Author ***@***.***>
Subject: Re: [IBM/nagios-for-i] Service time out (Issue #27)
Hi, is this a recent thing and it was ok before?
Also I take it you have already changed the service_check_timeout in core config from 60 to 90.?
We upgraded to 5.8.8 and noticed an increase in timeouts.
Cheers Will.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/IBM/nagios-for-i/issues/27*issuecomment-1096280160__;Iw!!O7V3aRRsHkZJLA!HTupD83hk6KBK-kjKBz20YyjMYel6iAt0YpR1iZy-gso8fkhs9XawDJWG1gXLiZLwVl7vM4b_VrNULR-5XKV6Ujx$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYVQLGRKJLQHSDO3X737LD3VEUS2HANCNFSM5TFNLKGA__;!!O7V3aRRsHkZJLA!HTupD83hk6KBK-kjKBz20YyjMYel6iAt0YpR1iZy-gso8fkhs9XawDJWG1gXLiZLwVl7vM4b_VrNULR-5WvwMomD$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
it might also be worth noting that depending on how many services that if one services starts to take a bit longer then that can have a knock on effect with other services also to trying run and if they are trying to access same tables then again it slows down more. |
Yeh that might be one case however we have seen the same across multiple LPAR on the same time across all services:
***@***.***
***@***.***
Regards,
Rajat Dhuria, IBMi (AS400) Team
Marsh & McLennan Companies
Global Technology Infrastructure (MGTI) | Centralized Operations
Desk: +1 8557 628 279 EXTN 4161840 | Mobile +91 831898813 | ***@***.******@***.***>
www.mmc.com<http://www.mmc.com/>
***@***.***
***@***.***
From: williamlea1 ***@***.***>
Sent: Tuesday, April 12, 2022 1:59 PM
To: IBM/nagios-for-i ***@***.***>
Cc: Dhuria, Rajat ***@***.***>; Author ***@***.***>
Subject: Re: [IBM/nagios-for-i] Service time out (Issue #27)
it might also be worth noting that depending on how many services that if one services starts to take a bit longer then that can have a knock on effect with other services also to trying run and if they are trying to access same tables then again it slows down more.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/IBM/nagios-for-i/issues/27*issuecomment-1096350767__;Iw!!O7V3aRRsHkZJLA!D88mwxTmhCdyo5JxEV4zWOr1yQ2issvbGrmnWk7T6Su0TLLY-sX7MuoM7_EeRk15nCZFKR6CZVQ0tFChBSiLEuQr$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYVQLGT22HEDK7FEKMERZOTVEUX3RANCNFSM5TFNLKGA__;!!O7V3aRRsHkZJLA!D88mwxTmhCdyo5JxEV4zWOr1yQ2issvbGrmnWk7T6Su0TLLY-sX7MuoM7_EeRk15nCZFKR6CZVQ0tFChBbnASHHa$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
as I said we have experienced more issues since we upgraded to 5.8.8. Before that we had the timeout value of 70 seconds and most of the time it sufficed but within hours of installing the upgrade I have had to up it to 120 seconds to cope. We did find that a Custom SQL service was exacerbating the situation and when turning that service off it improved but still not completely gone away. But certainly the upgrade has highlighted an issue we are looking into ourselves. |
Thanks than I would hold on to the upgrade :
***@***.***
Nagios plugin for i version: 2.3.4
Released on 11/12/2021
Regards,
Rajat Dhuria, IBMi (AS400) Team
Marsh & McLennan Companies
Global Technology Infrastructure (MGTI) | Centralized Operations
Desk: +1 8557 628 279 EXTN 4161840 | Mobile +91 831898813 | ***@***.******@***.***>
www.mmc.com<http://www.mmc.com/>
***@***.***
***@***.***
From: williamlea1 ***@***.***>
Sent: Tuesday, April 12, 2022 2:39 PM
To: IBM/nagios-for-i ***@***.***>
Cc: Dhuria, Rajat ***@***.***>; Author ***@***.***>
Subject: Re: [IBM/nagios-for-i] Service time out (Issue #27)
as I said we have experienced more issues since we upgraded to 5.8.8. Before that we had the timeout value of 70 seconds and most of the time it sufficed but within hours of installing the upgrade I have had to up it to 120 seconds to cope. We did find that a Custom SQL service was exacerbating the situation and when turning that service off it improved but still not completely gone away. But certainly the upgrade has highlighted an issue we are looking into ourselves.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/IBM/nagios-for-i/issues/27*issuecomment-1096408146__;Iw!!O7V3aRRsHkZJLA!Hc37McMsps-pKH90owXnGZQ6YJ9HArf78ewpHiI78vGxouiPAbcYrl_X3DemRpI8aXVk5uZ8Y9Lf72SHcLD451xn$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYVQLGQXJT7BEPKX3NFLPZTVEU4SDANCNFSM5TFNLKGA__;!!O7V3aRRsHkZJLA!Hc37McMsps-pKH90owXnGZQ6YJ9HArf78ewpHiI78vGxouiPAbcYrl_X3DemRpI8aXVk5uZ8Y9Lf72SHcNrcjJC5$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
We have IBMi LPAR being monitored by Nagios. every now and then we face the see the below issue. Please suggest
Notification details:
(Service check timed out after 91.01 seconds)
The text was updated successfully, but these errors were encountered: