Bug 48885 - Nagios fails to start on Slave/Member
Nagios fails to start on Slave/Member
Status: NEW
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-03-06 18:05 CET by Philipp Hahn
Modified: 2019-04-16 15:03 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.017
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2019-03-06 18:05:50 CET
Nagios can be installed directly from installer. Afterwards it fails to start automatically:

/var/log/univention/updater.log:
...
univention-nagios-server (12.0.1-4A~4.4.0.201902041533) wird eingerichtet ...
...
Restarting univention-directory-listener (via systemctl): univention-directory-listener.service.
apache2_invoke nagios: already enabled
Job for nagios.service failed because the control process exited with error code.
See "systemctl status nagios.service" and "journalctl -xe" for details.
...


# systemctl status nagios.service
● nagios.service - LSB: nagios host/service/network monitoring and management system
   Loaded: loaded (/etc/init.d/nagios; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-03-06 16:43:10 CET; 1h 21min ago
     Docs: man:systemd-sysv-generator(8)
      CPU: 112ms

Mär 06 16:43:10 member nagios[24992]: Total Errors:   2
Mär 06 16:43:10 member nagios[24992]: ***> One or more problems was encountered while running the pre-flight check...
Mär 06 16:43:10 member nagios[24992]:      Check your configuration file(s) to ensure that they contain valid
Mär 06 16:43:10 member nagios[24992]:      directives and data definitions.  If you are upgrading from a previous
Mär 06 16:43:10 member nagios[24992]:      version of Nagios, you should be aware that some variables/definitions
Mär 06 16:43:10 member nagios[24992]:      may have been removed or modified in this version.  Make sure to read
Mär 06 16:43:10 member nagios[24992]:      the HTML documentation regarding the config files, as well as the
Mär 06 16:43:10 member nagios[24992]:      'Whats New' section to find out what has changed.
Mär 06 16:43:10 member nagios[24992]: errors in config! ... failed!
Mär 06 16:43:10 member nagios[24992]:  failed!


# journalctl -xe -u nagios.service
Mär 06 16:43:10 member nagios[24992]:    Read object config files okay...
Mär 06 16:43:10 member nagios[24992]: Running pre-flight check on configuration data...
Mär 06 16:43:10 member nagios[24992]: Checking objects...
Mär 06 16:43:10 member nagios[24992]: Error: Service check command 'check_univention_ad_connector' specified in service 'UNIVENTION_ADCONNECTOR' for host 'backup.pt44.pmh' not defined anywhere!
Mär 06 16:43:10 member nagios[24992]: Error: Service check command 'check_univention_ad_connector' specified in service 'UNIVENTION_ADCONNECTOR' for host 'master.pt44.pmh' not defined anywhere!
Mär 06 16:43:10 member nagios[24992]:         Checked 75 services.
Mär 06 16:43:10 member nagios[24992]:         Checked 4 hosts.
Mär 06 16:43:10 member nagios[24992]:         Checked 2 host groups.
Mär 06 16:43:10 member nagios[24992]:         Checked 0 service groups.
Mär 06 16:43:10 member nagios[24992]:         Checked 1 contacts.
Mär 06 16:43:10 member nagios[24992]:         Checked 4 contact groups.
Mär 06 16:43:10 member nagios[24992]:         Checked 190 commands.
Mär 06 16:43:10 member nagios[24992]:         Checked 4 time periods.
Mär 06 16:43:10 member nagios[24992]:         Checked 0 host escalations.
Mär 06 16:43:10 member nagios[24992]:         Checked 0 service escalations.
Mär 06 16:43:10 member nagios[24992]: Checking for circular paths...
Mär 06 16:43:10 member nagios[24992]:         Checked 4 hosts
Mär 06 16:43:10 member nagios[24992]:         Checked 0 service dependencies
Mär 06 16:43:10 member nagios[24992]:         Checked 0 host dependencies
Mär 06 16:43:10 member nagios[24992]:         Checked 4 timeperiods
Mär 06 16:43:10 member nagios[24992]: Checking global event handlers...
Mär 06 16:43:10 member nagios[24992]: Checking obsessive compulsive processor commands...
Mär 06 16:43:10 member nagios[24992]: Checking misc settings...
Mär 06 16:43:10 member nagios[24992]: Total Warnings: 0
Mär 06 16:43:10 member nagios[24992]: Total Errors:   2
Mär 06 16:43:10 member nagios[24992]: ***> One or more problems was encountered while running the pre-flight check...
Mär 06 16:43:10 member nagios[24992]:      Check your configuration file(s) to ensure that they contain valid
Mär 06 16:43:10 member nagios[24992]:      directives and data definitions.  If you are upgrading from a previous
Mär 06 16:43:10 member nagios[24992]:      version of Nagios, you should be aware that some variables/definitions
Mär 06 16:43:10 member nagios[24992]:      may have been removed or modified in this version.  Make sure to read
Mär 06 16:43:10 member nagios[24992]:      the HTML documentation regarding the config files, as well as the
Mär 06 16:43:10 member nagios[24992]:      'Whats New' section to find out what has changed.
Mär 06 16:43:10 member nagios[24992]: errors in config! ... failed!
Mär 06 16:43:10 member nagios[24992]:  failed!