You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your efforts in providing this container!
Whenever I restart the Docker container I get:
nagios | nagios: Successfully launched command file worker with pid 35
nagios | nsca[43]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[44]: There's already an NSCA server running (PID 16). Bailing out...
nagios | postfix/master[16]: daemon started -- version 3.6.4, configuration /etc/postfix
nagios | nsca[47]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[48]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[49]: There's already an NSCA server running (PID 16). Bailing out...
If I just force-recreate it this doesn't happen.
The text was updated successfully, but these errors were encountered:
pathia
changed the title
here's already an NSCA server running (PID 16). Bailing out...
there's already an NSCA server running (PID 16). Bailing out...
Mar 10, 2024
I found that the following command followed by a restart of the container "fixes" it.
docker exec -it nagios rm /var/run/nsca.pid
But it's far from a permanent solution.
Thanks for your efforts in providing this container!
Whenever I restart the Docker container I get:
nagios | nagios: Successfully launched command file worker with pid 35
nagios | nsca[43]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[44]: There's already an NSCA server running (PID 16). Bailing out...
nagios | postfix/master[16]: daemon started -- version 3.6.4, configuration /etc/postfix
nagios | nsca[47]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[48]: There's already an NSCA server running (PID 16). Bailing out...
nagios | nsca[49]: There's already an NSCA server running (PID 16). Bailing out...
If I just force-recreate it this doesn't happen.
The text was updated successfully, but these errors were encountered: