-
Notifications
You must be signed in to change notification settings - Fork 149
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
Issue with Business Process #1351
Comments
does that happen all the time or just from time to time? And if you go to the services or hosts page, does naemon recover from that error? |
This used to work reliably, but now it no longer works, and is repeatable every time. Naemon is up and running, it’s just by Business Processes that no longer seem to work
Kevin McKee
Application Development Architect
Goodyear Canada Inc.
388 Goodyear Rd, Napanee, ON K7R 3L2
phone.613.354.7850
***@***.******@***.***>
From: Sven Nierlein ***@***.***>
Date: Tuesday, April 9, 2024 at 3:15 PM
To: sni/Thruk ***@***.***>
Cc: Kevin McKee ***@***.***>, Author ***@***.***>
Subject: [EXT] Re: [sni/Thruk] Issue with Business Process (Issue #1351)
WARNING: This is an EXTERNAL email. THINK before you open attachments, click links or respond. USE the Outlook button to REPORT suspicious email.
does that happen all the time or just from time to time? And if you go to the services or hosts page, does naemon recover from that error?
—
Reply to this email directly, view it on GitHub<#1351 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJY7YSYB4HOLPLRHPZQYPFLY4Q46JAVCNFSM6AAAAABF7BVMTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVHA4TSMBYGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
just a workaround, but using the livestatus unix socket instead of tcp localhost:7003 might improve the situation. Is there a reason for using the tcp connection? |
That isn’t something I specifically setup/chose – if you tell me where/how to change to the unix socket I’d be happy to give that a try
Kevin McKee
Application Development Architect
Goodyear Canada Inc.
388 Goodyear Rd, Napanee, ON K7R 3L2
phone.613.354.7850
***@***.******@***.***>
From: Sven Nierlein ***@***.***>
Date: Wednesday, April 10, 2024 at 3:03 AM
To: sni/Thruk ***@***.***>
Cc: Kevin McKee ***@***.***>, Author ***@***.***>
Subject: [EXT] Re: [sni/Thruk] Issue with Business Process (Issue #1351)
WARNING: This is an EXTERNAL email. THINK before you open attachments, click links or respond. USE the Outlook button to REPORT suspicious email.
just a workaround, but using the livestatus unix socket instead of tcp localhost:7003 might improve the situation. Is there a reason for using the tcp connection?
—
Reply to this email directly, view it on GitHub<#1351 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJY7YS6ORIVY2M5GHUDZQCTY4TP3VAVCNFSM6AAAAABF7BVMTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGY3TAMZUGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm using the Business Process plugin within Naemon/Thruk, and have previously been able to edit/save the processes successfully. More recently - and I don't know if it's a result of patches applied to my system, I'm now getting an error when trying to save a business process.
Thruk Version
3.14.2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Before, the business process would save without error, and then work (show red/green items as per host status), vs now where the items are now just gray, and have a status of 'pending'
Screenshots
Desktop (please complete the following information):
The only additional thing I see in my thruk.log file is
Naemon: 491: failed to connect - failed to connect to localhost:7003: Connection refused. at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 1598
I'm not really sure where to start troubleshooting this issue - if anybody has any tips, I'd appreciate the help. Thanks
The text was updated successfully, but these errors were encountered: