Including 'sudo'

[Danilo Godec]

Hi,

I would like to monitor my Esos machine with Nagios / Icinga monitoring.
For the most part, that works, but some Nagios plug-ins have to run as
'root'. Since 'nrpe' refuses to run as root, one usually turns to 'sudo'.

So I think it would make sense to include 'sudo' as a standard - unless
there is an alternative I'm not aware of?



Danilo

[Marc Smith]

Sounds like a good addition; I should have this committed later tonight.


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Marc Smith]

Hi,

I was finally able to get to this... its been committed (r759) and the new package should post in about an hour. Let me know if there are any problems.

--Marc

[Patrick]

Hi everyone,

I'm not able to get working NRPE checks.
Whatever I do, I get one of those two messages:

storage01 sudo:   nagios : 3 incorrect password attempts ;
or
storage01 sudo:     root : account validation failure, is your account locked? ;

Even this isn't working:

[root@storage01 ~]# sudo -l
sudo: account validation failure, is your account locked?

I'm running Enterprise Storage OS master_fac1cba_qz 

What's wrong? Any ideas?

Regards
Patrick


[root@storage01 etc]# cat /etc/sudoers
## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias    WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users.  These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias    ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands.  Often used to group related commands together.
# Cmnd_Alias    PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
#                           /usr/bin/pkill, /usr/bin/top
# Cmnd_Alias    REBOOT = /sbin/halt, /sbin/reboot, /sbin/poweroff

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file.  Note that other programs use HOME to find
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods.  Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to use a hard-coded PATH instead of the user's to find commands
# Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
##
## Uncomment to send mail if the user does not enter the correct password.
# Defaults mail_badpass
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!REBOOT !log_output

##
## Runas alias specification
##

##
## User privilege specification
##
root ALL=(ALL) ALL
nagios ALL=(ALL) ALL
#nagios          ALL=(ALL) NOPASSWD: /usr/libexec/

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL) ALL

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw  # Ask for the password of the target user
# ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d





[root@storage01 etc]# cat /etc/nrpe.cfg
#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad (nag...@nagios.org)
#
# Last Modified: 11-23-2007
#
# NOTES:
# This is a sample configuration file for the NRPE daemon.  It needs to be
# located on the remote host that is running the NRPE daemon, not the host
# from which the check_nrpe client is being executed.
#############################################################################


# LOG FACILITY
# The syslog facility that should be used for logging purposes.

log_facility=daemon



# PID FILE
# The name of the file in which the NRPE daemon should write it's process ID
# number.  The file is only written if the NRPE daemon is started by the root
# user and is running in standalone mode.

pid_file=/var/run/nrpe.pid



# PORT NUMBER
# Port number we should wait for connections on.
# NOTE: This must be a non-priviledged port (i.e. > 1024).
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

server_port=5666



# SERVER ADDRESS
# Address that nrpe should bind to in case there are more than one interface
# and you do not want nrpe to bind on all interfaces.
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

#server_address=127.0.0.1



# NRPE USER
# This determines the effective user that the NRPE daemon should run as.
# You can either supply a username or a UID.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

nrpe_user=nagios



# NRPE GROUP
# This determines the effective group that the NRPE daemon should run as.
# You can either supply a group name or a GID.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

nrpe_group=nagios



# ALLOWED HOST ADDRESSES
# This is an optional comma-delimited list of IP address or hostnames
# that are allowed to talk to the NRPE daemon. Network addresses with a bit mask
# (i.e. 192.168.1.0/24) are also supported. Hostname wildcards are not currently
# supported.
#
# Note: The daemon only does rudimentary checking of the client's IP
# address.  I would highly recommend adding entries in your /etc/hosts.allow
# file to allow only the specified host to connect to the port
# you are running this daemon on.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

allowed_hosts=172.16.150.2



# COMMAND ARGUMENT PROCESSING
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments to commands that are executed.  This option only works
# if the daemon was configured with the --enable-command-args configure script
# option.
#
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow arguments, 1=allow command arguments

dont_blame_nrpe=0



# BASH COMMAND SUBTITUTION
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments that contain bash command substitutions of the form
# $(...).  This option only works if the daemon was configured with both
# the --enable-command-args and --enable-bash-command-substitution configure
# script options.
#
# *** ENABLING THIS OPTION IS A HIGH SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow bash command substitutions,
#         1=allow bash command substitutions

allow_bash_command_substitution=0



# COMMAND PREFIX
# This option allows you to prefix all commands with a user-defined string.
# A space is automatically added between the specified prefix string and the
# command line from the command definition.
#
# *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
# Usage scenario:
# Execute restricted commmands using sudo.  For this to work, you need to add
# the nagios user to your /etc/sudoers.  An example entry for alllowing
# execution of the plugins from might be:
#
# nagios          ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
#
# This lets the nagios user run all commands in that directory (and only them)
# without asking for a password.  If you do this, make sure you don't give
# random users write access to that directory or its contents!

command_prefix=/usr/bin/sudo



# DEBUGGING OPTION
# This option determines whether or not debugging messages are logged to the
# syslog facility.
# Values: 0=debugging off, 1=debugging on

debug=1



# COMMAND TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# allow plugins to finish executing before killing them off.

command_timeout=60



# CONNECTION TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# wait for a connection to be established before exiting. This is sometimes
# seen where a network problem stops the SSL being established even though
# all network sessions are connected. This causes the nrpe daemons to
# accumulate, eating system resources. Do not set this too low.

connection_timeout=300



# WEEK RANDOM SEED OPTION
# This directive allows you to use SSL even if your system does not have
# a /dev/random or /dev/urandom (on purpose or because the necessary patches
# were not applied). The random number generator will be seeded from a file
# which is either a file pointed to by the environment valiable $RANDFILE
# or $HOME/.rnd. If neither exists, the pseudo random number generator will
# be initialized and a warning will be issued.
# Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness

#allow_weak_random_seed=1



# INCLUDE CONFIG FILE
# This directive allows you to include definitions from an external config file.

#include=<somefile.cfg>



# INCLUDE CONFIG DIRECTORY
# This directive allows you to include definitions from config files (with a
# .cfg extension) in one or more directories (with recursion).

#include_dir=<somedirectory>
#include_dir=<someotherdirectory>



# COMMAND DEFINITIONS
# Command definitions that this daemon will run.  Definitions
# are in the following format:
#
# command[<command_name>]=<command_line>
#
# When the daemon receives a request to return the results of <command_name>
# it will execute the command specified by the <command_line> argument.
#
# Unlike Nagios, the command line cannot contain macros - it must be
# typed exactly as it should be executed.
#
# Note: Any plugins that are used in the command lines must reside
# on the machine that this daemon is running on!  The examples below
# assume that you have plugins installed in a /usr/local/nagios/libexec
# directory.  Also note that you will have to modify the definitions below
# to match the argument format the plugins expect.  Remember, these are
# examples only!


# The following examples use hardcoded command arguments...

command[check_users]=/usr/libexec/check_users -w 0 -c 1
command[check_load]=/usr/libexec/check_load -w 7.5,8.0,8.5 -c 8,8.5,9.0
command[check_disk]=/usr/libexec/check_disk -w 20% -c 10%
command[check_zombie_procs]=/usr/libexec/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=/usr/libexec/check_procs -w 150 -c 200
command[check_zpools]=/usr/libexec/check_zpools.sh -p ALL -w 60 -c 80
command[check_zpool_STORAGE01_MIRROR_POOL_062017]=/usr/libexec/check_zpools.sh -p STORAGE01_MIRROR_POOL_062017 -w 60 -c 80
command[check_ntp_time]=/usr/libexec/check_ntp_time -H nl.pool.ntp.org -w 0.5 -c 0.7 -t 60
command[check_raid]=/usr/libexec/check_raid.pl

[Marc Smith]

How about something like this for a resolution: https://superuser.com/questions/1413065/how-to-fix-sudo-account-validation-failure-is-your-account-locked

--Marc

--

You received this message because you are subscribed to the Google Groups "esos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/ca441916-042b-4050-8a60-1f0705684522n%40googlegroups.com.

[Patrick]

I don't have the file /etc/pam.d/sudo and the entries in /etc/shadow seem to be correct and well formatted.

[Marc Smith]

Hmm... I'm using a recent build from the 'master' branch I don't have
that same behavior:

[root@node-devel-2 ~]# sudo -l
User root may run the following commands on node-devel-2:
(ALL) ALL
[root@node-devel-2 ~]#

[root@node-devel-2 ~]# sudo ls -ltrd /root/.ssh
drwxr-xr-x 1 root root 120 Feb 10 15:54 /root/.ssh
[root@node-devel-2 ~]#

Commit fac1cba1950c8297faf47a03b3b0fe99acbc09a8 is from 2019.

Maybe try a fresh install of the latest ESOS 'master' build on a new
machine and see if it behaves the same way?

--Marc

> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/e3d8eaea-1a26-4e43-839c-6b5d275efdadn%40googlegroups.com.

[Patrick]

I have the same issue on 3.0.6 on a testing machine

[Marc Smith]

How about the latest 'master' build?

> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/199d4813-eaf3-4bab-ad11-b965e47a2e1fn%40googlegroups.com.

[Patrick]

Same with latest master build.

[Patrick]

So the problem occurs on

3.0.6 - pre compiled, from website

3.0.6 - self compiled with zq option

master (83ad0b4_zq) - self compiled with zq option

[Patrick]

Any news on this?

[Patrick]

...

[Marc Smith]

What happens if you create a '/etc/pam.d/sudo' file that looks like this:

[root@localhost ~]# cat /etc/pam.d/sudo
# Begin /etc/pam.d/sudo

auth        include        system-auth
account     include        system-account
password    include        system-password
session     include        system-session

# End /etc/pam.d/sudo
[root@localhost ~]#

Does it work then?

--Marc

To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/b65a0c0f-1099-4fb9-9ae5-c60b8d69d133n%40googlegroups.com.

[Tyler Trafford]

For others looking to add accounts,

Marc's solution of adding '/etc/pam.d/sudo' and populating it as shown above works.