SpectroSERVER will not start CORBA::NO_PERMISSION or CORBA::TIMEOUT errors
search cancel

SpectroSERVER will not start CORBA::NO_PERMISSION or CORBA::TIMEOUT errors

book

Article ID: 391323

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

When starting the SpectroSERVER it does not properly start and the $SPECROOT/SS/VNM.OUT shows:

 
Mar 18 17:58:14 ERROR TRACE at CsCorbaMgr.cc(1271): Exception: CORBA::TIMEOUT
Minor: 1447165953 
Completion Status: NO
 
 
Mar 18 17:58:14 ERROR TRACE at CsCorbaMgr.cc(1271): Exception: CORBA::NO_PERMISSION
Minor: 1447165953 
Completion Status: NO

 

Cause

Old NAMINGSERVICE.IDB file in use.

Resolution

Review the $SPECROOT/lib/SDPM/partslist/NAMINGSERVICE.IDB file.  Make sure it is current to the release that is installed.  You can review the date with a listing of the directory to see if the file was modified.

Often this issue occurs when an upgrade is done and the entire $SPECROOT/lib/SDPM/partlist folder is replaced with the old directory.  Restart processd and it errors.  

Replace the *.idb files with the originals from the installation version you are running.  Generally this will be the idb files with java references:

NAMINGSERVICE.idb
NCMSERVICE.idb
TELNETD.idb

Restart processd:

systemctl stop processd

systemctl start processd

Additional Information

If you do not have a server that has the current files (they have all been overwritten), open a Broadcom Support ticket and an engineer will assist you with providing the default files for the version you are running.

If this does not resolve the issue, you may need to disable secure corba:

https://knowledge.broadcom.com/external/article?articleId=112340