Page 1 of 1

Can’t pull diagnostic logs on Linux

PostPosted: Tue Sep 18, 2018 3:25 am
by Seth Goldin
Wondering why I can’t pull a diagnostic log on Linux. Shell output below. This is the BMD-provided build of CentOS 7.3. Did my installation of 15.1.0.023 break something? Should I try installing 15.1.0.024 on top of this, or was that only a fix for Windows?

[sgoldin@seth-linux-localdomain scripts]$ sudo sh script.getlogs.v4
[sudo] password for sgoldin:
cp: cannot stat ‘/opt/resolve/logs/site1.log’: No such file or directory
cp: cannot stat ‘/opt/resolve/logs/ResolveDebug.txt.backup’: No such file or directory
cp: cannot stat ‘/opt/resolve/crash_archive.txt’: No such file or directory
cp: cannot stat ‘/etc/X11/XF86Config*’: No such file or directory
cp: cannot stat ‘/var/log/XFree86.*.log’: No such file or directory
cp: cannot stat ‘/etc/X11/xorg.conf’: No such file or directory

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

If you want to list systemd services use 'systemctl list-unit-files'.
To see services enabled on particular target use
'systemctl list-dependencies [target]'.

error reading information on service crond: No such file or directory


Sent from my iPhone using Tapatalk

Re: Can’t pull diagnostic logs on Linux

PostPosted: Tue Sep 18, 2018 6:14 am
by Dwaine Maggart
It's normal to see several error messages if you manually run script.getlogs.v4

If the files in the attached image are in the .tgz file, it's working correctly.

linux_log2.PNG
linux_log2.PNG (12.89 KiB) Viewed 1511 times

Re: Can’t pull diagnostic logs on Linux

PostPosted: Tue Sep 18, 2018 12:56 pm
by Seth Goldin
No actual file is being outputted to the desktop. No .tgz file. I also tried escalating privileges with sudo and su, but no log is outputted.


Sent from my iPhone using Tapatalk

Re: Can’t pull diagnostic logs on Linux

PostPosted: Tue Sep 18, 2018 2:31 pm
by Seth Goldin
Just installed 15.1.0.025 to Linux and now I can pull logs from the GUI or the CLI. Thanks.