adshares/ads

error "Lock user failed"

Closed this issue · 3 comments

Error Lock user failed occured when node status change was requested.

[1530536680] OFFICE new ticket (total open:0)
[1530536680] Client entered 172.16.222.101:57418
[1530536680] OFFICER ready 0012
[1530536680] OFFICE online 8
[1530536680] SENDING user info 00000012:0000
[1530536680] 000E HASH 00125B3A22C00D9D [00125B3A22C09D0F]
[1530536680] HASH find:00125B3A22C00D9D (00125B3A22C0) 18:1530536640
[1530536680] 000E PROVIDING MESSAGE 0012:5B3A22C0 0D (len:258)
[1530536680] 000F HASH 00125B3A22C00DE6 [00125B3A22C0E60F]
[1530536680] HASH find:00125B3A22C00DE6 (00125B3A22C0) 18:1530536640
[1530536680] 000F PROVIDING MESSAGE 0012:5B3A22C0 0D (len:258)
[1530536680] OFFICE new ticket (total open:1)
[1530536680] Client entered 172.16.222.101:57420
[1530536680] OFFICER ready 0012
[1530536680] OFFICE online 9
[1530536680] ERROR: Lock user failed
[1530536680] ERROR: 0
[1530536680] Client left 172.16.222.101:57420

Full log is available in 20180702_1526_lock_user_fail.zip

Probably cause of the error is that client and node are on the same machine.

Error was confirmed with remote node; client and node were on separate machines.

Lock user failed errors are to be expected. client should retry transaction