AnsweredAssumed Answered

Does anyone else have problem with AM 8.2 Patch 5?

Question asked by Luka Kodric on Feb 23, 2017
Latest reply on Feb 24, 2017 by Luka Kodric

Like • Show 0 Likes0
Comment • 8

Patch 5 for AM 8.2 arrived to today and I've tried to install it on AM 8.2 Patch 4 but it fails... some java error about installer.

I have case opened on My RSA: Case Number 00927074

Just wanna know if anyone else has problem.. This is VM on Hyper-V.

22295 2017-02-23 15:22:27,055 INFO: Waiting for update-installer webapp to start
84868 2017-02-23 15:23:29,628 ERROR: Failed to kill update-installer.
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused]

Edward Davis

Feb 23, 2017 2:12 PM

Correct Answer

slow reboot, something odd is going on...maybe not RSA software related

do some basic linux system checks

as root

check /var/log/messages for anything odd

check dmesg | more and look for disk errors

See the reply in context

No one else had this question

Outcomes

8 Replies

Edward Davis Feb 23, 2017 1:04 PM
Mark Correct
Correct Answer
that error is due to a timeout

8.2 patch 4 does contain a problem where sometimes the CPU spikes, so perhaps the system
is not freed of enough resources at the time of patch ?

AM-30780 – In certain deployments, virtual appliance CPU load exceeded 100%
AM-30478 – spike in CPU load and degraded performance

So...perhaps reboot, then try patch

------------
here is an example of when the timer was set to 30 seconds, and it took longer than 30, so it chucked this error
(this was 8.1 sp1 p4)

27199 2014-10-16 10:24:20,953 INFO: Waiting for update-installer webapp to start
57881 2014-10-16 10:24:51,635 ERROR: Failed to kill update-installer.
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340)

The timers are longer now (60 seconds) in all patches, but perhaps your system is out of resources due to
the CPU issue, and the extended timer is not enough.

15:22:27,055
15:23:29,628

62 seconds
Like • Show 0 Likes0
Actions
- Luka Kodric @ Edward Davis on Feb 23, 2017 1:38 PM
  Mark Correct
  Correct Answer
  okay this is bad..i rebooted the VM 8.2 P4 and it's freaking slow.... i'm not sure i will be able to appy p5.. reboot is taking now more than 30mins..
  Like • Show 0 Likes0
  Actions
  - Edward Davis @ Luka Kodric on Feb 23, 2017 2:12 PM
    Unmark Correct
    Correct Answer
    slow reboot, something odd is going on...maybe not RSA software related
    
    do some basic linux system checks
    as root
    
    check /var/log/messages for anything odd
    
    check dmesg | more and look for disk errors
    Like • Show 0 Likes0
    Actions
    - Luka Kodric @ Edward Davis on Feb 23, 2017 4:06 PM
      Mark Correct
      Correct Answer
      You were right... one other VM was trashing disk like there is no tomorrow.. I've moved RSA VM to new hyper-v host.. and now applying P5 thanks man
      Like • Show 0 Likes0
      Actions
Luka Kodric Feb 23, 2017 1:18 PM
Mark Correct
Correct Answer
Edward thanks.. will reboot and try again
Like • Show 0 Likes0
Actions
Luka Kodric Feb 24, 2017 4:10 AM
Mark Correct
Correct Answer
After moving VM to different Hyper-V host I applied Patch 5 successfully and now it's running like a champ! Thanks again Edward.
1 person found this helpful
Like • Show 1 Like1
Actions
steve brokenshire Feb 24, 2017 5:30 AM
Mark Correct
Correct Answer
I have had a problem but not the one you mention. I have lost replication after update. about to ring support, have folled knowledge base article but it appears to have lost its dba password
Like • Show 0 Likes0
Actions
- Luka Kodric @ steve brokenshire on Feb 24, 2017 5:34 AM
  Mark Correct
  Correct Answer
  Strange.. my replication was fine after patch 5.
  Like • Show 0 Likes0
  Actions

Does anyone else have problem with AM 8.2 Patch 5?

Outcomes

Related Content

Recommended Content