Symptom
FTD CLI command "tail-logs" erroring with script traceback citing "No such file or directory: '/ngfw/var/log/log'"
Conditions
Attempting to use FTD CLI command "tail-logs"
Workaround
Use pigtail or tail commands from expert mode for log review
OR
via expert mode, remove the broken symlink at /ngfw/var/log/log
Further Problem Description
The issue occurs when unit has been upgraded from a previous "major" version and there is a leftover broken symlink from the older software version, example:
admin@2110:/ngfw/var/log$ ls -alsh log
0 lrwxrwxrwx 1 root root 101 Mar 12 2021 log -> /opt/cisco/csp/applications/cisco-ftd.6.4.0.102__ftd_001_JMX2139Y0DGVMM6P61/app_data/Volume/6.4.0/log
admin@2110:/ngfw/var/log$ file log
log: broken symbolic link to /opt/cisco/csp/applications/cisco-ftd.6.4.0.102__ftd_001_JMX2139Y0DGVMM6P61/app_data/Volume/6.4.0/log
admin@2110:/ngfw/var/log$ cat /etc/sf/patch_history
6.4.0-102
6.4.0.7-53
6.4.0.9-62
6.6.4-59
6.6.5-81
7.0.1-84
