I seem to have the same issue when trying to start Weblogic server instances via the shell command (I have to use that for complicated reasons). After successfully starting the server Ansible sends a SIGHUP and the server shuts down again. :(
On Wednesday, October 15, 2014 1:39:08 PM UTC+2, Alainkr wrote: > > Hello, > > I'm very puzzled by the following: > > using regular ssh I'm not getting SIGHUP at the end. > using ansible SIGHUP get's sent : strace output : > > 0x7f34a666c9d0, tls=0x7f34a666c700, child_tidptr=0x7f34a666c9d0) = 600 > futex(0x7f34a666c9d0, FUTEX_WAIT, 600, NULL) = ? ERESTARTSYS (To be > restarted) > --- SIGHUP (Hangup) @ 0 (0) --- > +++ killed by SIGHUP +++ > > This is using an adhoc commands such : > -m shell -a "sudo /etc/init.d/myservice start" > -m shell -a "/etc/init.d/myservice start" -s > -m shell -a "/etc/init.d/myservice start" -s -c ssh > > I've tried -c ssh but behavior is unchanged. > I'm aware of the service module. But this is just an example. > The funny thing is that when using the service module no SIGHUP gets send > > My shell (bash) has "huponexit off" off couse. > > What is happening here ? Is this the excepted behavior ? > > I'm using ansible (1.7.1) paramiko (1.15.0) ( upgraded paramiko to > (1.15.1) same result ) > > Thanks for your help. I'm kind of lost on this. > > Alain > > > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/fd90b0fc-7313-4e11-a8fa-1be007758a69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
