Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when installing: Do not leave the Address field blank #5

Open
kpaulisse opened this issue Dec 14, 2017 · 7 comments
Open

Error when installing: Do not leave the Address field blank #5

kpaulisse opened this issue Dec 14, 2017 · 7 comments

Comments

@kpaulisse
Copy link

I'm trying to use this module to set up nexpose and when I run it I get this message:

Do not leave the Address field blank

The installation fails. Is there a new variable that needs to go into the response file that has not yet made it into the template in this repo?

@helenes-r7
Copy link
Contributor

Hey @kpaulisse

Yep you are correct that a new variable needs to go into the response file, currently looking at what that might be.
Nexpose should still install though, the message you get should only be a warning but not fail the installation. The service might fail to start on the first Puppet run, but another Puppet run should start it successfully. Can you confirm?

@kpaulisse
Copy link
Author

The command exits with status 1, which in our tooling causes Puppet to indicate that provisioning has failed.

Poking around a bit, it seems that "consoleAddress" and "sharedSecret" are the two parameters that we need to set in there, but I could not find documentation on what these do. I tried setting consoleAddress to localhost and sharedSecret to kittens which brings up this:

In screen "Console details [CustomFormPanelScreen]", property "Validation expression":
java.util.MissingResourceException: Can't find resource for bundle com.install4j.runtime.util.FileResourceBundle, key EngineConsoleTestunuccessful
	at java.util.ResourceBundle.getObject(ResourceBundle.java:450)
	at java.util.ResourceBundle.getObject(ResourceBundle.java:444)
	at java.util.ResourceBundle.getObject(ResourceBundle.java:444)
	at java.util.ResourceBundle.getObject(ResourceBundle.java:444)
	at com.install4j.runtime.installer.frontend.VariableResourceBundleWrapper.handleGetObject(VariableResourceBundleWrapper.java:32)
	at java.util.ResourceBundle.getObject(ResourceBundle.java:441)
	at java.util.ResourceBundle.getString(ResourceBundle.java:407)
	at com.install4j.runtime.installer.ContextImpl.getMessage(ContextImpl.java:349)
	at com.install4j.script.I4jScript_Internal_203.eval(I4jScript_Internal_203.java:212)
	at com.install4j.script.I4jScript_Internal_203.evaluate(I4jScript_Internal_203.java:242)
	at com.install4j.runtime.installer.helper.Script.evaluate(Script.java:33)
	at com.install4j.runtime.installer.ContextImpl.runScript(ContextImpl.java:188)
	at com.install4j.runtime.installer.ContextImpl.runScript(ContextImpl.java:182)
	at com.install4j.runtime.installer.ContextImpl.runBooleanScript(ContextImpl.java:55)
	at com.install4j.runtime.installer.ContextImpl.runBooleanScript(ContextImpl.java:225)
	at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.runValidationScript(AbstractHeadlessScreenExecutor.java:124)
	at com.install4j.runtime.installer.frontend.headless.UnattendedScreenExecutor.handleScreen(UnattendedScreenExecutor.java:100)
	at com.install4j.runtime.installer.frontend.headless.AbstractHeadlessScreenExecutor.execute(AbstractHeadlessScreenExecutor.java:81)
	at com.install4j.runtime.installer.controller.Controller$1.run(Controller.java:138)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
	at java.awt.EventQueue.access$500(EventQueue.java:97)
	at java.awt.EventQueue$3.run(EventQueue.java:709)
	at java.awt.EventQueue$3.run(EventQueue.java:703)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

I'm not sure if it's because of an apparent typo in "EngineConsoleTestunuccessful" or more likely if this is because it's trying to test communication between services that haven't been registered yet or started up. Maybe there's a boolean flag that we can set to disable this connectivity test during an unattended install?

@helenes-r7
Copy link
Contributor

Hmm interesting... can you provide the Puppet code? redacting any sensitive info

@kpaulisse
Copy link
Author

I just added this to the end of the response.varfile.erb template:

# Undocumented Parameters - Fix/parameterize these when we know what they do
consoleAddress=localhost
sharedSecret=kittens

@chunyong-lin
Copy link

chunyong-lin commented Jan 12, 2018

Hi @helenes-r7
I also encounter same issue with output Do not leave the Address field blank and chef installation exists with code 1(I am using nexpose chef cookbook to install scan engine.)
Do you know what're the variables am I missing?
Thanks!

@rrupesh
Copy link

rrupesh commented Aug 27, 2019

Hi! I am facing the same issue. Any help with this one?

In screen "Console details [CustomFormPanelScreen]", property "Validation expression":

@helenes-r7
Copy link
Contributor

Hi @rrupesh,

First time I see that error. Can you post the Puppet agent output and possibly the Puppet code you're using to reference the module?

@chunyong-lin
Sorry I hadn't seen your message. It looks like it might be related to @kpaulisse output of "Do not leave the Address field blank". His suggestion of adding the extra undocumented parameters might help. We've just been dealing with it since we normally reboot the system after installing Nexpose (really bad form on my part).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants