Discussion:
[Check_mk (english)] Error during system startup
Florian Holeczek
2018-02-09 05:40:24 UTC
Permalink
Hi all,

I'm using the latest Check_MK Raw Edition on an Ubuntu 16.04 server.

There's an error during startup which marks the omd.service as failed to start.

However, everything will be up and running after startup, i.e. without the need for any manual steps, so I think it's more or less almost a cosmetic issue.

Please find below the details. Does anybody else here face the same issue, or can someone confirm it's a bug?


# systemctl status omd.service
● omd.service - Check_MK Monitoring
Loaded: loaded (/etc/systemd/system/omd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fr 2018-02-09 06:21:24 CET; 25s ago
Docs: https://mathias-kettner.com
Process: 1449 ExecStart=/usr/bin/omd start (code=exited, status=1/FAILURE)
Main PID: 1449 (code=exited, status=1/FAILURE)

Feb 09 06:21:24 myserver omd[1449]: create_skeleton_file(skelroot, sitedir, dirpath + "/" + entry, replacements)
Feb 09 06:21:24 myserver omd[1449]: File "/usr/bin/omd", line 752, in create_skeleton_file
Feb 09 06:21:24 myserver omd[1449]: os.makedirs(user_path)
Feb 09 06:21:24 myserver omd[1449]: File "/omd/versions/1.4.0p24.cre/lib/python2.7/os.py", line 157, in makedirs
Feb 09 06:21:24 myserver omd[1449]: mkdir(name, mode)
Feb 09 06:21:24 myserver omd[1449]: OSError: [Errno 17] File exists: '/omd/sites/mysite/tmp/check_mk'
Feb 09 06:21:24 myserver systemd[1]: omd.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 06:21:24 myserver systemd[1]: Failed to start Check_MK Monitoring.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Unit entered failed state.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Failed with result 'exit-code'.


Thanks and kind regards
Florian
Andreas Döhler
2018-02-09 17:03:04 UTC
Permalink
Hi Florian,

Can you check if there is a init script existing with name
"check-mk-<version-number>" if yes it is possible that this script was
executed before the omd service. I remove all old legacy start scripts if I
use the systemd services.

Best regards
Andreas
Post by Florian Holeczek
Hi all,
I'm using the latest Check_MK Raw Edition on an Ubuntu 16.04 server.
There's an error during startup which marks the omd.service as failed to start.
However, everything will be up and running after startup, i.e. without the
need for any manual steps, so I think it's more or less almost a cosmetic
issue.
Please find below the details. Does anybody else here face the same issue,
or can someone confirm it's a bug?
# systemctl status omd.service
● omd.service - Check_MK Monitoring
Loaded: loaded (/etc/systemd/system/omd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fr 2018-02-09 06:21:24 CET; 25s ago
Docs: https://mathias-kettner.com
Process: 1449 ExecStart=/usr/bin/omd start (code=exited,
status=1/FAILURE)
Main PID: 1449 (code=exited, status=1/FAILURE)
Feb 09 06:21:24 myserver omd[1449]: create_skeleton_file(skelroot,
sitedir, dirpath + "/" + entry, replacements)
Feb 09 06:21:24 myserver omd[1449]: File "/usr/bin/omd", line 752, in
create_skeleton_file
Feb 09 06:21:24 myserver omd[1449]: os.makedirs(user_path)
Feb 09 06:21:24 myserver omd[1449]: File
"/omd/versions/1.4.0p24.cre/lib/python2.7/os.py", line 157, in makedirs
Feb 09 06:21:24 myserver omd[1449]: mkdir(name, mode)
'/omd/sites/mysite/tmp/check_mk'
Feb 09 06:21:24 myserver systemd[1]: omd.service: Main process exited,
code=exited, status=1/FAILURE
Feb 09 06:21:24 myserver systemd[1]: Failed to start Check_MK Monitoring.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Unit entered failed state.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Failed with result 'exit-code'.
Thanks and kind regards
Florian
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
Florian Holeczek
2018-02-10 16:11:44 UTC
Permalink
Hi Andreas,

thanks very much, that was it!

In fact, such an init script is even existing once per each installed version, in my case:
/etc/init.d/check-mk-raw-1.4.0p22
/etc/init.d/check-mk-raw-1.4.0p23
/etc/init.d/check-mk-raw-1.4.0p24

Kind regards
Florian
Post by Andreas Döhler
Hi Florian,
Can you check if there is a init script existing with name "check-mk-<version-number>" if yes it is possible that this script was executed before the omd service. I remove all old legacy start scripts if I use the systemd services.
Best regards
Andreas
Hi all,
I'm using the latest Check_MK Raw Edition on an Ubuntu 16.04 server.
There's an error during startup which marks the omd.service as failed to start.
However, everything will be up and running after startup, i.e. without the need for any manual steps, so I think it's more or less almost a cosmetic issue.
Please find below the details. Does anybody else here face the same issue, or can someone confirm it's a bug?
# systemctl status omd.service
● omd.service - Check_MK Monitoring
   Loaded: loaded (/etc/systemd/system/omd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fr 2018-02-09 06:21:24 CET; 25s ago
     Docs: https://mathias-kettner.com
  Process: 1449 ExecStart=/usr/bin/omd start (code=exited, status=1/FAILURE)
 Main PID: 1449 (code=exited, status=1/FAILURE)
Feb 09 06:21:24 myserver omd[1449]:     create_skeleton_file(skelroot, sitedir, dirpath + "/" + entry, replacements)
Feb 09 06:21:24 myserver omd[1449]:   File "/usr/bin/omd", line 752, in create_skeleton_file
Feb 09 06:21:24 myserver omd[1449]:     os.makedirs(user_path)
Feb 09 06:21:24 myserver omd[1449]:   File "/omd/versions/1.4.0p24.cre/lib/python2.7/os.py", line 157, in makedirs
Feb 09 06:21:24 myserver omd[1449]:     mkdir(name, mode)
Feb 09 06:21:24 myserver omd[1449]: OSError: [Errno 17] File exists: '/omd/sites/mysite/tmp/check_mk'
Feb 09 06:21:24 myserver systemd[1]: omd.service: Main process exited, code=exited, status=1/FAILURE
Feb 09 06:21:24 myserver systemd[1]: Failed to start Check_MK Monitoring.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Unit entered failed state.
Feb 09 06:21:24 myserver systemd[1]: omd.service: Failed with result 'exit-code'.
Thanks and kind regards
 Florian
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
Continue reading on narkive:
Loading...