Page 1 of 1
FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Error
Posted: Tue Jul 10, 2018 3:49 pm
by rbond
Hi. I tried to upgrade using the upgrade script. all i entered in was the ./upgrade command from the install directory. When testing, all i saw was a partial welcome screen with missing graphics and only a little text. When i tried to continue to the login screen got the HTTP ERROR 500 notice. It looks like the upgrade script needs to set the directory permissions or just not change them as it changed the permissions to root and the root group which locked out the nagios user and groups so apache could no longer read from those directories. I just fixed that by hand and appears to work now.
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 10, 2018 3:52 pm
by scottwilkerson
rbond wrote:Hi. I tried to upgrade using the upgrade script. all i entered in was the ./upgrade command from the install directory. When testing, all i saw was a partial welcome screen with missing graphics and only a little text. When i tried to continue to the login screen got the HTTP ERROR 500 notice. It looks like the upgrade script needs to set the directory permissions or just not change them as it changed the permissions to root and the root group which locked out the nagios user and groups so apache could no longer read from those directories. I just fixed that by hand and appears to work now.
This is the first we have heard of this. I'm glad you have it fixed. Does your system use a custom umask?
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 6:07 am
by junkertf
Hello, what diretory permission you've changed?
Same error still exist on upgrade to 5.5.1.
Thanks,
Ferenc
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 7:59 am
by rbond
Hi. In my case it was the nagios directories themselves as i noticed that the nagios id no longer had permissions. But in my case, I have to run from linked directories as the default setup would not work due to lack of space in /usr/local (we cannot control some platform filesystem specs where i work so we have to link). I stopped all services related to nagios and apache, reassigned the owner back to nagios:nagios on its core directories (nagios, nagiosxi, nrdp et al...), restarted the services and all was well.
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 10:10 am
by jomann
Most of the nagios directories get overwritten on upgrades. Did changing the permissions on the links fix this issue?
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 11:12 am
by vAJ
I've just upgraded my test box from 5.4.13 to 5.5.1 and get the 500.
Code: Select all
drwxr-xr-x. 2 root root 4096 Jul 17 11:59 bin
drwxr-xr-x. 2 root root 4096 Dec 14 2017 etc
drwxr-xr-x. 2 root root 4096 Dec 14 2017 games
drwxr-xr-x. 3 root root 4096 Jul 17 11:59 include
drwxr-xr-x. 3 root root 4096 Jul 17 11:59 lib
drwxr-xr-x. 3 root root 4096 Dec 14 2017 lib64
drwxr-xr-x. 2 root root 4096 Dec 14 2017 libexec
drwxr-xr-x 13 nagios nagios 4096 Jun 26 2017 nagios
drwxr-xr-x 6 nagios nagios 4096 Oct 15 2015 nagiosmobile
lrwxrwxrwx 1 nagios nagios 26 Jun 26 2017 nagiosxi -> /usr/local/nagios/nagiosxi
drwxr-xr-x 5 apache apache 4096 Jul 17 11:48 nagvis
drwxr-xr-x 5 apache apache 4096 Oct 15 2015 nagvis.old-2018-07-17_11:48:28
drwxr-xr-x 7 nagios nagios 4096 Jul 17 11:27 ncpa
drwxr-xr-x 7 nagios nagios 4096 Jul 17 11:58 nrdp
drwxr-xr-x 3 root root 4096 Sep 27 2016 nsis
drwxr-xr-x. 2 root root 4096 Dec 14 2017 sbin
drwxr-xr-x. 6 root root 4096 Dec 14 2017 share
drwxr-xr-x. 2 root root 4096 Dec 14 2017 src
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 11:51 am
by vAJ
For me, it was only /usr/local/nagios/nagiosxi that was root:root.
Fixed with
Code: Select all
chown -R nagios:nagios /usr/local/nagios/nagiosxi
Re: FYI Upgrade to XI 5.5.0 from 5.4.13 HTTP 500 Server Erro
Posted: Tue Jul 17, 2018 3:15 pm
by lmiltchev
@rbond, do you have any more questions/comments? Is it ok to close this topic now since your issue has been resolved?