...
| Tip | ||
|---|---|---|
| ||
The Abiquo Logs are described in detail in the Troubleshooting section of this wikithe Abiquo wiki for each version of Abiquo. |
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 renamed with date information when they are rotated.
In Abiquo 2.4, the logs arethe log files have the format *.log, for example:
| Code Block |
|---|
am.log api.log bpm-async.log catalina.out nodecollectornars.log ssm.log virtualfactory.log vsm.log |
...
| 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> |
To enable automatic log compression, set the filename extension as .gz for each log file. This will compress each log automatically to GZIP format each midnight with the daily rollover. For instance, if you want to compress nodecollector logs you would issue:
| Code Block | ||
|---|---|---|
| ||
<fileNamePattern>${catalina.base}/logs/nodecollector-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>
|
Disk Requirements
This section describes how to calculate the disk space requirements for the webapp logs. Customers must determine their own logging requirements.
...
Restart the Abiquo Tomcat Server
...
Changes apply within 60 seconds
In versions prior to Abiquo 3.4, after you have made you changes restart the Tomcat server.
In Abiquo 3.4
...
and later versions, do not restart the Tomcat server because modifications will be applied within 60 seconds
...
After modifying the log files you must restart the Abiquo Tomcat Server for changes to take effect.