DX Spectrum : IcmpServer.cc(897) error in VNM.OUT
search cancel

DX Spectrum : IcmpServer.cc(897) error in VNM.OUT

book

Article ID: 211546

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

The following error is seen in the $SPECROOT/SS/VNM.OUT file:

SPC-SHD-29021:
**************************************************************************
The following output is intended to facilitate debugging, please forward
to CA technical support.  The files listed are not part of the customer
installation of SPECTRUM.
**************************************************************************

Mar 19 13:10:14 ERROR TRACE at IcmpServer.cc(897): socket() failed for address 0.0.0.0, Cs_sock_get_last_error() = 1
Mar 19 13:10:14 ERROR TRACE at IcmpServer.cc(897): socket() failed for address ::, Cs_sock_get_last_error() = 1

Environment

Release : Any Spectrum version running on Linux

Component : Spectrum Core / SpectroSERVER

Cause

It looks like SpectroSERVER doesn’t have the proper capabilities to create the socket for ICMP.

Resolution

NOTE: The following commands use "/usr/Spectrum" as the Spectrum root directory. Your Spectrum maybe installed in a different Spectrum root directory. If so, replace "/use/Spectrum" with your Spectrum root directory.

Run the following command as the root user:

setcap cap_net_bind_service,cap_net_raw+ep /usr/Spectrum/SS/SpectroSERVER

To verify the above command ran correctly, run the following command:

getcap /usr/Spectrum/SS/SpectroSERVER

Your output should look similar to the following:

/usr/Spectrum/SS/SpectroSERVER = cap_net_bind_service,cap_net_raw+ep

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/23-3/installing-and-upgrading/fresh-install/install-ca-spectrum-with-non-root-user.html 

Note:

If the above procedure with setcap does not work as expected, and keep getting the same error message in VNM.OUT, verify the following at the Operating System level on the server.

Open the /etc/mtab and verify if it has the entry nosuid.

The mtab file lists all currently mounted filesystems along with their initialization options. 

If the filesystem is mounted with 'nosuid' option, this is preventing the 'setcap' command to work, even though it returned no error messages.

Removing the 'nosuid' option and restarting SpectroSERVER should work as expected.  

nosuid - do not set SUID/SGID access on this partition (prevent the setuid bit).

suid/nosuid - Permit/Block the operation of suid, and sgid bits.