Scontroller disappears after exiting the putty session

Hi all,

on our new AIX 5.3 plattform we are running a domino 8.0.2 Server. We start the server with the server -jc -c & command as , and everything works fine. We can also connect to the serverconsole via the DominoConsole on our clients.

If we now exit the ssh-session (putty or somehing else), we get the message:

There are running jobs.

After e second exit we get the message:

stty: setattr: There is an input or output error.

I think it could be something wrong with stdout or so, but i didn´t find anything.

Some ideas?

best regards

Frank

Subject: scontroller disappears after exiting the putty session

Frank,

Are you starting the server from a startup script or right from the command line in the putty session? If you’re starting it from the command line within the putty session, when you exit the putty session it’ll stop the server.

So, you need to start domino from a startup script. I have one for linux which should be very similar, you should just have to modify it to fit your environment.

Here’s the script I use…

#!/bin/sh

domino Start/stop the Lotus Domino server

chkconfig: 345 01 95

Description: This script is used to start and stop the domino \

server as a background process. It will send \

the serverID password from a file to the server.\

Communication with the server has to be done through \

console, Notes Administrator or webadmin.\

Usage: /etc/rc.d/init.d/domino start|stop|restart|condrestart

process name: server, …

Version 1.1, by LB, 2205-01-07

Change the USER, GROUP, DATA_DIR and BIN_DIR for your server

DOMINO_USER=“notes”
DOMINO_GROUP=“notes”
DOMINO_DATA_DIR=“/opt/ibm/notesdata”
DOMINO_BIN_DIR=“/opt/ibm/lotus/bin”
LOCKFILE=“/var/lock/subsys/domino”

export ODBCINI=“/etc/odbc.ini”

We need a file to put the serverID password in.

Make sure the owner is the Domino owner and the file

permissions are set to 400

SERVER_PASSWD_FILE=“/opt/ibm/notesdata/.domino.pwd”

See if the user that runs this script is root

if [ id -u != 0 ]; then
echo “This script must be run by root only”
exit 1
fi

start() {

First, check if the password file exists,

and if not, exit with an errorcode

if [ ! -f $SERVER_PASSWD_FILE ] ; then

echo “Error: no password file.”

exit 1

fi

Set permission to 400 (read-only-owner)

and ownership to $DOMINO_USER. These next lines are

not necessary if the ownership was set correctly the first time.

chmod 400 $SERVER_PASSWD_FILE
chown $DOMINO_USER.$DOMINO_GROUP $SERVER_PASSWD_FILE

Check we’re not already running

if [ -f $LOCKFILE ] ; then
echo “Domino server apparently already running.”
exit 1
fi

Two ways to run the server (comment one of them out)

1. With the output of the console redirected to /var/log/domino.log

Be sure to change the logrotate daemon.

2. With the output of the console redirected to /dev/null

echo -n “Starting domino server…”

Version with logfile

su - ${DOMINO_USER} -c “cd ${DOMINO_DATA_DIR};
cat ${SERVER_PASSWD_FILE} | ${DOMINO_BIN_DIR}/server” \

/var/log/domino 2>&1 &
RETVAL=$?
if [ “$RETVAL” = “0” ] ; then
touch $LOCKFILE > /dev/null 2>&1
fi

Version without logfile

su - ${DOMINO_USER} -c "cd ${DOMINO_DATA_DIR};\

cat ${SERVER_PASSWD_FILE} |\

${DOMINO_BIN_DIR}/server" > /dev/null 2>&1 &

echo “done.”
}

stop() {
echo -n "Stopping Domino server. "
su - ${DOMINO_USER} -c “cd ${DOMINO_DATA_DIR}; ${DOMINO_BIN_DIR}/server -q”
RETVAL=$?

RETVAL is 38 on normal shutdown - what does that mean?

Users should test this on their own systems . . .

if [ $RETVAL -lt 50 ] ; then
rm $LOCKFILE
fi
}

restart() {
stop
start
}

See how we were called.

case $1 in
start)
start
;;
stop)
stop
;;
restart)
stop
start
;;
condrestart)
[ -f $LOCKFILE ] && restart
;;
*)
echo “Usage: domino {start|stop|restart|condrestart}”
exit 1
;;

esac

End of the domino script

exit 0

Keith

http://www.keithstric.com