When LiveUpdate runs manually or scheduled, the error message "Another instance of LiveUpdate is already running" appears in the Domino console and Symantec Mail Security for Domino (SMSDOM) logs.
"Another instance of LiveUpdate is already running"
When LiveUpdate starts, a "smsdulck" file is created in the Temp folder.
If this file is present when LiveUpdate runs, the error "Another instance of liveupdate is already running" appears in the Domino console and in the SMSDOM server messages.
The "smsdulck" file may not be deleted if LiveUpdate does not exit gracefully or Domino server is terminated abnormally while LiveUpdate is running.
In order to resolve this problem, it is first recommended to check whether LiveUpdate is in fact still running by doing one of the following:
Check the list of running tasks or processes and look for entries starting with "java" or "java.exe". No processes should be visibile.
Check the LiveUpdate log file "liveupdt.log" and ensure LiveUpdate has finished its last session.
If the above checks are negative (i.e. no "Java" processes and clean termination of "liveupdt.log" file), then it's recommended to check whether the "smsdulck" file exists on the system and delete it manually. This file may be present at the following locations:
Windows 2008: C:\Windows\Temp UNIX/Solaris/AIX: /tmp
Deleting the file will allow to run LiveUpdate properly from the SMSDOM Admin interface.
Workaround A workaround script is available for Linux, Solaris and AIX servers. The script can be scheduled to run every 15 or 30 minutes and will ensure no lock files are present in the temp folder when no LiveUpdate is running.
How to implement the script
Download the script below and copy it to a folder in the Domino server filesystem (e.g. /opt)
Edit the crontab file for the root user (or any other account if needed) to run the script every 30 minutes.
Example on AIX:
cp smschkdulck.sh /opt
crontab -e root
add the following line to the crontab: "0,30 * * * * /opt/smschkdulck.sh >> /tmp/smschkdulck.log 2>&1
save the crontab file
Technical Information By default, LiveUpdate is configured to run 3 times at 20 minute intervals, which means that it can take up to 40+ minutes to stop if there are network issues or other problems preventing LiveUpdate from connecting on the first attempt.
Best Practices In order to prevent similar problems to occur again, it is recommended to review the automated tasks taken when the server is shutdown or rebooted, and include operations/commands to cleanup all temporary locations/folders used in the system.