If a second identity is mistakenly created the node will not start

Description

Whilst testing the Hot-Cold HA deployment we did the following:
1. Deployed a node on one machine (devMode=false)
2. Registered the node properly with the doorman
3. Copied files to cold backup node.
4. Stopped primary node and started secondary node.
5. This seemed to create a fresh node identity??? How in devMode=false????
6. Then correctly copied identity from primary node and restarted.
7. Now DB contains two identities for itself and the node cannot be started and crashes out!!!!

Good logging of error is required when this happens so the node operator / administrator knows what the issue is

Activity

Show:
Matthew Nesbit
June 1, 2018, 10:48 AM

Attached the log of this sordid tale

Gavin Thomas
June 14, 2018, 9:57 AM

Fix should focus on improved logging of the reason for the crash

Stefano Franz
June 14, 2018, 1:56 PM

I am working on a fix

Katelyn Baker
June 25, 2018, 10:18 AM

Moving to Core since Stefano seems to have claimed it

Assignee

Stefano Franz

Reporter

Matthew Nesbit

Labels

Sprint

None

Epic Link

None

Priority

High

Severity

Medium

CVSS Score

None

CVSS Vector

None

Due Date

None

Engineering Teams

None

Fix versions

Affects versions

None

Ported to...

None

Story Points / Dev Days

None
Configure