When trying to configure the nagios-1.1.0 JumpBox for the first time through the web inbterface I get the following error messages displayed:
/jumpbox/application_portal/privileged_scripts/ubuntu/lib/jbutils.rb:31:in `service': couldn't run init script: nagios2 restart (RuntimeError) from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:57:in `set_email' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/generic.rb:66:in `setup' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `send' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `execute_method' from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:86
Any information on why this is happening would be greatly appreciated.
Configuration errors for nagios-1.1.0
Also, what can you guys tell me about your network environment? Presumably you aren't changing the JumpBox configuration so it is still running in bridged mode.
Where,exactly, are you seeing this error, email screenshots to godber at JumpBox dot com? Immediately after setup it explodes and shows this error? Or does the error show up in the top part of the admin portal, leaving the admin portal functional? Can you SSH into the JumpBox after you get this error? If so, you may be able to restart nagios manually and proceed as usual.
Austin
Configuration errors for nagios-1.1.0
I got the same errors:
/jumpbox/application_portal/privileged_scripts/ubuntu/lib/jbutils.rb:31:in `service': couldn't run init script: nagios2 restart (RuntimeError) from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:57:in `set_email' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/generic.rb:66:in `setup' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `send' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `execute_method' from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:86
Nagios 1.1.0
Host OS: Centos 5.2
Platform: VMware Server 1.06
Browser: Firefox 3
Configuration errors for nagios-1.1.0
Does unzipping and trying again make any difference?
I will try this with FF3. Perhaps I haven't done that yet.
Update - No its not just FF3, what OS are you running the browser on? XP?
Austin
Configuration errors for nagios-1.1.0
Hmm, can you tell us a little bit about your environment?
What host OS, virtualization platform and browser you were using to set this up? I think I have heard mention of someone with this issue once before (earlier release) but we were unable to reproduce it at all.
Austin
OS: Vista Business Browser:
OS: Vista Business
Browser: Firefox 3.0 or IE7
vmWare Server: 2.0 Beta
I have an Ubuntu 6.x box I can try this on as well and will update with my findings.
Confirmed that this worked
Confirmed that this worked fine on an Ubuntu box.
Configuration errors for nagios-1.1.0
What was the browser there, FF3 or FF2? Or are you saying that the Ubuntu machine was the Host OS rather than the Desktop OS?
Austin
Same Issues
I have exactly the same problem.
Running on Vista 64 and VMWare Workstation 6.
Have tried many combinations of browsers and guest configurations. Always the same error during configuration of the JumpBox.
/jumpbox/application_portal/privileged_scripts/ubuntu/lib/jbutils.rb:31:in `service': couldn't run init script: nagios2 restart (RuntimeError) from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:57:in `set_email' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/generic.rb:66:in `setup' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `send' from /jumpbox/application_portal/privileged_scripts/ubuntu/lib/utils.rb:176:in `execute_method' from /jumpbox/application_portal/privileged_scripts/ubuntu/app.rb:86
Have tried to configure on IE7, FF2, FF3, Safari, and Opera 9. All give same error.
Would indicate to me this is an issue with VMWare on Windows?
Does anyone else have this Jumpbox running on VMWare on a Windows Vista host?
Just for reference, I have every other JumpBox running on this infrastructure perfectly. Only Nagios displays this behaviour.