What's the reason of a full root volume on the appliance, logs?
I cannot acces my monitoring GUI because there is no space left, i cannot even start yast on the console...
what to do, please help.
Please login to VMTurbo via SSH and follow the steps below.
1. echo "" > /var/log/tomcat/catalina.out
2. rm /srv/tomcat/data/repos/customer.markets.topology
3. rm /srv/tomcat/data/repos/customer.repos.topology
4. service tomcat restart.
This should resolve the issue you are having.
Thanks indeed!, works like a charm!
The underlying cause of the problem is some very verbose debug messages that incorrectly appear in the logs in 5.4. This will be fixed in a soon-to-be available patch. It's a deceptive problem because the debug messages don't "turn themselves on" until a server has run for about a week.
You can work around the problem without restart the server by executing the following commands:
$ cd /var/log/tomcat
$ xzcat --compress catalina.out >catalina.out-some-suffix
$ truncate --size=0 catalina.out
The "xzcat" command is optional; it saves the current log file in compressed format. Change "some-suffix" to something appropriate - e.g., you could imitate the date format used by the automatic log file rollover mechanism. If you don't care about the older logs, just skip this line and do the "truncate" immediately.
The new log file will immediately start growing, and you'll eventually run out of space again. (This typically takes several days, but watch your own system to get an estimate.)
5.4.1, the release that fixes the underlying issue, is now live.
Retrieving data ...