Service Center Installation Error when running the ConfigurationTool.sh

Service Center Installation Error when running the ConfigurationTool.sh

  

Hi guys,


Has anyone of you has encountered the below errors when running the configurationtool.sh script?

Error messages are those in Bold Italic letter.




# ./configurationtool.sh
Initializing...

===== OutSystems Platform Configuration Tool 9.1 =====

Skip Database configuration? [y]: y

Skip Farm configuration? [y]: y

Skip Advanced configurations? [y]: y

Updating Platform Configuration files...

[Update Schema] Update the Session Catalog (discarding current sessions)? [n]: n
The Application Server needs to be restarted. Restart now? [n] y
Stopping jboss-outsystems:                                 [  OK  ]
Stopping jboss-outsystems-mq:                              [  OK  ]
Starting jboss-outsystems-mq:                              [  OK  ]
Starting jboss-outsystems:
jboss-outsystems startup has timed out, process still running.


Do you want to run Service Center installation? [y] y

===== Restarting OutSystems Services =====

Stopping RMI Registry Service                              [  OK  ]
Stopping OutSystems Deployment Controller Service          [  OK  ]
Stopping OutSystems Deployment Service                     [  OK  ]
Stopping OutSystems Log Service                            [  OK  ]
Stopping OutSystems Scheduler Service                      [  OK  ]
Starting RMI Registry Service                              [  OK  ]
Starting OutSystems Deployment Controller Service          [WARNING]
Starting OutSystems Deployment Service                     [  OK  ]
Starting OutSystems Log Service                            [  OK  ]
Service Center Installer v9.1.300.2

Start installing Service Center v9.1.300.2...
This operation may take a few minutes to complete...

Publishing Extension(s)...
Message 1
  [Error] Unable to contact Outsystems Deployment Controller Service

Message 2
  [Error] Unable to contact Outsystems Deployment Controller Service

Starting OutSystems Scheduler Service                      [  OK  ]

Hello Amelie,

The message says that the configuration tool wasn't able to connect to the Deployment Controller Service.

So, after it was stopped, it seems the configuration tool wasn't able to start it again:

Starting OutSystems Deployment Controller Service          [WARNING]

So, something went wrong during your upgrade of the platform.

You will need to investigate (logs, etc) in order to find out what's the problem. Maybe your configuration is not correct, for example (Controller IP, ports are blocked, etc).

In any case, you should contact OutSystems Support to help you in this case.

Cheers.




Hi Eduardo,


The Service Center is running though despite of the error. Port are ok. Following is the Deployment Controller Log.


2018-08-03 13:50:23,322 ERROR [outsystems.hubedition.util.ServerLog] (Pool Garbage Collector) Error on Message Queue setup: queue/OutSystemsGeneralLog
Exception: HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.]
2018-08-03 13:50:23,323 ERROR [outsystems.hubedition.util.ServerLog] (Pool Garbage Collector) Error sending log: javax.jms.IllegalStateException: Unable to create QueueSession because connection not initialized
   at outsystems.extensibility.MessageQueueClient.initSession(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.internalRestart(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.internalFullInit(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.createObjectMessageAndSend(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.LoggerAsynchronous.$qbd(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.LoggerAsynchronous.$qfd(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.LoggerAsynchronous.log(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.OSLogger.log(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.GeneralLog.$ued(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.GeneralLog$$Lambda$18/1120897940.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action1_Lambda.execute(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.GeneralLog.write(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.GeneralLog.write(Unknown Source)
   at outsystems.hubedition.runtimeplatform.log.GeneralLog.staticWrite(Unknown Source)
   at outsystems.hubedition.servercommon.pool.PoolGarbageCollector.$izd(Unknown Source)
   at outsystems.hubedition.servercommon.pool.PoolGarbageCollector$$Lambda$107/1690766092.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.servercommon.SandboxUtils.executeForSingleSandbox(Unknown Source)
   at outsystems.hubedition.servercommon.pool.PoolGarbageCollector.$bud(Unknown Source)
   at outsystems.hubedition.servercommon.pool.PoolGarbageCollector.collectLinkFiles(Unknown Source)
   at outsystems.hubedition.servercommon.pool.PoolGarbageCollector.innerExecute(Unknown Source)
   at outsystems.hubedition.deploymentcontroller.iiiIiiiiiiiIi.executeGC(Unknown Source)
   at outsystems.hubedition.servercommon.pool.IiiiIiiiiiiiI.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.ThreadStart_Lambda.run(Unknown Source)

How is your setup?
A single server? Or a Farm?
Where is the Deployment Controller Server? In the same machine as the rest of the server?

I'm not familiar with the JAVA installation (it seems to be JAVA).

Eduardo Jauch wrote:

How is your setup?
A single server? Or a Farm?
Where is the Deployment Controller Server? In the same machine as the rest of the server?

I'm not familiar with the JAVA installation (it seems to be JAVA).

it's just a single server.  OS is Linux RHEL 6.9.  Jboss EAP 6.4.19.  


Hum...

It seems the queue system is not correctly configured.

You should go through the upgrade list and see if you skipped some step. If the queue system is not properly configured, you will get errors like this.

P.S. Did you upgrage the server or changed configurations?

Eduardo Jauch wrote:

Hum...

It seems the queue system is not correctly configured.

You should go through the upgrade list and see if you skipped some step. If the queue system is not properly configured, you will get errors like this.

P.S. Did you upgrage the server or changed configurations?

There was no server upgrade nor any changed in the configurations. I;m not really familiar with the queue system, how is it being configured if you don't mind? 


I'm not familiar with the JAVA stack.

In this case, the best option I think it is to open a support case with OutSystems so they can take a look and help you in the steps necessary to troubleshooting this issue.

Cheers.