Bug #1453

Updated by Tobias Brunner over 4 years ago


We have several hundred connections defined in ipsec.conf. We have script which calls "ipsec reload" whenever a new connection definition is added. If the script calls "ipsec reload" few times in loop due to any reason we are seeing that starter getting stuck in the following call stack and never recovers. We started seeing this issue after upgraded to 5.3.5. Any help in debugging this issue is highly appreciated.

(gdb) bt
#0 0x00007faeee9edcb0 in __write_nocancel () from /lib/x86_64-linux-gnu/
#1 0x00007faeeee31c25 in update (this=<optimized out>) at processing/watcher.c:121
#2 0x00007faeeee31cce in remove_ (this=0xf60490, fd=6) at processing/watcher.c:490
#3 0x00007faeeee2cc1e in destroy (this=0xfe2730) at networking/streams/stream.c:263
#4 0x0000000000405dc3 in send_stroke_msg (msg=0xf61840) at starterstroke.c:119
#5 0x0000000000406476 in starter_stroke_add_conn (cfg=0xfd0e30, conn=0xfbe000) at starterstroke.c:280
#6 0x0000000000403023 in main (argc=<optimized out>, argv=<optimized out>) at starter.c:902

(gdb) info threads
Id Target Id Frame
* 1 Thread 0x7faeef276700 (LWP 25088) "starter" 0x00007faeee9edcb0 in __write_nocancel () from /lib/x86_64-linux-gnu/