Nagios Support Forum

Posted: **Wed Mar 20, 2019 4:20 pm**

Ran a yum update, and now nagios wont start, reason it cites is:

Error: Unable to write to check_result_path ('/usr/local/nagios/var/spool/checkresults') - Read-only file system

I've checked that path, nagios can write to every directory. I've used

Code: Select all

su - nagios

to see if I could touch a file in that path as the nagios user, and it created just fine.

This instance was working fine before, any idea what's broke?
Here's everything from the journal -xe command should it be needed:

Code: Select all

-- Unit nagios.service has begun starting up.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Nagios Core 4.3.4
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Copyright (c) 1999-2009 Ethan Galstad
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Last Modified: 2017-08-24
Mar 20 17:11:09 nagios.domain.com nagios[24821]: License: GPL
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Website: https://www.nagios.org
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Reading configuration data...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Read main config file okay...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Read object config files okay...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Running pre-flight check on configuration data...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checking objects...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 2257 services.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 199 hosts.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 79 host groups.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 81 service groups.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 12 contacts.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 0 contact groups.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 121 commands.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 185 time periods.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 0 host escalations.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 0 service escalations.
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checking for circular paths...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 199 hosts
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 0 service dependencies
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 0 host dependencies
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checked 185 timeperiods
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checking global event handlers...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checking obsessive compulsive processor commands...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Checking misc settings...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Error: Unable to write to check_result_path ('/usr/local/nagios/var/spool/checkresults') - Read-only file system
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Total Warnings: 0
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Total Errors:   1
Mar 20 17:11:09 nagios.domain.com nagios[24821]: ***> One or more problems was encountered while running the pre-flight check...
Mar 20 17:11:09 nagios.domain.com nagios[24821]: Check your configuration file(s) to ensure that they contain valid
Mar 20 17:11:09 nagios.domain.com nagios[24821]: directives and data definitions.  If you are upgrading from a previous
Mar 20 17:11:09 nagios.domain.com nagios[24821]: version of Nagios, you should be aware that some variables/definitions
Mar 20 17:11:09 nagios.domain.com nagios[24821]: may have been removed or modified in this version.  Make sure to read
Mar 20 17:11:09 nagios.domain.com nagios[24821]: the HTML documentation regarding the config files, as well as the
Mar 20 17:11:09 nagios.domain.com nagios[24821]: 'Whats New' section to find out what has changed.
Mar 20 17:11:09 nagios.domain.com systemd[1]: nagios.service: control process exited, code=exited status=1
Mar 20 17:11:09 nagios.domain.com systemd[1]: Failed to start Nagios Network Monitoring.
-- Subject: Unit nagios.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nagios.service has failed.
--
-- The result is failed.
Mar 20 17:11:09 nagios.domain.com systemd[1]: Unit nagios.service entered failed state.
Mar 20 17:11:09 nagios.domain.com systemd[1]: nagios.service failed.

Posted: **Thu Mar 21, 2019 2:17 pm**

What OS and version of that OS are being used on this machine? Sounds like one of your mounts is set to read-only for one reason or another.

What is the output of the following command, executed from the CLI of your Nagios Core machine:

Code: Select all

cat /proc/mounts

Posted: **Thu Mar 21, 2019 4:46 pm**

+1 on getting the output of the /procs/mounts file.

Nagios Support Forum

Nagios Thinks check_results_path is read-only

Nagios Thinks check_results_path is read-only

Re: Nagios Thinks check_results_path is read-only

Re: Nagios Thinks check_results_path is read-only