Search Engine: Elastic

Article ID: 130157, created on Jan 13, 2017, last review on Jan 13, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

  1. Update installation fails with error:

    2017-01-13 15:44:12.203 [INFO] Starting JBoss, it can take around of 1-2 minutes, please wait...
    Starting pau (via systemctl):  Warning: pau.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    Job for pau.service failed because the control process exited with error code. See "systemctl status pau.service" and "journalctl -xe" for details.
                                                               [FAILED]
    2017-01-13 15:46:37.528 [INFO] Upgrading PAU
    2017-01-13 15:46:38.319 [ERROR] CLI return code is: 1, stderr: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
            at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278)
            at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:241)
            at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:483)
            at org.jboss.modules.Module.run(Module.java:312)
            at org.jboss.modules.Main.main(Main.java:460)
    Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
            at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1028)
            at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:840)
            at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:819)
            at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:276)
            ... 8 more
    Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:9990. The connection failed
            at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
            at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
            at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1005)
            ... 11 more
    
  2. System log /var/log/messages contains the error:

    Jan 13 18:42:54.855 pau[807]: Starting pau: [FAILED]^MStartup failure, check  /var/log/pa/console.log , if it doesn't contain any errors this could mean your host is too slow to start in  120
    

Cause

Update installer was performing restart of 'pau', but the server is not productive enough to let 'pau' start within specified timeout period and operation was interrupted.

Resolution

Refer to KB article for solution.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF