Bug #188
open
"FATAL: Element with key nohar already in hash 5151a968" when netplit occurs
Added by Pierre-Louis Bonicoli over 13 years ago.
Updated over 12 years ago.
Description
Sometimes when a netsplit occurs, bip exits after logging:
FATAL: Element with key nohar already in hash 5151a968
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]
- Target version changed from 0.8.8 to 0.8.9
- Priority changed from Normal to High
A dump of server message that lead to the fatal() would help reproduce and fix this.
- Assignee deleted (
Pierre-Louis Bonicoli)
- Priority changed from High to Normal
- Target version deleted (
0.8.9)
Also available in: Atom
PDF
Updated by 
Updated by