AnsweredAssumed Answered

Issue with installation of ACM V7.0 with remote DB

Question asked by Kumar Gaurav

on Apr 13, 2016
Latest reply on Sep 21, 2016 by Edwin Mullie

Like • Show 0 Likes0
Comment • 5

Installation of ACM V7.0 with remote DB fials with error in aveksa-install.log.

The error is " Failed to connect to server. Error message - Unable to connect to controller.org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990"

Please see attachment for full error log.

However am able to start and stop asveksa services without any issues but application is not accessible from UI.

I found that ports 8443 and 8445 are not listening, may be due to some error.

Anyone faced similar issues? I see (ACM-59364) was opened few months back and was closed as not reproducible. AM facing the exact same issue.

Ted Barbour

Apr 14, 2016 8:21 AM

Correct Answer

I don't know of a simple fix/work-around. Things started going downhill on your install attempt when:

"Start Wildfly to configure and load ear

Cannot connect to the database. The watchdog will start the server when it can connect to the database."

occurred.

I would recommend opening a support case and providing all relevant information so that a reproduction environment can be created.

See the reply in context

Attachments

aveksa-install.log_customer.zip5.0 KB

No one else had this question

Outcomes

Ted Barbour

Apr 14, 2016 8:21 AM

I don't know of a simple fix/work-around. Things started going downhill on your install attempt when:

"Start Wildfly to configure and load ear

Cannot connect to the database. The watchdog will start the server when it can connect to the database."

occurred.

I would recommend opening a support case and providing all relevant information so that a reproduction environment can be created.

Actions

Erica Chalfin

Apr 14, 2016 11:03 AM

Kumar,

Per Ted's recommendation, please contact RSA Customer Support to open a case so an engineer can work with you to resolve this issue.

Regards,

Erica

Actions

Edwin Mullie

Aug 3, 2016 9:35 AM

If you use the service name as the SID and when asked is the service name equal to the SID say yes. This will get the product installed, how ever when you try to connect to it using a browser you will see that avuser, advuser and acmdb cannot connect to the database.

You can solve this by editing the aveksa-standalone-full.xml file (when running standalone) or domain.xml on the domain controller (when running in cluster).

You need to changed all entries that have the service name in them:

It was: <hostname>:<port>:<service name>

It should be: <hostname>:<port>/<service name>

so replace the : with / between the port and the service name

this should get you up and running

Engineering is aware of this and will be working on a fix in future releases

Edwin

Actions

WdMkzGi9PIXAIIHXTI2lJhYwV4QIpZ3yOW521w1a3kE= Sep 19, 2016 8:53 PM

Hi Kumar,

I am facing exact same error during installation on remote db. Is it possible to share the solution for this issue.

Regards

Tripura

Actions

Edwin Mullie

@ WdMkzGi9PIXAIIHXTI2lJhYwV4QIpZ3yOW521w1a3kE= on Sep 21, 2016 2:48 AM

Do the suggestions posted not work?

Edwin

Actions

5 Replies

Ted Barbour Apr 14, 2016 8:21 AM
Unmark Correct
Correct Answer
I don't know of a simple fix/work-around. Things started going downhill on your install attempt when:

"Start Wildfly to configure and load ear
Cannot connect to the database. The watchdog will start the server when it can connect to the database."

occurred.

I would recommend opening a support case and providing all relevant information so that a reproduction environment can be created.
Like • Show 1 Like1
Actions
Erica Chalfin Apr 14, 2016 11:03 AM
Mark Correct
Correct Answer
Kumar,

Per Ted's recommendation, please contact RSA Customer Support to open a case so an engineer can work with you to resolve this issue.

Regards,
Erica
Like • Show 0 Likes0
Actions
Edwin Mullie Aug 3, 2016 9:35 AM
Mark Correct
Correct Answer
If you use the service name as the SID and when asked is the service name equal to the SID say yes. This will get the product installed, how ever when you try to connect to it using a browser you will see that avuser, advuser and acmdb cannot connect to the database.

You can solve this by editing the aveksa-standalone-full.xml file (when running standalone) or domain.xml on the domain controller (when running in cluster).
You need to changed all entries that have the service name in them:
It was: <hostname>:<port>:<service name>
It should be: <hostname>:<port>/<service name>

so replace the : with / between the port and the service name

this should get you up and running

Engineering is aware of this and will be working on a fix in future releases

Edwin
Like • Show 1 Like1
Actions
WdMkzGi9PIXAIIHXTI2lJhYwV4QIpZ3yOW521w1a3kE= Sep 19, 2016 8:53 PM
Mark Correct
Correct Answer
Hi Kumar,

I am facing exact same error during installation on remote db. Is it possible to share the solution for this issue.

Regards
Tripura
Like • Show 0 Likes0
Actions
- Edwin Mullie @ WdMkzGi9PIXAIIHXTI2lJhYwV4QIpZ3yOW521w1a3kE= on Sep 21, 2016 2:48 AM
  Mark Correct
  Correct Answer
  Do the suggestions posted not work?
  
  Edwin
  Like • Show 0 Likes0
  Actions

Issue with installation of ACM V7.0 with remote DB

Attachments

Outcomes

Related Content

Recommended Content