HPE 3PAR StoreServ Storage
1819774 Members
3514 Online
109607 Solutions
New Discussion

Re: SSMC and log4j vulnerability

 
SOLVED
Go to solution
sbhat09
HPE Pro

Re: SSMC and log4j vulnerability

Hello @BBARBAROS,

If you can check the SSMC upgrade activity logs, are you finding this error? '/var/lib/dpkg/lock was found to be acquired'

If yes, some other process may be running simultaneously that is stopping the SSMC new version to acquire lock to the directory /var/lib/dpkg/

You may wait for the other process to complete and then proceed with upgrading SSMC.

Or identify, terminate/stop the other process and then proceed.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo