supportconfig throws out error "find: Symbolic link.."

SUSE Product Topics SLES Configure-Administer
1

since update supportconfig to supportutils-3.0-30.1.noarch.rpm I get following errors

find: Symbolic link `/sys/class/drm/controlD64/device/subsystem/devices/0000:00:1d.0/firmware_node/subsystem/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/physical_node/pci_bus/0000:05/subsystem/0000:00/device/0000:00:1d.1/driver/0000:00:1d.2/usb4/subsystem/devices/usb1/driver/usb3/3-2/3-2:1.0/0003:04F2:0200.0001/subsystem/devices/0003:04F2:0200.0003/driver/module/drivers/usb:usbhid/3-2:1.2/input/input5/mouse1/subsystem/input6/device/subsystem/devices/serial8250/tty/ttyS1/subsystem/tty27/subsystem' is part of a loop in the directory hierarchy; we have already visited the directory to which it points.

Comment on Coolsolution https://www.suse.com/communities/conversations/free_tools/supportconfig-linux/
is not possible.

anyone knows about ?
cheers
BB

2

Is it just the presence of the error that is concerning, or are you
needing to get into a recursive search for some reason? What version of
SLES, with which patches? To what does this link point, exactly? It
sounds like a generally good thing for ‘find’ to do, not recursively
following links, so unless there is something else I’d probably ignore the
warning.

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

3

Supportconfig from supportutils-3.0-30.1 does not work anymore, fails to create the tar at the end.
the last I see is:

[QUOTE]=============================================================================
Support Utilities - Supportconfig
Script Version: 3.0-26
Script Date: 2014 04 03

Detailed system information and logs are collected and organized in a
manner that helps reduce service request resolution times. Private system
information can be disclosed when using this tool. If this is a concern,
please prune private data from the log files. Several startup options
are available to exclude more sensitive information. Supportconfig data is
used only for diagnostic purposes and is considered confidential information.
See http://www.novell.com/company/legal/privacy/

Gathering system information
Data Directory: /var/log/nts_compaq_140414_1648

Basic Server Health Check… Done
RPM Database… Done
Basic Environment… Done.
.snip
.
.snip
KVM… Skipped
X… [/QUOTE]

4

Have you tried excluding the ‘X’ stuff, since most servers don’t need
those data anyway?

Code:

supportconfig -x X

Another option may be to enable debugging so you can see exactly what is
searching down there so we can create a bug report.

Also, what about the other questions from before to see if there are
similar systems that can be tested?

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…