AppSuite:Oxsysreport: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
<div class="title">Creating an OX Support Tarball</div> | <div class="title">Creating an OX Support Tarball</div> | ||
The '/opt/open-xchange/sbin/oxsysreport' tool is able to collect a lot of useful log and system information into a tar archive. This so called OX Support Tarball contains Apache and OX configurations, OX logs and system information. This and a qualified error report makes sure that our support department get all needed details for a fast effective help in a incident | The '/opt/open-xchange/sbin/oxsysreport' tool is able to collect a lot of useful log and system information into a tar archive. This so called OX Support Tarball contains Apache and OX configurations, OX logs and system information. This and a qualified error report makes sure that our support department get all needed details for a fast effective help in a incident. We always recommend to encrypt your E-Mail with our [http://software.open-xchange.com/0x51E6AA1C-oxsupportkey.pub Support Key] when attaching this tarball. | ||
__TOC__ | __TOC__ | ||
| Line 121: | Line 121: | ||
{{VersionFrom|7.6.0}} | {{VersionFrom|7.6.0}} | ||
== Create Thread Dumps (--thread-dump) == | == Create Thread Dumps (--thread-dump) == | ||
This Option normaly should only be used in case it is requested by our Support department. The collected thread dumps may help to identify the root cause of long running threads, critical load und very high cpu usage incidents. In case of a very high cpu incident, please keep by the lack of resources the additional usage of '--skip-compression' in mind. | |||
=== Further Details of Thread Dump Creation === | |||
This Option triggers via 'kill -3' the thread dump creation and logs the related top output into the '/commands/top -d 3 -bHn 5 (thread-dump)' file. The thread dump on none IBM Java Systems will are stored within the open-xchange-console.log, on IBM Java they will be stored separately inside the support tarball as '/tmp/javacore.<timestamp>.txt'. | This Option triggers via 'kill -3' the thread dump creation and logs the related top output into the '/commands/top -d 3 -bHn 5 (thread-dump)' file. The thread dump on none IBM Java Systems will are stored within the open-xchange-console.log, on IBM Java they will be stored separately inside the support tarball as '/tmp/javacore.<timestamp>.txt'. | ||
{{VersionFrom|7.6.0}} | {{VersionFrom|7.6.0}} | ||
== Create Heap Dumps (--heap-dump) == | == Create Heap Dumps (--heap-dump) == | ||
This option normaly should only be used in case it is requested by our Support department. The collected heap dumps are might be helpful in memory or OX service outage incidents, before restarting the service. | |||
First you will get an warning dialog with some system details and with the choice to proceed or to cancel. While creating Java heap dumps your JVM will be stopped and the OX Service is not functional. This step may | First you will get an warning dialog with some system details and with the choice to proceed or to cancel. While creating Java heap dumps your JVM will be stopped and the OX Service is not functional. This step may | ||
take several minutes and it could happen that you need to restart the open-xchange service afterwards manually again. | take several minutes and it could happen that you need to restart the open-xchange service afterwards manually again. | ||
You also have to make sure that you have enough free disk space for processing the data in directories which are defined by '--tempdir' and '--log-archive'. Depending on your ox-scriptconf.sh | You also have to make sure that you have enough free disk space for processing the data in directories which are defined by '--tempdir' and '--log-archive'. Depending on your max heap size '-Xmx' defined by your ox-scriptconf.sh of your groupware Java virtual machine and amount of logs, several gigabyte could be needed! | ||
This | === Further Details of Heap Dump Creation=== | ||
This option triggers the creation of an heap dump which will be stored on none IBM Java Systems within '/commands/jmap -dump:file (heap-dump).bz2' and '/commands/jmap -histo (heap-dump)'. The two jmap files beside without '(heap-dump)' marker contain the stdout/stderr of jmap by running this command. Please note, the '.bz2' suffix (and compression) will be vanished by '--skip-compression' option. | |||
On IBM Java Systems the 'jmap' command is not available and 'kill -ABRT' will do the job instead. This will kill the JVM completely by writing the heap dump, afterwards the dump will be moved within the tarball and processed by the tool jextract. Depending on '--skip-compression' option jextract will compress it as zip or not. The heap dump will be located '/tmp/core.<timestamp>.dmp.zip' within the tarball. The stdout/stderr of jextract will be written to '/commands/jextract core.<timestamp>.dmp (heap-dump)'. On IBM Java the OX groupware service will be restarted by this script . | On IBM Java Systems the 'jmap' command is not available and 'kill -ABRT' will do the job instead. This will kill the JVM completely by writing the heap dump, afterwards the dump will be moved within the tarball and processed by the tool jextract. Depending on '--skip-compression' option jextract will compress it as zip or not. The heap dump will be located '/tmp/core.<timestamp>.dmp.zip' within the tarball. The stdout/stderr of jextract will be written to '/commands/jextract core.<timestamp>.dmp (heap-dump)'. On IBM Java the OX groupware service will be restarted by this script . | ||
| Line 139: | Line 145: | ||
{{VersionFrom|7.6.0}} | {{VersionFrom|7.6.0}} | ||
== Drop Older OX Logfiles from Support Tarball (--exclude-old-logs) == | == Drop Older OX Logfiles from Support Tarball (--exclude-old-logs) == | ||
This option drops all logs (except mandatory) which has a later modified day than the given argument. If logs are dropped they are listed in the overview file '/modified-and-excluded-files.txt' of the tarball. | This option drops all logs (except mandatory) which has a later modified day than the given argument. If logs are dropped they are listed in the generated overview file '/modified-and-excluded-files.txt' of the tarball. | ||
{{VersionFrom|7.6.0}} | {{VersionFrom|7.6.0}} | ||
Revision as of 20:39, 29 May 2014
The '/opt/open-xchange/sbin/oxsysreport' tool is able to collect a lot of useful log and system information into a tar archive. This so called OX Support Tarball contains Apache and OX configurations, OX logs and system information. This and a qualified error report makes sure that our support department get all needed details for a fast effective help in a incident. We always recommend to encrypt your E-Mail with our Support Key when attaching this tarball.
Parameter Overview
| Option | Default Values | Possible Values | Required Tools | |
| --tempdir | /tmp | <directory> | ||
| --logdir | ox_support_infos-<timestamp> | <folder name> | ||
| --log-archive | /tmp/ox_support_infos-<timestamp>.tar.gz | <path to tarball> | ||
| --keep-tmp-files | false | true false | ||
| --thread-dump | false | true false | ||
| --heap-dump | false | true false | jmap, sudo (Only if not IBM Java) | |
| --skip-compression | false | true false | ||
| --exclude-old-logs | disabled | 0 ... n Days | ||
| --exclude-ox-secrets | false | true false | ||
| -h,--help | disabled |
Required Tools
We recommend to check if all required tools are installed before a incident happens. In case your are running IBM Java on e.g. SUSE Linux Enterprise, heap dumps will be created differently. Please note, we do not list package names which are usually get installed in a default installation.
| Tool | Debian | SuSE | Redhead | CentOS | Univention |
| bzip2 | bzip2 | ||||
| jmap | sun-java<version>-jdk openjdk-<version>-jdk | N/A | java-<version>-openjdk-devel | java-<version>-openjdk-devel | openjdk-<version>-jdk |
| sudo | sudo |
Features
Directory for Temporary Process Data (--tempdir)
If you need by e.g. space limitations to switch to a different drive for collecting and processing the data, you can choose here a alternative but existing path. /<tempdir>
Output Log Directory Name (--logdir)
We do not recommend to use this option, but you can choose the output log directory name of the data collection and processing. This will also be the root folder of the OX Support Tarball. Please note, this tempory folder will be removed by default and you need to choose a not existing directory name. /<tempdir>/<logdir>
OX Support Tarball Name and Storage Location (--log-archive)
By this you can choose an alternative tarball name and storage location.
Keep Temporary Process Data (--keep-tmp-files)
If you like to observe or to add additional files for repacking, you can choose this option.
Create Thread Dumps (--thread-dump)
This Option normaly should only be used in case it is requested by our Support department. The collected thread dumps may help to identify the root cause of long running threads, critical load und very high cpu usage incidents. In case of a very high cpu incident, please keep by the lack of resources the additional usage of '--skip-compression' in mind.
Further Details of Thread Dump Creation
This Option triggers via 'kill -3' the thread dump creation and logs the related top output into the '/commands/top -d 3 -bHn 5 (thread-dump)' file. The thread dump on none IBM Java Systems will are stored within the open-xchange-console.log, on IBM Java they will be stored separately inside the support tarball as '/tmp/javacore.<timestamp>.txt'.
Create Heap Dumps (--heap-dump)
This option normaly should only be used in case it is requested by our Support department. The collected heap dumps are might be helpful in memory or OX service outage incidents, before restarting the service.
First you will get an warning dialog with some system details and with the choice to proceed or to cancel. While creating Java heap dumps your JVM will be stopped and the OX Service is not functional. This step may take several minutes and it could happen that you need to restart the open-xchange service afterwards manually again. You also have to make sure that you have enough free disk space for processing the data in directories which are defined by '--tempdir' and '--log-archive'. Depending on your max heap size '-Xmx' defined by your ox-scriptconf.sh of your groupware Java virtual machine and amount of logs, several gigabyte could be needed!
Further Details of Heap Dump Creation
This option triggers the creation of an heap dump which will be stored on none IBM Java Systems within '/commands/jmap -dump:file (heap-dump).bz2' and '/commands/jmap -histo (heap-dump)'. The two jmap files beside without '(heap-dump)' marker contain the stdout/stderr of jmap by running this command. Please note, the '.bz2' suffix (and compression) will be vanished by '--skip-compression' option.
On IBM Java Systems the 'jmap' command is not available and 'kill -ABRT' will do the job instead. This will kill the JVM completely by writing the heap dump, afterwards the dump will be moved within the tarball and processed by the tool jextract. Depending on '--skip-compression' option jextract will compress it as zip or not. The heap dump will be located '/tmp/core.<timestamp>.dmp.zip' within the tarball. The stdout/stderr of jextract will be written to '/commands/jextract core.<timestamp>.dmp (heap-dump)'. On IBM Java the OX groupware service will be restarted by this script .
Skip Support Tarball Compression (--skip-compression)
If this option is set, no compression takes place. This option will effect the support tarball, as well as nested tarballs and possible heap dumps.
Drop Older OX Logfiles from Support Tarball (--exclude-old-logs)
This option drops all logs (except mandatory) which has a later modified day than the given argument. If logs are dropped they are listed in the generated overview file '/modified-and-excluded-files.txt' of the tarball.
Remove Confidential Details from OX Config Files (--exclude-ox-secrets)
This option removes all unexpected, as well as hole confidential known files from the '/opt/open-xchange/etc/' copy of the support tarball. Also confidential information like passwords and keys will be replaced by an white and blacklist heuristic with an <REMOVED BY OXSYSREPORT> marker. The replacement works only on OX properties files and the '/modified-and-excluded-files.txt' file will contain the details of affected files.