When installing nagios 2.4 the apache user isn't added to the nagios group when using the '-noweb' flag. This means that the config files located in /etc/nagios and the logs located in /var/nagios are unreadable by the cgi processes running via apache. This means that you *always* get an error, even with a correctly configured setup. We need to change the following: if use noweb; then enewuser nagios -1 /bin/bash /dev/null nagios else enewuser nagios -1 /bin/bash /dev/null nagios,apache fi To be: enewuser nagios -1 /bin/bash /dev/null nagios if ! use noweb; then usermod -a -G nagios apache fi
or the other fix would be to change the ownership of /etc/nagios to be nagios:apache. you could use the following for that: enewuser nagios -1 /bin/bash /dev/null nagios if ! use noweb; then chown -R nagios:apache ${D}/etc/nagios || die "Failed Chown of ${D}/etc/nagios" fi
*** This bug has been marked as a duplicate of 134344 ***
