[4.2.0]Unable to get process status (vserver based) help ple

[justroot]

Hey Forum,
I have the problem that I get the error :
unable to get process status.

If I try to access services:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

All the normal fixes are not working, I think it is because It runs on an Ubuntu 16.04 vserver(cant afford more), is there any solution to fix this? I tried about 2 weeks now, I cant find anything, maybe you guys the pros know something.

Thanks in advance to anybody even just reading this.
Felix

[rkennedy]

What instructions did you follow to install Core?

It may be quicker to start with a clean, minimal Ubuntu 16 install, and start from scratch with our official instructions - https://support.nagios.com/kb/article.p ... ategory=58

[justroot]

Ok! I will try that and come back to you, thanks!

[rkennedy]

Sounds good - let us know how they go or if you run into any other problems with it!

[justroot]

Okay, so I followed the instruction 1 to 1, and still get the Unable to get process status.
If you wanna take a look at it: www.justroot.de/nagios
user: nagiosadmin
pw: nagiosadmin

I had no errors or such things.

regards Felix

[rkennedy]

Can you show us copy of your apache logs? /var/log/httpd/*_log will help. From there, what is the output of getenforce?

Lastly, what are the permissions of the folder? ls -la /usr/local/nagios/var/

[justroot]

All Logs are attached.

Getenforce:

Code: Select all

root@v462xx:/tmp/nagios-plugins-release-2.1.3#
root@v462xx:/tmp/nagios-plugins-release-2.1.3# getenforce
bash: getenforce: command not found

Permissions:

Code: Select all

root@v462xx:/tmp/nagios-plugins-release-2.1.3# ls -la /usr/local/nagios/var/
total 100
drwxrwxr-x 5 nagios nagios  4096 Feb  7 20:17 .
drwxr-xr-x 8 root   root    4096 Feb  7 17:24 ..
drwxrwxr-x 2 nagios nagios  4096 Feb  7 17:24 archives
-rw-r--r-- 1 nagios nagios    34 Feb  7 17:25 nagios.configtest
-rw-r--r-- 1 nagios nagios     6 Feb  7 17:25 nagios.lock
-rw-r--r-- 1 nagios nagios  7259 Feb  7 19:33 nagios.log
-rw-r--r-- 1 nagios nagios 12655 Feb  7 17:25 objects.cache
-rw-r--r-- 1 nagios nagios 12655 Feb  7 17:25 objects.precache
-rw------- 1 nagios nagios 13146 Feb  7 19:25 retention.dat
drwxrwsr-x 2 nagios nagios  4096 Feb  7 17:25 rw
drwxr-xr-x 3 root   root    4096 Feb  7 17:24 spool
-rw-rw-r-- 1 nagios nagios 13580 Feb  7 20:17 status.dat
root@v462xx:/tmp/nagios-plugins-release-2.1.3#

[rkennedy]

This looks standard.

Can you also post your /etc/sudoers and /etc/group files for us to review?

[justroot]

/etc/sudoers:

Code: Select all

root@v462cc:/home/justroot# cat /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults        env_reset
Defaults        mail_badpass
Defaults        secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root    ALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d

/etc/group:

Code: Select all

root@v462xx:/home/justroot# cat /etc/group
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:
floppy:x:25:
tape:x:26:
sudo:x:27:
audio:x:29:
dip:x:30:
www-data:x:33:www-data
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
netdev:x:101:
input:x:102:
systemd-journal:x:103:
systemd-timesync:x:104:
systemd-network:x:105:
systemd-resolve:x:106:
systemd-bus-proxy:x:107:
crontab:x:108:
uuidd:x:109:
sambashare:x:110:
syslog:x:111:
mlocate:x:112:
ssh:x:113:
bind:x:114:
ssl-cert:x:115:
postfix:x:116:
postdrop:x:117:
mysql:x:118:
psaadm:x:1000:psaadm,sw-cp-server
swkey-data:x:1001:psaadm
popuser:x:31:
psaserv:x:1002:psaadm,psaftp,www-data,nginx
psacln:x:1003:
sw-cp-server:x:999:sw-cp-server
lock-manager:x:998:psaadm
dovecot:x:1004:
dovenull:x:1005:
roundcube_sysgroup:x:1006:
horde_sysgroup:x:1007:
nginx:x:997:nginx
messagebus:x:119:
psaftp:x:1008:psaftp
psasb:x:1009:psaadm,www-data
debian-spamd:x:120:
justroot:x:10003:
nagios:x:10006:www-data
root@v462xx:/home/justroot#

regards and thanks
Felix

[rkennedy]

Do you have plesk running on this same machine? My guess is there could be some custom nginx / apache settings configured, which would definitely affect Nagios. I wasn't able to get anything specific out of your log files, either. The sudoers file looks fine, and the groups look fine as well.

The one thing that might help is adding the nagios user to the www-data group.