Hello,
Installed Nagwin as per installation instructions and after starting all the Nagwin services, tried accessing http://localhost but the page never loaded.
After going through FAQ's, tried changing the port from 80 to 11790 in \etc\nginx\nginx.conf to see if http://localhost:11790 works or not, but the page is still not loading.
Also, find below the log details from /var/opt/nginx/logs
1 [main] nginx 7536 child_info_fork::abort: C:\PROGRA~2\ICW\bin\cygssl-1.0.0.dll: Loaded to different address: parent(0x320000) != child(0x5A0000)
2014/03/27 08:23:57 [alert] 2488#0: fork() failed while spawning "worker process" (11: Resource temporarily unavailable)
2014/03/27 08:46:01 [alert] 2676#0: fork() failed while spawning "worker process" (11: Resource temporarily unavailable)
Have executed the below command, but there seems to be no problem:
C:\Program Files (x86)\ICW\etc\nagios>nagios -v nagios.cfg
C:\Program Files (x86)\ICW\etc\nagios>nagios -v nagios.cfg
Nagios Core 4.0.3
Copyright (c) 2009-present Nagios Core Development Team and Community Contributo
rs
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 02-28-2014
License: GPL
Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in
host type objects (config file '/etc/nagios/nagwin/templates.cfg', starting at
line 52)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in
service type objects (config file '/etc/nagios/nagwin/templates.cfg', starting
at line 155)
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 12 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 23 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 0
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check
Please let me know what needs to be further checked to get this running.
Regards,
Kapil Raut
Hmm, probably some processes are not terminated properly. Please do the following:
TASKKILL /F /FI "USERNAME EQ COMPUTER-OR-DOMAIN-NAME\SvcNagwin"
assuming that your service account is SvcNagwin
Hello,
Thanks for your kind reply. As specified, executed the steps but the issue still exists.
The page is not even loading for the URL: http://localhost:11790
Error Log:
2014/03/27 09:53:53 [alert] 2952#0: fork() failed while spawning "worker process" (11: Resource temporarily unavailable)
FYI....Nagwin is installed on Windows 7 64 bit OS. Do you foresee any issue with port not responding.
Regards,
Kapil Raut
Make sure if all four services are running. Try a port much lower than 11790.
Hello,
Thanks for you kind reply.
Problem has been resolved after the port number was changed from 11790 to 5555.
The URL: http://localhost:5555 did prompt for user/pwd for which nagiosadmin/nagios credentials was successfully authorized and the home page loaded.
Regards,
Kapil Raut
Hello,
Encountered 2nd issue w.r.t port number.
New port number needs to be specified in configuration file to access the web interface in new browser.
It seems that the port number once used gets locked and cannot be reused forever and hence new port number needs to be specified in configuration and Nagwin* services needs to be restarted.
Please help me in reslving this port number issue.
Regards,
Kapil Raut
This is weird. You say "It seems that the port number once used gets locked". Please make sure that you clean up dormant processes with the taskkill command before starting services again. If it doesn't help, that may mean that you have some security software blocking the web server operating on the specified port.
Hello,
Used port number: 9079 and this seems to work with every new session of the browser.
Will be montoring if there are any further issues w.r.t this port number.
Regards,
Kapil Raut