As stated in above section, core/coredump files formatted as core-* and coredump-* can be downloaded from System > Maintenance > Backup & Restore > GUI File Download/Upload.
It’s also necessary to collect some other logs that can help to analyze the coredump causes.
Please collect these logs:
Download the archived debug log with one-click button (System > Maintenance > Debug > Download).
The archive file includes most logs under /var/log/debug/, /var/log/gui_upload and some other system directories.
Please remember that you have to enable System > Config > Feature Visibility > Debug at first.
Download core/coredump files (named as core-* and coredump-*), detailed dmesg logs, and other logs (not archived in the debug log, but can be seen directly in GUI File Download/Upload).
It’s better to check the files in the one-click downloaded debug file to see which logs are not included, then just download them to avoid duplicate download.
/var/log/dmesg/: #You can archive this directory first by executing “tar czf /var/log/gui_upload/dmesg.tar.gz /var/log/dmesg/”
ha_event_log: including very detailed HA init, switch, config-sync, heartbeat logs
Download Event logs from Log&Report > Log Access > Download, selecting the corresponding time period;
- In 6.4.0, core and coredump files will be achieved and put a copy into /var/log/debug/tmp when one clicks to download the debug log (System > Maintenance > Debug > Download Log),
In 6.4.1, 7.0.0 and later releases, all kernel core and coredump files will not be achieved and can be only downloaded from /var/log/gui_upload. Please refer to the screenshot below, one can also compress a specific file before download it:
- Provide core/coredump files, dmesg and other necessary logs to the support team for further investigation.
Usually you only needs to collect core/coredump, dmesg and other logs and provide them to support team for further analysis.