successful installation yet only 404 errors

Information and discussions relating to the Nagios Mobile addon.

successful installation yet only 404 errors

Postby canyonbakehouse » Mon Mar 19, 2018 4:36 pm

Hello,

Within this month I've installed Nagios Core on a Ubuntu Server VM in ESXI. The Core install went fine and the web interface (http://.../nagios) works yet I'm unable to get NagiosMobile working. I followed these instructions (https://goo.gl/19DQss) in the official Nagios Mobile PDF, ensuring all the links were correct in include.inc.php. The only problem I can find with the PDF instructions is that '/conf.d' is nonexistent in newer versions of apache2. It was replaced with "/conf-available". I've tried defining the apache conf location in the INSTALL.php as the following and none have worked...
... "define('APACHECONF',"/etc/apache2/conf-available");"
... "define('APACHECONF',"/etc/apache2/");"
... "define('APACHECONF',"/etc/apache2/conf.d");" //I tried creating this directory myself since it doesn't exist as I've explained above.
By 'none have worked' I mean the installation is successful, however there's no 'nagiosmobile_conf' in "/etc/apache2/sites-enabled' as there was with nagios core. That and http://.../nagiosmobile renders only a 404 error. The error logs are at the bottom of this post.

I've tried following this link's advice without success (viewtopic.php?f=7&t=45567)


Please let me know if there's any more information you need to diagnose the problem or if there are any solutions you want me to try. Thank you for all your help, I love Nagios and I think Nagios Mobile is going to be very helpful.


Thanks Again,
Canyon Bakehouse


/var/log/apache2/error.log
-----------------------------------------------------------------------------------------
[Mon Mar 19 06:25:02.484089 2018] [mpm_prefork:notice] [pid 6639] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 06:25:02.484130 2018] [core:notice] [pid 6639] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:15:05.168628 2018] [mpm_prefork:notice] [pid 6639] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 10:15:05.275706 2018] [mpm_prefork:notice] [pid 6418] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:15:05.275777 2018] [core:notice] [pid 6418] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:19:59.307035 2018] [mpm_prefork:notice] [pid 6418] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Mon Mar 19 10:19:59.377787 2018] [mpm_prefork:notice] [pid 6418] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:19:59.377817 2018] [core:notice] [pid 6418] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:23:12.962619 2018] [mpm_prefork:notice] [pid 6418] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 10:23:13.061975 2018] [mpm_prefork:notice] [pid 6698] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:23:13.062031 2018] [core:notice] [pid 6698] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:23:25.366140 2018] [mpm_prefork:notice] [pid 6698] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Mon Mar 19 10:23:25.414533 2018] [mpm_prefork:notice] [pid 6698] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:23:25.414560 2018] [core:notice] [pid 6698] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:34:52.614320 2018] [mpm_prefork:notice] [pid 6698] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 10:34:52.708644 2018] [mpm_prefork:notice] [pid 7172] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:34:52.708700 2018] [core:notice] [pid 7172] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:35:47.920612 2018] [mpm_prefork:notice] [pid 7172] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 10:35:48.018296 2018] [mpm_prefork:notice] [pid 7259] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:35:48.018349 2018] [core:notice] [pid 7259] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 10:39:01.839007 2018] [mpm_prefork:notice] [pid 7259] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 10:44:16.130915 2018] [mpm_prefork:notice] [pid 7927] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 10:44:16.130963 2018] [core:notice] [pid 7927] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 11:02:33.561120 2018] [mpm_prefork:notice] [pid 7927] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Mon Mar 19 11:02:33.625760 2018] [mpm_prefork:notice] [pid 7927] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 11:02:33.625785 2018] [core:notice] [pid 7927] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 11:17:47.367523 2018] [mpm_prefork:notice] [pid 7927] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 11:17:47.470069 2018] [mpm_prefork:notice] [pid 8922] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 11:17:47.470142 2018] [core:notice] [pid 8922] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 14:05:53.264987 2018] [mpm_prefork:notice] [pid 8922] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 14:05:53.374046 2018] [mpm_prefork:notice] [pid 13160] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 14:05:53.374135 2018] [core:notice] [pid 13160] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 19 14:44:45.508332 2018] [mpm_prefork:notice] [pid 13160] AH00169: caught SIGTERM, shutting down
[Mon Mar 19 14:44:45.613553 2018] [mpm_prefork:notice] [pid 14542] AH00163: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Mon Mar 19 14:44:45.613626 2018] [core:notice] [pid 14542] AH00094: Command line: '/usr/sbin/apache2'
canyonbakehouse
 
Posts: 2
Joined: Mon Mar 19, 2018 3:46 pm

Re: successful installation yet only 404 errors

Postby cdienger » Tue Mar 20, 2018 12:33 pm

Do yo use anything listed under /usr/local/nagiosmobile ? Are you prompted to login when you go to http://.../nagiosmobile?

Try manually copying the config over with:

cp /tmp/nagiosmobile/nagiosmobile_apache.conf /etc/apache2/sites-enabled/nagiosmobile.conf

and restart the service:

service apache2 restart
User avatar
cdienger
Support Tech
 
Posts: 1276
Joined: Tue Feb 07, 2017 11:26 am

Re: successful installation yet only 404 errors

Postby canyonbakehouse » Tue Mar 20, 2018 2:46 pm

Voilà, you're amazing, thank you very much!




Thanks Again,
Canyon Bakehouse
canyonbakehouse
 
Posts: 2
Joined: Mon Mar 19, 2018 3:46 pm

Re: successful installation yet only 404 errors

Postby tmcdonald » Wed Mar 21, 2018 10:07 am

Glad to hear it! I'll be closing this up now, but feel free to open another thread if you need anything in the future!
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
tmcdonald
Operations Engineer
 
Posts: 8989
Joined: Mon Sep 23, 2013 8:40 am


Return to Nagios Mobile

Who is online

Users browsing this forum: No registered users and 1 guest