To summarize: Make sure if you reset the security password on the Publisher (even if it's right) using the procedure below and then try installing again if you hit this error.
Had a nightmare with this issue (both servers on the LAN).
Verified the security password was correct as it tells you when you try to reset it back to the same old password so then after taking log dumps over the serial port and analysing the logs it said the below which meant there was an issue with the security password.
Had a nightmare with this issue (both servers on the LAN).
Verified the security password was correct as it tells you when you try to reset it back to the same old password so then after taking log dumps over the serial port and analysing the logs it said the below which meant there was an issue with the security password.
02/23/2018
01:22:30 IPM|(CAPTURE) head: cannot open
`/usr/local/platform/.security/CCMEncryption/keys/encrypted_Dkey.txt' for
reading: No such file or directory|<LVL::Debug>
02/23/2018
01:22:30 IPM|(CAPTURE) isftp
using password failed (15). Trying sftp using keys.|<LVL::Debug>
02/23/2018
01:22:30 IPM|(CAPTURE) Required file
/usr/local/platform/conf/platformConfig.xml not present on first node
(active)|<LVL::Debug>
02/23/2018
01:22:30 IPM|(CAPTURE) isftp
using password failed (15). Trying sftp using keys.|<LVL::Debug>
Procedure
So used the above procedure to change the Security Password on the Publisher and rebooted the node, then went over the install again and it went through fine (did ask me for "more time") but ultimately went through fine.
Then tried installing a .cop file to math what's on the publisher and hit the following bug so had to restart the install from the CLI and all good.
Attempted
to upgrade the system to ES03 but we ran into the defect:
No comments:
Post a Comment