Skip to content
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

Open
Kevin-McKee opened this issue Apr 9, 2024 · 4 comments
Open

Issue with Business Process #1351

Kevin-McKee opened this issue Apr 9, 2024 · 4 comments

Comments

@Kevin-McKee
Copy link

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.

320843450-2c36752f-e3e6-47c0-8b28-4d0638497b21

Thruk Version
3.14.2

To Reproduce
Steps to reproduce the behavior:

  1. Go to reports, business process
  2. Click on an existing business process
  3. Click on 'enable edit mode'
  4. Click 'save changes'

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
Screenshot 2024-04-09 at 2 11 17 PM
320843450-2c36752f-e3e6-47c0-8b28-4d0638497b21

Desktop (please complete the following information):

  • Safari 17.2.1
  • Chrome 123.0.6312.107

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

@sni
Copy link
Owner

sni commented Apr 9, 2024

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?

@Kevin-McKee
Copy link
Author

Kevin-McKee commented Apr 9, 2024 via email

@sni
Copy link
Owner

sni commented Apr 10, 2024

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?

@Kevin-McKee
Copy link
Author

Kevin-McKee commented Apr 10, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants