System Dumps
Three types of system dumps can be created and stored as a compressed file (.tgz) by an AppResponse 11 system:
◼ Logs—includes log files, stack traces, and some additional diagnostics as well as version information and the msot recent core dump.
◼ Cores—includes all core dumps, versions, and all stack traces.
◼ Both—includes the logs and the core dumps.
This section covers the following:
Sysdump employs a storage quota that limits the amount of disk space that can be consumed by a sysdump as it is being created; this prevents a rapidly growing sysdump from consuming an excessive amount of storage before the exhaustion of storage is recognized. Essentially, the amount of space that is available for sysdumps that is not used already is divided in half; if a newly created sysdump reaches the size of half the remaining sysdump space, the sysdump is stopped at that point as marked as “partial.”
Creating a System Dump
1. Go to Administration > System Settings: System Operations, then click the System Dumps tab.
2. Select the Log Type from the drop-down list:
– Logs
– Cores
– Both
3. Optionally, type a customer case ID if you have received one from Riverbed support. The case ID will be prepended to the sysdump filename, and will be inserted also in the file metadata so that it will be easy to recognize which customer case the sysdump is associated with.
4. The Include System Metrics option is selected by default, but you can deselect it if you wish. System metrics occupy a majority of the space used by a sysdump, up to 3.5 GB. You can deselect this option if you’re certain that the salient information in the sysdump is not in the system metrics.
5. Click Generate. The compressed log file is generated in the background and is listed as pending under Available System Dumps until it is completed.