Users Guide
When I run suu -c on a Linux system, I get an error saying, "Problem
executing Inventory Collector." What causes this error and how can I fix it?
The Inventory Collector subcomponent of SUU requires the libstdc++-libc6.2-2.so.3 shared library to be
installed on the system. Install the compat-libstdc++ RPM from RedHat.com or from the Red Hat CD if
you are running a supported version of Red Hat Enterprise Linux on the system or from the SUSE Linux
Enterprise Server CD if you are running SUSE Linux Enterprise Server on the system.
Why do I get a pop-up box titled "Unsafe Removal of Device"?
A part of the SUU update requires updating the backplane firmware. If the operating system queries the
backplane during a flash update and the backplane does not respond, the operating system receives an
indication that the device was removed unsafely. After the backplane firmware is updated, you may see a
screen indicating that a new device was added.
When using the SUU GUI to perform an update, a message is displayed
asking me to see the User's Guide for information on possible causes of why
a server object is not displayed in the tree.
To perform updates, you must be running SUU on a supported system and must have the correct user
access privileges. For Microsoft Windows you must have administrator privileges and for Linux you must
have root privileges. For a list of supported servers and operating systems, see the Dell Systems Software
Support Matrix at www.dell.com/support/manuals.
When I run SUU, why do I not see the Comparison Report? Why can I not
update the system?
SUU requires that Windows users have local administrator privileges. To obtain local administrator
privileges, users must either belong to the local administrators group or use the local administrator
account. On Linux systems, only root (user id 0) users can see the Comparison Report and perform
updates.
Why do I get a message saying, "Inventory operation exceeded specified
time-out" when I try to run a Dell Update Package at the same time as SUU?
Running SUU and a separate DUP concurrently may cause unexpected behavior. SUU runs DUPs in the
background. Therefore, you do not need to run DUPs. Either run SUU or DUP; do not run both at the
same time.
I cannot start SUU. The "Another instance of SUU is already running"
message is displayed even though no other instance of SUU is running on the
system.
To ensure that no other instance of SUU is running on the system: On systems running Windows
operating systems, open the Windows Task Manager, click the Applications tab, and find out if SUU is
running. On systems running Linux operating systems, open a terminal and type the ps -eaf | grep suu
command to find out if SUU is running. If SUU is running, close the application, and restart SUU. If no
other instance of SUU is running, then SUU may have encountered an abrupt shutdown for some reason.
This results in the creation of lock files. To delete these lock files on systems running Windows operating
27