Hi all,
A customer got this message when trying to start the Orchestrator services.
This is the error message :
Starting tcServer
=== Checking vCAC Configuration...
Found in /etc/vcac/security.properties: csp.host
Found in /etc/vcac/security.properties: vmidentity.websso.host
Found in /etc/vcac/security.properties: vmidentity.websso.tenant
Found in /etc/vcac/security.properties: vmidentity.websso.solution
Found in /etc/vcac/security.properties: certificate.store.file
Found in /etc/vcac/security.properties: certificate.store.password
Found in /etc/vcac/security.properties: csp.component.registry.url
Found in /etc/vcac/security.properties: certificate.store.websso.alias
Found in /etc/vcac/security.properties: certificate.store.ssl.alias
websso, Apr 24, 2014, trustedCertEntry,
Certificate fingerprint (SHA1): E6:DE:4E:D1:09:18:AE:30:E1:D6:2C:18:5A:92:58:CA: E9:59:6E:FE
apache, Apr 24, 2014, PrivateKeyEntry,
Certificate fingerprint (SHA1): 25:5C:B1:9C:E7:8E:AD:34:C9:E2:1A:B9:D9:8B:79:0B: B4:41:11:4A
VCAC configuration seems to be ok.
vCO is already registered. Starting it directly...
Using CATALINA_BASE: /var/lib/vco/app-server
Using CATALINA_HOME: /usr/local/tcserver/vfabric-tc-server-standard/tomcat-7.0 .35.B.RELEASE
Using CATALINA_TMPDIR: /var/lib/vco/app-server/temp
Using JRE_HOME: /usr/java/jre-vmware
Using CLASSPATH: /usr/local/tcserver/vfabric-tc-server-standard/tomcat-7.0 .35.B.RELEASE/bin/bootstrap.jar:/usr/local/tcserver/vfabric-tc-server-standard/t omcat-7.0.35.B.RELEASE/bin/tomcat-juli.jar
Using CATALINA_PID: /var/lib/vco/app-server/logs/tcserver.pid
/usr/local/tcserver/vfabric-tc-server-standard/tomcat-7.0.35.B.RELEASE/bin/catal ina.sh: line 400: echo: write error: No space left on device
Status: UNKNOWN due to Tomcat 7-based instance being started as a foreground process
The issue seems to come because there wasn't enough space on the disk to start the service. He removed some java Logs (see the image attached) and started manually the services and everything worked.
I suggested to remove the temp and old log files from Tomcat but he wants to know if the issue will appear again and why tomcat didn't delete automatically the files.
I tried to look for it in Internet and the GSS but I couldn't find anything.
Anybody knows something about it please?
Thanks in advance.