Accidentaly create identity with same name

Node Operators troubleshooting
1

I want create second node, at the second node i didnt know before which don’t use same name identity

first node and second node are different vm and location

What have i done?
-I was creating second node with same email with first node but with different authorization token, so a something like this at both node user@example.com:xxxxxx are different each other
-Both node have same wallet address, i think it’s not a problem.
-I was executing identity create storagenode in first node, but i did same too in second node, i realized it’s a mistake after saw this forum because that identity name already exist (storagenode),
so i saw in second node’s log it gave me output like this

storj.io/private/process.cleanup.func1:381
        github.com/spf13/cobra.(*Command).execute:852
        github.com/spf13/cobra.(*Command).ExecuteC:960
        github.com/spf13/cobra.(*Command).Execute:897
        storj.io/private/process.ExecWithCustomConfig:88
        storj.io/private/process.ExecCustomDebug:70
        main.main:385
        runtime.main:204
2021-10-01T20:33:49.220Z        INFO    Configuration loaded    {"Location": "/app/config/config.yaml"}
2021-10-01T20:33:49.236Z        INFO    Operator email  {"Address": "ikhwanperwira@gmail.com"}
2021-10-01T20:33:49.237Z        INFO    Operator wallet {"Address": "0xF6E8d68C40886aEA1d5A73DfA47BD2AEDFE57d55"}
2021-10-01T20:33:49.243Z        INFO    db      database does not exists       {"database": "info"}
2021-10-01T20:33:49.243Z        INFO    db      database does not exists       {"database": "bandwidth"}
2021-10-01T20:33:49.243Z        INFO    db      database does not exists       {"database": "orders"}
2021-10-01T20:33:49.243Z        INFO    db      database does not exists       {"database": "piece_expiration"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "pieceinfo"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "piece_spaced_used"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "reputation"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "storage_usage"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "used_serial"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "satellites"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "notifications"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "heldamount"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "pricing"}
2021-10-01T20:33:49.244Z        INFO    db      database does not exists       {"database": "secret"}
Error: Error creating revocation database: revocation database: boltdb: invalid database
        storj.io/storj/storage/boltdb.New:44
        storj.io/storj/private/revocation.openDBBolt:52
        storj.io/storj/private/revocation.OpenDB:35
        storj.io/storj/private/revocation.OpenDBFromCfg:23
        main.cmdRun:169
        storj.io/private/process.cleanup.func1.4:363
        storj.io/private/process.cleanup.func1:381
        github.com/spf13/cobra.(*Command).execute:852
        github.com/spf13/cobra.(*Command).ExecuteC:960
        github.com/spf13/cobra.(*Command).Execute:897
        storj.io/private/process.ExecWithCustomConfig:88
        storj.io/private/process.ExecCustomDebug:70
        main.main:385
        runtime.main:204

i should have execute this identity create storagenode2 in second node,
so will it affect my first node?

2

if you moved first node identity to other place then all ok, but it you rewrited first identity then all is bad

3

but i saw first node’s logs everything are running normal

4

did you made restart? identity loading during service start only

5

i did sudo docker stop storagenode in first node, then sudo docker start storagenode in first node. Still working fine because logs stream still give me normal output

6

does nodes has unic id? if they are not same then you safe, if same then bad

7

they are different node id, okay thank you solved,

that output error because permission error in folder,

eventhough same name identity when creating it, doesnt mean same nodeid, luckily i have the backup identity if theres something unexpected event