Smarts NCM: Report Advisor fails to start with error; Starting tomcat: touch: cannot touch /usr/tomcat/apache-tomcat-6.0.36/logs/catalina.out: Read-only file system
Article ID: 331055
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
When we try to start the tomcat service for the Report Advisor it fails with the following error:
Starting tomcat: touch: cannot touch `/usr/tomcat/apache-tomcat-6.0.36/logs/catalina.out': Read-only file system.
When we try to start the tomcat service for the Report Advisor it fails with the following error:
Starting tomcat: touch: cannot touch `/usr/tomcat/apache-tomcat-6.0.36/logs/catalina.out': Read-only file system.
Environment
VMware Smart Assurance - NCM
Cause
Catalina.out is the primary log file used by the tomcat service as implemented by the Apache foundation and the file must either already exist in a writable state, or must be able to be created in the path tomcat is configured to use or tomcat will be unable to start. In this case, a Linux OS based 'touch' command is failing to create the file. This would only ever be attempted if the existing file was not detected by tomcat.
Resolution
1. Log into a Linux shell on the Report Advisor (RA) host as 'root'.
2. Set shell session variables by running the followign command:
source /etc/voyence.conf
3. Run the following commands to show permissions and status of the path mentioned in the error message you receive when attempting to start the tomcat service:
ls -latrh $TOMCAT_HOME
(or)
stat -c "%a %n" ./$TOMCAT_HOME/logs
It is important that the environment variable be used as shown in the above instructions since RA application depends upon the content of this environment variable.
4. Check if the logs directory has required permissions as below.
Ex:
If not set the permissions on 'logs' folder by navigating to $TOMCAT_HOME using below command:
cd $TOMCAT_HOME
chmod 750 logs
5. If required permissions are already set on directory and you still face this error, then the entire file system is marked read-only, that's the reason creation of the catalina.out is failing.
a)Try to create a temp/test file manually under $TOMCAT_HOME/logs using touch command Ex: touch temp.txt
b)If the file gets created, write something to file and try saving it.
c)If the file creation/write & save fails, then its the issue with the Linux machine(file system permissions issue).
Please contact your Linux administrator for fixing the permissions on file system.
2. Set shell session variables by running the followign command:
source /etc/voyence.conf
3. Run the following commands to show permissions and status of the path mentioned in the error message you receive when attempting to start the tomcat service:
ls -latrh $TOMCAT_HOME
(or)
stat -c "%a %n" ./$TOMCAT_HOME/logs
It is important that the environment variable be used as shown in the above instructions since RA application depends upon the content of this environment variable.
4. Check if the logs directory has required permissions as below.
Ex:
If not set the permissions on 'logs' folder by navigating to $TOMCAT_HOME using below command:
cd $TOMCAT_HOME
chmod 750 logs
5. If required permissions are already set on directory and you still face this error, then the entire file system is marked read-only, that's the reason creation of the catalina.out is failing.
a)Try to create a temp/test file manually under $TOMCAT_HOME/logs using touch command Ex: touch temp.txt
b)If the file gets created, write something to file and try saving it.
c)If the file creation/write & save fails, then its the issue with the Linux machine(file system permissions issue).
Please contact your Linux administrator for fixing the permissions on file system.
Feedback
Yes
No
Powered by
