Unix Manager won't start because there is a touch file
Article ID: KB0085609
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Resolution:
The Linux or Solaris Manager won't start because there's a "touch file". The log message looks like:
JAVA_HOME=/usr/local/java/j2se-1.4
RESIN_CONF=
DS_BASEDIR=
There appears to be a server instance running on another machine which is using DS_BASEDIR='/opt/datasynapse'
If this is not the case, delete the file '/opt/datasynapse/touchfile.dizzy.penthouse.datasynapse.com' and then start the server
The Linux and Solaris Managers use a simple touch file mechanism to prevent you from running multiple instances of a Manager from the same NFS-mounted directory. If the system fails or is shut down while GridServer is running, the touch file will still be present the next time you try to run GridServer. Follow the instructions from the log message by deleting the existing lock file and restarting the Manager.
The Linux or Solaris Manager won't start because there's a "touch file". The log message looks like:
JAVA_HOME=/usr/local/java/j2se-1.4
RESIN_CONF=
DS_BASEDIR=
There appears to be a server instance running on another machine which is using DS_BASEDIR='/opt/datasynapse'
If this is not the case, delete the file '/opt/datasynapse/touchfile.dizzy.penthouse.datasynapse.com' and then start the server
The Linux and Solaris Managers use a simple touch file mechanism to prevent you from running multiple instances of a Manager from the same NFS-mounted directory. If the system fails or is shut down while GridServer is running, the touch file will still be present the next time you try to run GridServer. Follow the instructions from the log message by deleting the existing lock file and restarting the Manager.
Issue/Introduction
Unix Manager won't start because there is a touch file
Feedback
Yes
No
Powered by
