AnsweredAssumed Answered

Installation RSA L&G 7.0.1 - Web and DB time different

Question asked by Armel Lupapi on Apr 18, 2017
Latest reply on Aug 2, 2017 by Amit Khatua

Like • Show 0 Likes0
Comment • 9

I am installing RSA L&G 7.0.1 and I'm having an error at the end, which prompts the installation script to remove the Aveksa_System.cfg file right after.

Installation type:

Remote DB installation, already upgraded to Oracle v12

Installation check is successful (after updating the host file and the oracle user and oinstall group ID).

While trying to start the application, the startup fail and the installation script delete the Aveksa_System.cfg

Under the aveksa_server file, I tried to update the time buffer interval, but this is irrelevant because the that file get overwritten every time you run the install.sh script.

From the installation script, below is the error I'm having

Attachments

Capture.PNG62.3 KB

No one else has this question

Outcomes

9 Replies

Boris Lekumovich Apr 18, 2017 11:00 PM
Mark Correct
Correct Answer
can you share aveksa-install.log?
Like • Show 0 Likes0
Actions
- Armel Lupapi @ Boris Lekumovich on Apr 19, 2017 5:01 AM
  Mark Correct
  Correct Answer
  Find it attached
  
  Regards
  Armel Lupapi
  
  Group IT | armel.lupapi@investec.co.za<mailto:armel.lupapi@investec.co.za> | Tel: +27 11 286 8063 | Cell: +27 76 920 8549
  Client Support Centre: +27 11 286 9663 / 0860 110 161 | www.investec.co.za <https://www.investec.co.za/>
  
  “The best way to get started is to quit talking and begin doing.”
  Attachments
  - aveksa-install.zip7.4 KB
  - image002.gif2.5 KB
  - image001.png13.6 KB
  Like • Show 0 Likes0
  Actions
  - Amit Khatua @ Armel Lupapi on Apr 19, 2017 7:18 AM
    Mark Correct
    Correct Answer
    Can you increase the wait time and check once -
    
    // sleep 10 seconds to wait Wildfly starting and checkIfWildflyRunning works properly
    Thread.sleep(60000)
    //Thread.sleep(10000)
    restarted = checkIfWildflyRunning(160)
    //restarted = checkIfWildflyRunning(60)
    File location -
    /staging/deploy/wildfly-conf/groovy/com/aveksa/wildfly/Util.groovy
    
    Thanks !
    Like • Show 0 Likes0
    Actions
    - Brenden McNeil @ Amit Khatua on Aug 2, 2017 5:17 PM
      Mark Correct
      Correct Answer
      I was having an issue where on the Configure Wildfly Server section it would fail saying it could not connect to localhost:9990, however after the install failed it was clear that the Wildfly Server was actually started. Making the change Amit describes got me past the error successfully. Thanks for posting, saved me from starting a new thread
      Like • Show 0 Likes0
      Actions
      - Amit Khatua @ Brenden McNeil on Aug 2, 2017 9:35 PM
        Mark Correct
        Correct Answer
        Good news to hear early morning
        Like • Show 0 Likes0
        Actions
Armel Lupapi Apr 19, 2017 7:38 AM
Mark Correct
Correct Answer
Actually, I managed to get through that issue now. The application is installed and is running according to application log, but the it's not accessible from the web browser. I have tried on both 8443 and 8080.
I did made sure that there are no firewalls on them
Like • Show 0 Likes0
Actions
- Amit Khatua @ Armel Lupapi on Apr 19, 2017 7:52 AM
  Mark Correct
  Correct Answer
  Could you please provide more details on the error message you received in browser ? Meanwhile check the log files
  ../wildfly/standalone/log/server.log
  and
  ../wildfly/standalone/log/aveksaServer.log
  to confirm if the ear got deployed properly.
  Like • Show 0 Likes0
  Actions
  - Armel Lupapi @ Amit Khatua on Apr 19, 2017 8:02 AM
    Mark Correct
    Correct Answer
    The funny thing is that there is no aveksaServer.log at all. Only the server.log file
    Under /home/oracle/wildfly-8.2.0.Final/standalone/log
    
    Regards
    Armel Lupapi
    
    Group IT | armel.lupapi@investec.co.za<mailto:armel.lupapi@investec.co.za> | Tel: +27 11 286 8063 | Cell: +27 76 920 8549
    Client Support Centre: +27 11 286 9663 / 0860 110 161 | www.investec.co.za <https://www.investec.co.za/>
    
    “The best way to get started is to quit talking and begin doing.”
    Attachments
    image003.gif2.5 KB
    image002.png13.6 KB
    image001.jpg13.9 KB
    Like • Show 0 Likes0
    Actions
    - Amit Khatua @ Armel Lupapi on Apr 19, 2017 8:10 AM
      Mark Correct
      Correct Answer
      That means the application is not deployed itself. You cane try the workaround as mentioned in this discussion 000033000 - Error when running RSA Via Lifecycle & Governance 7.0 customizeACM.sh: Could not find Aveksa ear to redeploy the ear
      
      Thanks !
      Like • Show 0 Likes0
      Actions

Installation RSA L&G 7.0.1 - Web and DB time different

Attachments

Outcomes

Attachments

Attachments

Related Content

Recommended Content