...
| Tip | ||
|---|---|---|
| ||
The Abiquo Logs are described in detail the Troubleshooting section of this wiki. |
Log files
A current log is created for each webapp in the directory \{catalina.base}/logs/
In a standard install, this is /opt/abiquo/tomcat/logs. The logs are named after the webapps and then renamed with date information when they are rotated.
In Abiquo 2.4, the standard configuration is as follows. This example shows the log for "nodecollector", which logs are:
| Code Block |
|---|
am.log
api.log
bpm-async.log
catalina.out
nodecollector.log
ssm.log
virtualfactory.log
vsm.log |
The logback config file is in WEB-INF/classes in each webapp and can be edited.
For example, for the nodecollector webapp, the file would be in /opt/abiquo/tomcat/webapps/WEB-INF/classes/log????
(Nodecollector is the name of the webapp for the Discovery Manager Remote Service).
Example
The following example shows the standard configuration log for "nodecollector" ...
| Code Block |
|---|
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${catalina.base}/logs/nodecollector-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
<timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<maxFileSize>50MB</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy> |
...
This means that the logs are kept indefinitely. , which can cause the system disk to fill up.
Set the maxHistory size for each log file by adding a line after maxFileSize and changing the \{NUMBER OF FILES TO KEEP} as shown in the example below.
| Code Block |
|---|
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${catalina.base}/logs/nodecollector-%d{yyyy-MM-dd}.%i.log</fileNamePattern>
<timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<maxFileSize>50MB</maxFileSize>
<maxHistory>{NUMBER OF FILES TO KEEP}</maxHistory>
</timeBasedFileNamingAndTriggeringPolicy>
</rollingPolicy> |
...
At the moment 2.4 doesn't delete historirc logs from webapps, this may lead ( and actually it did ) to an usable platform because of full filesystem.
I'm going to open an improvement but I think is really important for new customers to configure this properly at installation time. Could you please include this as a note on the installation documentation?On my first mail you can find the steps to configure the deletion and the link to official documentation, it would be something like:
What do you think?
Regards,
Sergio
---------- Forwarded message ----------
From: Ignasi Barrera <ignasi.barrera@abiquo.com>
Date: Thu, May 30, 2013 at 9:03 AM
Subject: Re: Logback deletion of older logs.
To: Sergio Pena <sergio.pena@abiquo.com>
Cc: Equipo desarrollo Abiquo <developers@abiquo.com>, Support Engineers <support.engineers@abiquo.com>We can open an improvement in Jira and tell customers to configure they log files as they want. The logback config file is in WEB-INF/classes in each webapp and can be edited.
El 29/05/2013 22:25, "Sergio Pena" <sergio.pena@abiquo.com> escribió:
...