Bug #188
"FATAL: Element with key nohar already in hash 5151a968" when netplit occurs
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2011-01-19
Due date:
% Done:
0%
Estimated time:
Patch Available:
No
Found in Versions:
0.8.6
Confirmed:
No
Branch:
Security:
No
Help Needed:
Description
Sometimes when a netsplit occurs, bip exits after logging:
FATAL: Element with key nohar already in hash 5151a968
History
Updated by Pierre-Louis Bonicoli about 12 years ago
Updated by Thanks to Trou there is a backtrace:
bip(print_trace+0x1f)[0x7f95e889e3d4] bip(fatal+0xcc)[0x7f95e889e4e5] bip(list_remove_if_exists+0xc3)[0x7f95e889ea0f] bip(list_remove+0x23)[0x7f95e889ea7e] bip(hash_remove+0x68)[0x7f95e889f3c5] bip(+0x1b7c2)[0x7f95e88957c2] bip(+0x1b4fb)[0x7f95e88954fb] bip(irc_dispatch_server+0x9cb)[0x7f95e88912f3] bip(irc_dispatch+0x4d)[0x7f95e8893b3a] bip(bip_on_event+0x1bc)[0x7f95e8896f5a] bip(irc_main+0x10c)[0x7f95e8897171] bip(main+0x83c)[0x7f95e8888720] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f95e7d21c4d] bip(+0x7999)[0x7f95e8881999]
Updated by Arnaud Cornet almost 12 years ago
Updated by A dump of server message that lead to the fatal() would help reproduce and fix this.
Updated by Pierre-Louis Bonicoli over 11 years ago
- Assignee deleted (
Pierre-Louis Bonicoli) - Priority changed from High to Normal
- Target version deleted (
0.8.9)