wrapper-user

[Wrapper-user] centos5 - Can't make old wrapper daemon go away

[Horace P. <fli...@ya...>]

=0Ai ran into a simliar problem like mark leone some months ago: http://www=
.nabble.com/Can%27t-make-old-wrapper-daemon-go-away-tf3346234.html#a9353225=
.=0A=0Ahowever, i run the script on a fresh centos5 installation. but just =
to be sure i added the -ww in my script, too.=0A=0Aactually i found that th=
e getpid() function always leads to a deletion of the pid file, so i can no=
t use the script to stop/status/restart a service.=0A=0Ai put in some echo =
statements to narrow the problem.=0A=0Ahave a look at this code:=0A=0A...=
=0A               pidtest=3D`$PSEXE -ww -p $pid -o args | grep "$WRAPPER_CM=
D" | tail -1`=0Aecho "1"=0A                echo `$PSEXE -ww -p $pid -o args=
`=0Aecho "2"=0A                echo `$PSEXE -ww -p $pid -o args | grep "$WR=
APPER_CMD"`=0Aecho "3"=0A                echo `$PSEXE -ww -p $pid -o args |=
 grep "$WRAPPER_CMD" | tail -1`=0Aecho "4"=0A        echo "$pidtest"=0Aecho=
 "4"=0A=0A....=0A=0Aonly between 1 and 2 there will be any output. in the m=
oment the result of ps is piped to the grep command there is no longer any =
output. so especially $pidtest ist empty which leads to a deletion of the p=
id file and so the script does not work at all.=0A=0Aany thoughts?=0A=0A=0A=
=0A=0A=0A       =0A________________________________________________________=
____________________________=0ATake the Internet to Go: Yahoo!Go puts the I=
nternet in your pocket: mail, news, photos & more. =0Ahttp://mobile.yahoo.c=
om/go?refer=3D1GNXIC

Re: [Wrapper-user] centos5 - Can't make old wrapper daemon go away

[Leif M. <le...@ta...>]

Horace,
What version of the Wrapper are you using?  I was working with a
customer up until a couple months ago working with CentOS and
it was working perfectly.  That was using the latest script out of
SVN though:
http://wrapper.svn.sourceforge.net/viewvc/*checkout*/wrapper/trunk/wrapper/src/bin/sh.script.in

For some reason the value of $WRAPPER_CMD is not being found in
the output of your ps command.

Can you run this and then post the results:

echo $WRAPPER_CMD
echo `$PSEXE -ww -p $pid -o args`

That should make the cause clear.

Cheers,
Leif

Horace Pinker wrote:
>
> i ran into a simliar problem like mark leone some months ago: 
> http://www.nabble.com/Can%27t-make-old-wrapper-daemon-go-away-tf3346234.html#a9353225.
>
> however, i run the script on a fresh centos5 installation. but just to 
> be sure i added the -ww in my script, too.
>
> actually i found that the getpid() function always leads to a deletion 
> of the pid file, so i can not use the script to stop/status/restart a 
> service.
>
> i put in some echo statements to narrow the problem.
>
> have a look at this code:
>
> ...
>                pidtest=`$PSEXE -ww -p $pid -o args | grep 
> "$WRAPPER_CMD" | tail -1`
> echo "1"
>                 echo `$PSEXE -ww -p $pid -o args`
> echo "2"
>                 echo `$PSEXE -ww -p $pid -o args | grep "$WRAPPER_CMD"`
> echo "3"
>                 echo `$PSEXE -ww -p $pid -o args | grep "$WRAPPER_CMD" 
> | tail -1`
> echo "4"
>         echo "$pidtest"
> echo "4"
> ....
>
> only between 1 and 2 there will be any output. in the moment the 
> result of ps is piped to the grep command there is no longer any 
> output. so especially $pidtest ist empty which leads to a deletion of 
> the pid file and so the script does not work at all.
>
> any thoughts?