program terminate by signal 1

[kholikt]

One of my SAP application support they are running some job from the telnet session. Some how after two hours plus the telnet session is timeout. They get the error message that this job was terminated by signal 1.

I have asked him to run the job using nohup but the problem still.

I was wondering is this because the job itself is having some problem.

[Rajeev Shukla · Accepted solution]

To diagnose really if its terminal timing out problem of program problem. remove the timing out from terminal session by exporting TMOUT=0

then run the program and see if you still get the error.

Rajeev

[Michael Tully]

Check to see if there is a timeout being used by the users shell. (TMOUT, autologout)

The first places to check are:
/etc/profile ~user/.profile

Is there a 'trap' definition within the program that is being run?

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[Bill Hassell]

How was the job started? The shell timeout will have no effect if the user simply starts the program from the shell prompt. However, if the user decides to put the process into the background with the & character, then the shell prompt returns and the timer starts. Signal 1 is known as SIGHUP and occurs when the connection to the controlling terminal has been terminated. nohup will indeed protect the process from seeing this (and other kill signals) but a bit more information is needed about how the process is started.

[kholikt]

Thank to all the reply. According to the developer he is running the program in the foreground. Apart from this he has tried nohup program but still get signhup problem.

This is my /etc/profile

# more /etc/profile

# @(#) $Revision: 74.2 $

# Default (example of) system-wide profile file (/usr/bin/sh initialization).
# This should be kept to the bare minimum every user needs.

# Ignore HUP, INT, QUIT now.

trap "" 1 2 3

# Set the default paths - Do NOT modify these.
# Modify the variables through /etc/PATH and /etc/MANPATH

PATH=/usr/bin:/usr/ccs/bin:/usr/contrib/bin
MANPATH=/usr/share/man:/usr/contrib/man:/usr/local/man

# Insure PATH contains either /usr/bin or /sbin (if /usr/bin is not available).

if [ ! -d /usr/sbin ]
then
PATH=$PATH:/sbin

else if [ -r /etc/PATH ]
then

# Insure that $PATH includes /usr/bin . If /usr/bin is
# present in /etc/PATH then $PATH is set to the contents
# of /etc/PATH. Otherwise, add the contents of /etc/PATH
# to the end of the default $PATH definition above.

grep -q -e "^/usr/bin$" -e "^/usr/bin:" -e ":/usr/bin:" -e ":/usr/bin$" /etc/PATH
if [ $? -eq 0 ]
then
PATH=`cat /etc/PATH`
else
PATH=$PATH:`cat /etc/PATH`
fi
fi
fi

export PATH

# Set MANPATH to the contents of /etc/MANPATH, if it exists.

if [ -r /etc/MANPATH ]
then
MANPATH=`cat /etc/MANPATH`
fi

export MANPATH

# Set the TIMEZONE

if [ -r /etc/TIMEZONE ]
then
. /etc/TIMEZONE
else
TZ=MST7MDT # change this for local time.
export TZ
fi

# Be sure that VUE does not invoke tty commands

if [ ! "$VUE" ]; then

# set term if it's not set

if [ "$TERM" = "" -o "$TERM" = "unknown" -o "$TERM" = "dialup" -o "$TERM" = "network" ]
then
eval `ttytype -s -a`
fi

export TERM

# set erase to ^H, if ERASE is not set
if [ "$ERASE" = "" ]
then
ERASE="^H"
export ERASE
fi
stty erase $ERASE

# Set up shell environment:

trap "echo logout" 0


# This is to meet legal requirements...

cat /etc/copyright

# Message of the day

if [ -r /etc/motd ]
then
cat /etc/motd
fi

# Notify if there is mail

if [ -f /usr/bin/mail ]
then
if mail -e
then echo "You have mail."
fi
fi

# Notify if there is news

if [ -f /usr/bin/news ]
then news -n
fi

# Change the backup tape

if [ -r /tmp/changetape ]
then echo "\007\nYou are the first to log in since backup:"
echo "Please change the backup tape.\n"
rm -f /tmp/changetape
fi

fi # if !VUE

# Leave defaults in user environment.

trap 1 2 3
umask 022

User is using c shell

I don't see any autologout or tmout variable set in the cshrc