nagios service issue
Re: nagios service issue
they won't support for this. That is the problem. Also they will tell us to contact Nagios team for this type of issue. They will tell as per policy we won't support this tool. Hence they give us for root access.
Re: nagios service issue
Hi,
Thanks for the support. Now I am able to install nagios in linux system and got message install completed.
After installation I am facing Monitor engine service issue and it is showing "No lock file found". Please check and suggest us.
Also attached install log file for reference and also I am able to download Profile file from Admin-system profile-Download profile.
[root@bhusprv024 lib]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 12 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 5 contacts.
Checked 2 contact groups.
Checked 124 commands.
Checked 11 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 11 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 0
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check
[root@bhusprv024 lib]# systemctl status nagios.service
● nagios.service - Nagios
Loaded: loaded (/etc/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2017-05-12 19:57:06 EDT; 11h ago
Main PID: 18590 (nagios)
CGroup: /system.slice/nagios.service
├─18590 /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
├─18592 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18593 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18594 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18595 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18596 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18597 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
└─18604 /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
May 13 06:51:04 bhusprv024.bhprod.ibm.com sudo[9513]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
May 13 06:55:03 bhusprv024.bhprod.ibm.com sudo[10890]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status crond
May 13 06:55:38 bhusprv024.bhprod.ibm.com sudo[11002]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status httpd
May 13 06:55:45 bhusprv024.bhprod.ibm.com sudo[11062]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status mysqld
May 13 06:56:04 bhusprv024.bhprod.ibm.com sudo[11526]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
May 13 06:57:05 bhusprv024.bhprod.ibm.com nagios[18590]: Auto-save of retention data completed successfully.
May 13 07:00:03 bhusprv024.bhprod.ibm.com sudo[12980]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status crond
May 13 07:00:38 bhusprv024.bhprod.ibm.com sudo[13091]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status httpd
May 13 07:00:45 bhusprv024.bhprod.ibm.com sudo[13151]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status mysqld
May 13 07:01:04 bhusprv024.bhprod.ibm.com sudo[13398]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
[root@bhusprv024 lib]# journalctl -n
-- Logs begin at Tue 2017-05-09 23:15:08 EDT, end at Sat 2017-05-13 07:03:01 EDT. --
May 13 07:03:01 bhusprv024.bhprod.ibm.com systemd[1]: Starting Session 44889 of user nagios.
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13947]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php >> /usr/local/nagiosxi/var/cmdsubsys.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13949]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/nom.php >> /usr/local/nagiosxi/var/nom.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13952]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php >> /usr/local/nagiosxi/var/perfdataproc.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13953]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php >> /usr/local/nagiosxi/var/feedproc.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13954]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/var/eventman.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13951]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cleaner.php >> /usr/local/nagiosxi/var/cleaner.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13961]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/reportengine.php >> /usr/local/nagiosxi/var/reportengine.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13962]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php >> /usr/local/nagiosxi/var/event_handler.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13959]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1)
Thanks for the support. Now I am able to install nagios in linux system and got message install completed.
After installation I am facing Monitor engine service issue and it is showing "No lock file found". Please check and suggest us.
Also attached install log file for reference and also I am able to download Profile file from Admin-system profile-Download profile.
[root@bhusprv024 lib]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 12 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 5 contacts.
Checked 2 contact groups.
Checked 124 commands.
Checked 11 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 11 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 0
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check
[root@bhusprv024 lib]# systemctl status nagios.service
● nagios.service - Nagios
Loaded: loaded (/etc/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2017-05-12 19:57:06 EDT; 11h ago
Main PID: 18590 (nagios)
CGroup: /system.slice/nagios.service
├─18590 /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
├─18592 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18593 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18594 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18595 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18596 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─18597 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
└─18604 /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
May 13 06:51:04 bhusprv024.bhprod.ibm.com sudo[9513]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
May 13 06:55:03 bhusprv024.bhprod.ibm.com sudo[10890]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status crond
May 13 06:55:38 bhusprv024.bhprod.ibm.com sudo[11002]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status httpd
May 13 06:55:45 bhusprv024.bhprod.ibm.com sudo[11062]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status mysqld
May 13 06:56:04 bhusprv024.bhprod.ibm.com sudo[11526]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
May 13 06:57:05 bhusprv024.bhprod.ibm.com nagios[18590]: Auto-save of retention data completed successfully.
May 13 07:00:03 bhusprv024.bhprod.ibm.com sudo[12980]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status crond
May 13 07:00:38 bhusprv024.bhprod.ibm.com sudo[13091]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status httpd
May 13 07:00:45 bhusprv024.bhprod.ibm.com sudo[13151]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status mysqld
May 13 07:01:04 bhusprv024.bhprod.ibm.com sudo[13398]: nagios : TTY=unknown ; PWD=/tmp ; USER=root ; COMMAND=/usr/local/nagiosxi/scripts/manage_services.sh status ndo2db
[root@bhusprv024 lib]# journalctl -n
-- Logs begin at Tue 2017-05-09 23:15:08 EDT, end at Sat 2017-05-13 07:03:01 EDT. --
May 13 07:03:01 bhusprv024.bhprod.ibm.com systemd[1]: Starting Session 44889 of user nagios.
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13947]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php >> /usr/local/nagiosxi/var/cmdsubsys.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13949]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/nom.php >> /usr/local/nagiosxi/var/nom.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13952]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php >> /usr/local/nagiosxi/var/perfdataproc.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13953]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php >> /usr/local/nagiosxi/var/feedproc.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13954]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/var/eventman.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13951]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/cleaner.php >> /usr/local/nagiosxi/var/cleaner.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13961]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/reportengine.php >> /usr/local/nagiosxi/var/reportengine.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13962]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/event_handler.php >> /usr/local/nagiosxi/var/event_handler.log 2>&1)
May 13 07:03:01 bhusprv024.bhprod.ibm.com CROND[13959]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1)
You do not have the required permissions to view the files attached to this post.
Re: nagios service issue
Attached Monitor Engine error screen shot.
You do not have the required permissions to view the files attached to this post.
Re: nagios service issue
Let's get some file/directory listings. Please send the output of the following commands:
Code: Select all
ls -l /usr/local/nagios/
ls -l /usr/local/nagios/varFormer Nagios employee
Re: nagios service issue
Please find the command output details.
Code: Select all
[root@bhusprv024 ~]#
[root@bhusprv024 ~]# ls -l /usr/local/nagios/
total 28
drwxrwxr-x 2 nagios nagios 4096 May 12 19:09 bin
drwsrwsr-x 7 apache nagios 4096 May 12 19:36 etc
drwxr-xr-x 2 root users 4096 May 12 19:08 include
drwxrwsr-x 2 apache nagios 4096 May 12 19:11 libexec
drwxrwxr-x 2 nagios nagios 4096 May 12 19:07 sbin
drwxrwxr-x 18 nagios nagios 4096 May 12 19:09 share
drwxrwxr-x 6 nagios nagios 4096 May 15 12:36 var
[root@bhusprv024 ~]#
[root@bhusprv024 ~]# ls -l /usr/local/nagios/var
total 184
drwxrwxr-x 2 nagios nagios 4096 May 14 23:59 archives
-rw-r--r-- 1 nagios nagios 0 May 15 12:36 host-perfdata
-rw-r--r-- 1 nagios nagios 34 May 14 19:17 nagios.configtest
-rw------- 1 nagios nagios 8381 May 15 11:48 nagios.log
-rw-r--r-- 1 nagios nagios 5 May 12 19:14 ndo2db.lock
-rw-r--r-- 1 nagios nagios 0 May 15 06:48 ndomod.tmp
srwxr-xr-x 1 nagios nagios 0 May 12 19:14 ndo.sock
-rw-r--r-- 1 nagios nagios 234 May 12 19:14 npcd.log
-rw-r--r-- 1 nagios nagios 37056 May 15 06:48 objects.cache
-rw-r--r-- 1 nagios nagios 35133 May 14 19:17 objects.precache
-rw------- 1 nagios nagios 29805 May 15 11:48 retention.dat
drwxrwsr-x 2 nagios nagcmd 4096 May 15 06:48 rw
-rw-r--r-- 1 nagios nagios 438 May 15 12:36 service-perfdata
drwxr-xr-x 5 nagios nagios 4096 May 12 19:07 spool
drwxr-xr-x 2 nagios nagios 4096 May 15 12:36 stats
-rw-rw-r-- 1 nagios nagios 30259 May 15 12:36 status.dat
[root@bhusprv024 ~]#
Last edited by tmcdonald on Mon May 15, 2017 11:41 am, edited 1 time in total.
Reason: Please use [code][/code] tags around terminal output
Reason: Please use [code][/code] tags around terminal output
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: nagios service issue
What's the output of the following:
?
Also, can you attach the present sudoers file?
Code: Select all
ll /usr/local/nagios/bin/nagios
ll /usr/local/nagios/var/rw
sestatus
Also, can you attach the present sudoers file?
Re: nagios service issue
find command output below.
[root@bhusprv024 local]# ll /usr/local/nagios/bin/nagios
-rwxrwxr-- 1 nagios nagios 692656 May 12 19:07 /usr/local/nagios/bin/nagios
[root@bhusprv024 local]# ll /usr/local/nagios/var/rw
total 0
prw-rw---- 1 nagios nagcmd 0 May 12 19:14 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 May 15 14:43 nagios.qh
[root@bhusprv024 local]#
[root@bhusprv024 local]# ll /usr/local/nagios/bin/nagios
-rwxrwxr-- 1 nagios nagios 692656 May 12 19:07 /usr/local/nagios/bin/nagios
[root@bhusprv024 local]# ll /usr/local/nagios/var/rw
total 0
prw-rw---- 1 nagios nagcmd 0 May 12 19:14 nagios.cmd
srw-rw---- 1 nagios nagcmd 0 May 15 14:43 nagios.qh
[root@bhusprv024 local]#
Re: nagios service issue
Also find present sudoers file detail below.
Code: Select all
[root@bhusprv024 etc]# cat sudoers
## Sudoers allows particular users to run various commands as
## the root user, without needing the root password.
##
## Examples are provided at the bottom of the file for collections
## of related commands, which can then be delegated out to particular
## users or groups.
##
## This file must be edited with the 'visudo' command.
## Host Aliases
## Groups of machines. You may prefer to use hostnames (perhaps using
## wildcards for entire domains) or IP addresses instead.
# Host_Alias FILESERVERS = fs1, fs2
# Host_Alias MAILSERVERS = smtp, smtp2
## User Aliases
## These aren't often necessary, as you can use regular groups
## (ie, from files, LDAP, NIS, etc) in this file - just use %groupname
## rather than USERALIAS
# User_Alias ADMINS = jsmith, mikem
## Command Aliases
## These are groups of related commands...
## Networking
# Cmnd_Alias NETWORKING = /sbin/route, /sbin/ifconfig, /bin/ping, /sbin/dhclient, /usr/bin/net, /sbin/iptables, /usr/bin/rfcomm, /usr/bin/wvdial, /sbin/iwconfig, /sbin/mii-tool
## Installation and management of software
# Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum
## Services
# Cmnd_Alias SERVICES = /sbin/service, /sbin/chkconfig, /usr/bin/systemctl start, /usr/bin/systemctl stop, /usr/bin/systemctl reload, /usr/bin/systemctl restart, /usr/bin/systemctl status, /usr/bin/systemctl enable, /usr/bin/systemctl disable
## Updating the locate database
# Cmnd_Alias LOCATE = /usr/bin/updatedb
## Storage
# Cmnd_Alias STORAGE = /sbin/fdisk, /sbin/sfdisk, /sbin/parted, /sbin/partprobe, /bin/mount, /bin/umount
## Delegating permissions
# Cmnd_Alias DELEGATING = /usr/sbin/visudo, /bin/chown, /bin/chmod, /bin/chgrp
## Processes
# Cmnd_Alias PROCESSES = /bin/nice, /bin/kill, /usr/bin/kill, /usr/bin/killall
## Drivers
# Cmnd_Alias DRIVERS = /sbin/modprobe
# Defaults specification
#
# Disable "ssh hostname sudo <cmd>", because it will show the password in clear.
# You have to run "ssh -t hostname sudo <cmd>".
#
#Defaults requiretty
#
# Refuse to run if unable to disable echo on the tty. This setting should also be
# changed in order to be able to use sudo without a tty. See requiretty above.
#
Defaults !visiblepw
#
# Preserving HOME has security implications since many programs
# use it when searching for configuration files. Note that HOME
# is already set when the the env_reset option is enabled, so
# this option is only effective for configurations where either
# env_reset is disabled or HOME is present in the env_keep list.
#
Defaults always_set_home
Defaults env_reset
Defaults env_keep = "COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS"
Defaults env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaults env_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES"
Defaults env_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaults env_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"
#
# Adding HOME to env_keep may enable a user to run unrestricted
# commands via sudo.
#
# Defaults env_keep += "HOME"
Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin
## Next comes the main part: which users can run what software on
## which machines (the sudoers file can be shared between multiple
## systems).
## Syntax:
##
## user MACHINE=COMMANDS
##
## The COMMANDS section may have other options added to it.
##
## Allow root to run any commands anywhere
root ALL=(ALL) ALL
## Allows members of the 'sys' group to run networking, software,
## service management apps and more.
# %sys ALL = NETWORKING, SOFTWARE, SERVICES, STORAGE, DELEGATING, PROCESSES, LOCATE, DRIVERS
## Allows people in group wheel to run all commands
%wheel ALL=(ALL) ALL
## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
## Allows members of the users group to mount and unmount the
## cdrom as root
# %users ALL=/sbin/mount /mnt/cdrom, /sbin/umount /mnt/cdrom
## Allows members of the users group to shutdown this system
# %users localhost=/sbin/shutdown -h now
## Read drop-in files from /etc/sudoers.d (the # here does not mean a comment)
#includedir /etc/sudoers.d
User_Alias NAGIOSXI=nagios
User_Alias NAGIOSXIWEB=apache
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios start
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios stop
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios restart
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios reload
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios status
NAGIOSXI ALL = NOPASSWD:/etc/init.d/nagios checkconfig
NAGIOSXI ALL = NOPASSWD:/etc/init.d/ndo2db start
NAGIOSXI ALL = NOPASSWD:/etc/init.d/ndo2db stop
NAGIOSXI ALL = NOPASSWD:/etc/init.d/ndo2db restart
NAGIOSXI ALL = NOPASSWD:/etc/init.d/ndo2db reload
NAGIOSXI ALL = NOPASSWD:/etc/init.d/ndo2db status
NAGIOSXI ALL = NOPASSWD:/etc/init.d/npcd start
NAGIOSXI ALL = NOPASSWD:/etc/init.d/npcd stop
NAGIOSXI ALL = NOPASSWD:/etc/init.d/npcd restart
NAGIOSXI ALL = NOPASSWD:/etc/init.d/npcd reload
NAGIOSXI ALL = NOPASSWD:/etc/init.d/npcd status
NAGIOSXI ALL = NOPASSWD:/usr/bin/php /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php *
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/html/includes/components/profile/getprofile.sh
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/scripts/upgrade_to_latest.sh
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/scripts/change_timezone.sh
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/scripts/manage_services.sh *
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/scripts/reset_config_perms.sh
NAGIOSXI ALL = NOPASSWD:/usr/local/nagiosxi/scripts/backup_xi.sh *
NAGIOSXIWEB ALL = NOPASSWD:/usr/bin/tail -100 /var/log/messages
NAGIOSXIWEB ALL = NOPASSWD:/usr/bin/tail -100 /var/log/httpd/error_log
NAGIOSXIWEB ALL = NOPASSWD:/usr/bin/tail -100 /var/log/mysqld.log
NAGIOSXIWEB ALL = NOPASSWD:/usr/bin/php /usr/local/nagiosxi/html/includes/components/autodiscovery/scripts/autodiscover_new.php *
NAGIOSXIWEB ALL = NOPASSWD:/usr/local/nagiosxi/html/includes/components/profile/getprofile.sh
NAGIOSXIWEB ALL = NOPASSWD:/etc/init.d/snmptt restart
NAGIOSXIWEB ALL = NOPASSWD:/usr/local/nagiosxi/scripts/repair_databases.sh
NAGIOSXIWEB ALL = NOPASSWD:/usr/local/nagiosxi/scripts/manage_services.sh *
[root@bhusprv024 etc]#
Last edited by dwhitfield on Mon May 15, 2017 3:25 pm, edited 1 time in total.
Reason: code blocks FTW!
Reason: code blocks FTW!
-
dwhitfield
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: nagios service issue
First off, it doesn't look like I got the output of sestatus. Are you back in enforcing?
Otherwise, that all looks good to me. Have you had a quickstart yet? https://www.nagios.com/services/quickstart/nagios-xi/ It might be easiest if one of us actually takes a look at the server.
Otherwise, that all looks good to me. Have you had a quickstart yet? https://www.nagios.com/services/quickstart/nagios-xi/ It might be easiest if one of us actually takes a look at the server.
Re: nagios service issue
In addition to what @dwhitfield said, try and restart the daemons and see if the nagios lock file is created which will show the status that it is running.
Login as root to the server and run the following.
Wait a few minutes before logging in to the GUI to see if the status shows that the nagios process is running.
It it is not, run the following and post the output.
ps -ef --cols=300
Also, attach the following file to this post
/etc/init.d/nagios
Login as root to the server and run the following.
Code: Select all
service nagios stop
killall -9 nagios
service httpd restart
service nagios startIt it is not, run the following and post the output.
ps -ef --cols=300
Also, attach the following file to this post
/etc/init.d/nagios
Be sure to check out our Knowledgebase for helpful articles and solutions!