<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 10:09 PM, Paul Wouters <span dir="ltr"><<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, 18 Nov 2008, Anirudh Kamatgi wrote:<br>
<br>
> I have a custom updown script written in perl.<br>
> Whenever this script gets called with 'down-client', I want to parse the<br>
> output of 'ipsec auto --status' inside this script.<br>
> I am assigning the output to a perl array( my @status = `ipsec auto<br>
> --status`; ).<br>
> However, the script hangs at this point.<br>
<br>
</div>Does the script rely on DNS at the other end of a tunnle that is down?</blockquote><div>No, I am using static IP private addresses, it is a gateway-gateway tunnel and the gateways are connected by a crossover cable.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
> I can see 2 shell processes executing the <path to ipsec>/ipsec/auto command<br>
> and one whack process.<br>
> After I kill the whack process, things get back to normal.<br>
<br>
</div>add plutodebug=controlmore and see if the logs say more.</blockquote><div>I did not get any extra information after adding the above parameter.<br>I did notice one interesting thing.<br><br>The problem happens when I bring down a tunnel administratively with the 'ipsec auto --down tunnel-name' command.<br>
This results in the updown script getting called which executes the command 'ipsec auto --status' and hangs.<br><br>If I see the processes which are running at this point, I see 2 whack processes, with the arguments '--name tunnel-name --terminate' and '--status' respectively.<br>
If I terminate( i.e send SIGINT ) the '--down' command which has hung, the first whack process is terminated, but the second whack process( the one with argument '--status' ) is still not terminated.<br>After this, all ipsec commands hang until I kill the original whack process which had not terminated.<br>
Is this a reentrancy issue?<br>Paul,<br>Do you need any more information like the barf output?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<font color="#888888"><br>
Paul<br>
<br>
</font></blockquote></div><br>