To collect log files from the system in case of problem solving, this can also be done via the CLI interface.

  1. Enable the CLI access
  2. Login via SSH client using the CLI login credentials
  3. Enter: sysdump-all
  4. sysdumps are created


Mounting tmpfs done...
SYSDUMP start...
creating local sysdump for: base-dm-int-7c:2f:80:c6:e5:c2
N870: executing db.dump
N870: executing dlsd.dump
N870: executing gib.dump
N870: executing mosquitto.dump
N870: executing system.dump
Sysdump done at: 2020-09-08-154929 (file: /tmp/sysdump/sysdump-base-dm-int-7c:2f:80:c6:e5:c2/sysdump.base-dm-int-7c:2f:80:c6:e5:c2; size: 576.0K; took: 152 [sec])
generating local dump file at: /tmp/sysdump/sysdump-base-dm-int-7c:2f:80:c6:e5:c2/sysdump.base-dm-int-7c:2f:80:c6:e5:c2.tar.gz
sysdump for hostname: base-dm-int-7c:2f:80:c6:e5:c2, ip: already exists! Skipping...
bases are excluded by default (add -b as cmdline option to include them)
SYSDUMP finished (/tmp/pub//sysdump-all.tar, 88.0K, 161 [sec])

Writing sysdump file to default location makes the dump-file downloadable from web-browser via https://<device-ip>/pub/sysdump-all.tar

More information:

Usage: sysdump-all [<options>]
-h Show this help
-c add core dump
-s add css_ramdump
-x exclude rotated /var/log/messages*.gz
-b add sysdumps from all external bases
-i exclude last incident sysdump
-e exclude database dump
-d define output directory of the generated sysdump-all.tar file (dflt: /tmp/pub/sysdump-all.tar)

  • No labels