kill: bad signal ?

thomas2004ch · 07-03-2013, 01:31 AM

I started a process and the pid is 1234. When I try to kill this process with kill 1234, I got error

Code:

/usr/share/jbossas/bin/standalone.sh: kill: bad signal

The standalone.sh is the script starting the process.

anon237 · 07-03-2013, 02:46 AM

Cross-posting is against the LQ rules. Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place.

Continue in the other/original thread: https://www.linuxquestions.org/quest...al-4175468296/

Reported for closure.

thomas2004ch · 07-03-2013, 03:05 AM

It seems there is to less posts in Solaris, sothat I post my question by LINUX.

anon237 · 07-03-2013, 03:10 AM

All cross-posters think they have a legitimate reason to break the LQ rules.

Just open _one_ thread about a subject, be patient and do not break the rules.

jlliagre · 07-03-2013, 04:25 PM

Quote:

Originally Posted by thomas2004ch

It seems there is to less posts in Solaris, sothat I post my question by LINUX.

That doesn't make sense. Either the issue is related on Solaris and this is the right forum or the issue happen on Linux too and Linux software would be fine.

Back to the topic, how are you trying to kill the process (just "kill 1234" or "kill -15 1234" or something else ) ?

thomas2004ch · 07-04-2013, 03:35 AM

I got the same error no mather with "kill 1234" or "kill -15 1234".

In RedHat-Linux I don't get such error.

jlliagre · 07-04-2013, 03:41 PM

What say:

Code:

type kill
which kill
whence -pv kill
truss -t kill -f kill 1234

?

thomas2004ch · 07-09-2013, 01:10 AM

Code:

-bash-3.2$ type kill
kill is a shell builtin

Code:

-bash-3.2$ which kill
/usr/bin/kill

Code:

-bash-3.2$ whence -pv kill
-bash: whence: command not found

Code:

-bash-3.2$ truss -t kill -f kill 27875
27886:  kill(27875, SIGTERM)                            = 0
-bash-3.2$ /usr/share/jbossas/bin/standalone.sh: kill: bad signal
*** JBossAS process (27875) received  signal ***

jlliagre · 07-09-2013, 02:35 AM

The signal is properly sent. Is the process staying alive after the kill or are you just complaining about the error message ?

What says

Code:

egrep "(trap|kill)" /usr/share/jbossas/bin/standalone.sh

?

thomas2004ch · 07-09-2013, 04:31 AM

The prozess is killed, and I complaining about the error message.

Code:

root@S001AP61-TEST (vws-tst1) # egrep "(trap|kill)" /usr/share/jbossas/bin/standalone.sh
echo "  JBoss Bootstrap Environment"
      trap "kill -HUP  $JBOSS_PID" HUP
      trap "kill -TERM $JBOSS_PID" INT
      trap "kill -QUIT $JBOSS_PID" QUIT
      trap "kill -PIPE $JBOSS_PID" PIPE
      trap "kill -TERM $JBOSS_PID" TERM
            SIGNAL_NAME=`kill -l $SIGNAL`
root@S001AP61-TEST (vws-tst1) #

jlliagre · 07-09-2013, 05:06 PM

The error likely comes from that line:

Code:

SIGNAL_NAME=`kill -l $SIGNAL`

I guess the standalone.sh script starts with "#!/bin/sh" and wrongly assumes a POSIX shell will be run.

Change that line to one of:

Code:

#!/bin/ksh

or

Code:

#!/bin/bash

or

Code:

#!/usr/xpg4/bin/sh

thomas2004ch · 07-10-2013, 02:25 AM

The standalone.sh does starts with "#!/bin/sh". But after I changed this to "#/bin/bash" it is getting worse since I got the message

*** JBossAS process (5240) received signal ***
*** JBossAS process (5240) received signal ***
*** JBossAS process (5240) received signal ***
...
...

endless and I have to reboot the machine.

jlliagre · 07-10-2013, 04:56 AM

Did you try /bin/ksh ?