Hello,
We are trying to upgrade our environment to the latest version (10.5.0.1) but cannot do so using the GUI method as provided on the documentation.
Did anyone get the same error as ours?
The Broker/SA Head-unit is already up to date though.
If we cannot fix the error, I think we'll go with a manual CLI update, which based on our experience is a bit complicated and time consuming.
Cheers!
Hi RJ,
There was a issue which I also faced during the update of RSA SA from 10.5 to 10.5.0.1.
Have you installed GPG-keys?
Regards,
Deepanshu Sood.
yup, all of my hosts are installed with the 10.5.0.1 gpg-pubkeys
Are you still getting the same error or what if you try to update the SA by CLI, the what error are you receiving?
Regards,
Deepanshu Sood.
Aug 12, 2015 9:30 AMHi RJ,
In the other support cases that I was able to find that experienced this issue, they were able to resolve the issue by rebooting the Security Analytics server and the affected appliance. However, to rule out the possibility of the issue simply being UI-related, I would recommend first issuing the commands below on the SA Server to see if it takes care of the issue.
service collectd restart
stop jettysrv
start jettysrv
Be warned that the UI will be inaccessible while the jettysrv service is stopped and while it is re-initializing (which generally takes 3-5 minutes), and will log out any users that are currently using the system, so you will want to execute those commands when nobody else is logged in to the Security Analytics UI.
Please let us know if either of these workarounds fix your issue.
Thanks.
Jeff
Unfortunately, it didn't help resolving the issue.
According to the support we got in contact with, we need to re-establish the puppet.
May also lead to removal and re-purposing the appliance.
Any more thoughts on this?
Thanks.
@ Rey John Ignacio on Aug 18, 2015 9:07 AMRJ,
I'm sorry to hear that the workaround didn't resolve the issue. In that case it may be necessary to remove and re-purpose the appliance, as the support team suggested. They can help you with the process, and the steps can also be found in the knowledge article 29081.
Thanks,
Jeff
I would suggest to verify that NTP is synchronized , also that issue sounds like a Linux yum issue.
De: RJ
Enviado el: jueves, 13 de agosto de 2015 06:35 a. m.
Para: D4v3
Asunto: Re: - 10.5.0.0 to 10.5.0.1 Upgrade Challenges
<https://community.emc.com/?et=watches.email.thread> ECN
10.5.0.0 to 10.5.0.1 Upgrade Challenges
reply from RJ <https://community.emc.com/people/rjignacio?et=watches.email.thread> in RSA Security Analytics - View the full discussion <https://community.emc.com/message/901308?et=watches.email.thread#901308>
Hello Jeff and Dave,
You're both right, we succeeded doing so 2 days ago, We re-synced NTP and fixed puppet communications first (along with remove and re-purpose). There's a script to do knowledge article 29081 quick, but I'm not sure if I can share it here.
I guess this should solve our problems moving forward
Thanks for all your help!
-RJ
@ Rey John Ignacio on Aug 19, 2015 10:34 AMThat's great! Thanks for giving us the update!
Hello Jeff and Dave,
You're both right, we succeeded doing so 2 days ago, We re-synced NTP and fixed puppet communications first (along with remove and re-purpose). There's a script to do knowledge article 29081 quick, but I'm not sure if I can share it here.
I guess this should solve our problems moving forward
Thanks for all your help!
-RJ