I’ve just installed Domino 6.0.3 on SuSE Linux 8.0. All is working great, except I’m having a problem getting Domino to stop prior to my scheduled TSM backup.
We’ve got the 5.2 TSM client running on the Linux server. TSM allows you to add “pre” and “post” commands in the dsm.sys file which are used to stop an application prior to the backup starting, and to then restart the application once the backup has completed. I’ve used this TSM feature on NT to stop the Domino service prior to the backup and then restart it afterwards.
I’m having a problem getting this to work on Linux. Here’s the stop line from my TSM dsm.sys file:
PRESCHEDULECMD “/etc/init.d/domino stop > /dev/null 2>&1”
The “domino” shell starts the domino server, which uses the “startup” shell to actually start and stop the server. The “domino stop” command works FINE when I run it manually from the console. However, when launched from TSM, the command successfully stops domino, but the following tasks “hang” and never complete:
root 9372 9370 0 16:40 pts/1 00:00:00 /bin/bash /etc/init.d/domino stop
domadmin 9390 9372 0 16:40 pts/1 00:00:00 su - domadmin -c cd /smm/notesdata; /smm/lotus/bin/server -q
domadmin 9392 9390 0 16:40 pts/1 00:00:00 -su -c cd /smm/notesdata; /smm/lotus/bin/server -q
domadmin 9407 9392 0 16:40 pts/1 00:00:00 -su -c cd /smm/notesdata; /smm/lotus/bin/server -q
domadmin 9487 9407 0 16:40 pts/1 00:00:00 stty sane
I’ve found it’s this last task (stty sane) that’s causing the problem. Apparently, there is a permissions problem with this task running, and it simply hangs, causing the parent tasks to hang as well. The net result is that my backup never starts, since the “domino stop” command never completes.
I’ve figured out a way around this, but I don’t like my solution and want a better answer. The …/lotus/notes/latest/linux/startup script (linked to the Domino “server” command) which ships with Domino starts with the following three lines:
if [ a$domcon_pbits = “a” ]; then # if we are using zOS Native console, we are not tty based
trap “stty sane” 0 # restore terminal echo at exit
fi
I’ve found that I can bypass the hang problem by modifying the second line in the script to the following:
sudo trap “stty sane” 0 # restore terminal echo at exit
Using “sudo” runs the “stty” command as root, which seems to resolved the problem. As you probably know, Domino must be started under the Domino installation userid and not root.
Can someone help me understand why this problem occurs, and how better to resolve it?
Thanks…