Unsolved
This post is more than 5 years old
1 Message
0
2504
AEE 2.0 - lockbox issue
I've downloaded the Atmos Evaluation Edition 2.0 version and am currently trying to get it running on ESXi 6.0.
I manually created the required networks and uploaded the VM images to one of the Datastores, then registered all of the machines. Once registered, I set the VMs to boot to BIOS, so I could answer the 'moved / copied' prompt without having the servers spin up - all were answered moved.
Once there, Network Adapter 2 was set to an internal vSwitch and all 4 machines were powered on at the same time (following ancidotal suggestions here).
Followed the PDF (included in the tar download) to shut down the RMGs, run the ip_change.py script, restore the RMGs, then run the post_ipchange.py and cst_post.py.
The post_ipchange script is where I start noticing issues with AEE-r2s1-001 - the mauimds_10402 service dies on start / restart (this has happened several times following the above process).
Ignoring that and setting up a CAS endpoint (tenant -> subtenant -> UID, then creating a PEA file with the ATMOS CAS PEA file generator) gives me errors in the /var/log/maui/casd.log:
CAS:casd:3:0:lockbox.cxx:openLockBox:60:Can't open the Lockbox: /var/local/maui/ws/ws.clb, error = -9, errmsg: The lockbox stable value threshold was not met because the system fingerprint has changed. To reset the system fingerprint, open the lockbox using the passphrase..
CAS:casd:3:0:lockbox.cxx:closeLockBox:81:Can't close lockbox /var/local/maui/ws/ws.clb, error: -38, errmsg: An invalid lockbox handle was specified.
CAS:casd:3:0:keyst_cstlb.cxx:ks_initialize:58:LockboxKeyStore: Cannot open lockbox /var/local/maui/ws/ws.clb
....
I'm not sure if there is an issue with the VM images, or trying to run them on ESXi 6.0, but this is completely reproducible.
Does anyone have any suggestions, or a potential way forward with this?
Thanks
Phil