Prime 3.10 boot time

[mladenp]

Hello,

This isn't look good to me - fresh installation on hyper-v, according to requirements:

Starting Prime Infrastructure...

This may take a while (10 minutes or more) ...

Prime Infrastructure started successfully.

Redirecting to /bin/systemctl restart rsyslog.service
Completed in 2223 seconds
ERROR: You must be root or super-admin (username - "admin") to run this command...

Br,

Mladen

[marce1000]

 - Could be some resource problem , can you (still) login after the boot ? If so check ncs status (e.g.)  , of for instance, check disk io performance with  : ncs run test iops (you may want to stop prime first with ncs stop)

 M.

[mladenp]

prime/admin# ncs run test iops
Testing disk write speed ...
8388608+0 records in
8388608+0 records out
34359738368 bytes (34 GB) copied, 144.644 s, 238 MB/s

Looks OK.

[marce1000]

 - Check other performance parameters during this particular long boot from the Prime VM. Use the hypervisor (hyper-v) monitoring tools for the particular vm, look for cpu , memory and network usage. If needed add additional resources.

 M.

[mladenp]

This ouput is aftrer iops test:

prime/admin# ncs start verbose

Starting Prime Infrastructure...

Reporting Server Heap size = 3072m
XMP Server Heap size = 5120m
Starting Health Monitor

Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
CERT MATCHED :
Updating web server configuration file ...
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Setting UID to 191:110
UID set to 191:110
Starting Health Monitor Server...
Health Monitor Server Started.
Database server started for instance : wcs

Processing Service Name: Database
In startService - serviceType:
In startService - serviceName:Database
Database is already running.

Processing Service Name: FTP Service
In startService - serviceType:
In startService - serviceName:FTP Service

Processing Service Name: TFTP Service
In startService - serviceType:
In startService - serviceName:TFTP Service

Processing Service Name: Matlab
In startService - serviceType:
In startService - serviceName:Matlab

Processing Service Name: Matlab1
In startService - serviceType:
In startService - serviceName:Matlab1

Processing Service Name: NMS Server
In startService - serviceType:
In startService - serviceName:NMS Server
Starting Remoting Service: Matlab Server
Starting Remoting Service: Matlab Server Instance 1
DEPENDENCY CHECK: Database
Started FTP Service
Started TFTP Service
Checking /tmp/remoting_launchout_Matlab1.lock...
Executing startRemoting for Matlab1 ...
Checking /tmp/remoting_launchout_Matlab.lock...
Executing startRemoting for Matlab ...
DB scheme update process starting..
DB scheme update process finished.
Starting NMS Server
/opt/CSCOlumos/classloader-conf:/opt/CSCOlumos/lib/xmp/XMPClassLoader-11.0.1.jar
Unable to initialize com.mathworks.mwswing.MJStartup
Unable to initialize com.mathworks.mwswing.MJStartup

Matlab pid = 35759
system property before init instance: null
Starting Remoting Instance: Matlab Server
Checking for Port 10555 availability... OK
Starting Remoting Service Web Server Matlab Server...
Warning: latest version of matlab app-defaults file not found.
Contact your system administrator to have this file installed
Warning: Duplicate directory name: /opt/CSCOlumos/matlab/toolbox/compiler.
Remoting Service Web Server Matlab Server Started.
Starting Remoting Service Matlab Server...
Remoting 'Matlab Server' started successfully.
Checking for running servers.
Checking if DECAP is running.
00:00 DECAP is not running.
00:00 Check complete. No servers running.
Matlab1 pid = 35736
system property before init instance: null
Starting Remoting Instance: Matlab Server Instance 1
Checking for Port 10755 availability... OK
Starting Remoting Service Web Server Matlab Server Instance 1...
Warning: latest version of matlab app-defaults file not found.
Contact your system administrator to have this file installed
Warning: Duplicate directory name: /opt/CSCOlumos/matlab/toolbox/compiler.
Remoting Service Web Server Matlab Server Instance 1 Started.
Starting Remoting Service Matlab Server Instance 1...
Remoting 'Matlab Server Instance 1' started successfully.
00:07 DECAP setup complete.
Starting Server ...
Done waiting DB initialization
Done waiting DB initialization
Starting SAM daemon...
Done.
Starting DA daemon...
Attempt 1: checking /opt/CSCOlumos/logs/remotingMatlab-0-0.log and /opt/CSCOlumos/logs/remoting_launchout_Matlab.log whether Remoting Service Web Server Matlab.* Started.
Detected: /opt/CSCOlumos/logs/remotingMatlab-0-0.log:04/27/22 13:40:06.026 INFO [system] [main] Remoting Service Web Server Matlab Server Started.
/opt/CSCOlumos/logs/remoting_launchout_Matlab.log:Remoting Service Web Server Matlab Server Started.
Completed launchout Matlab as 35759
Attempt 1: checking /opt/CSCOlumos/logs/remotingMatlab1-0-0.log and /opt/CSCOlumos/logs/remoting_launchout_Matlab1.log whether Remoting Service Web Server Matlab.* Started.
Detected: /opt/CSCOlumos/logs/remotingMatlab1-0-0.log:04/27/22 13:40:11.694 INFO [system] [main] Remoting Service Web Server Matlab Server Instance 1 Started.
/opt/CSCOlumos/logs/remoting_launchout_Matlab1.log:Remoting Service Web Server Matlab Server Instance 1 Started.
Completed launchout Matlab1 as 35736
Creating Application Context
ServerStartupStatus:Creating
ServerStartupStatus:Creating
ServerStartupStatus:Creating
/snip/
ServerStartupStatus:Creating
ServerStartupStatus:Creating
ServerStartupStatus:Creating
ServerStartupStatus:Creating
^CRedirecting to /bin/systemctl restart rsyslog.service
Completed in 1771 seconds

prime/admin# ncs status
Health Monitor Server is running. ( [Role] Primary [State] HA not Configured )
Database server is running
FTP Service is running
TFTP Service is running
Matlab Server is running
Matlab Server Instance 1 is running
NMS Server is running.
Coral Service is running.
WSA Service is running.
SAM Daemon is running ...
DA Daemon is running ...

Boot time is 1770s instead 2220s, without any other interventions. I will check with adminis the workload of this VM.

[Flavio Miranda]

Your concern is about the 10 minutes time or the message:

ERROR: You must be root or super-admin (username - "admin") to run this command.

Prime takes time to boot up, no suprise but this error do not look good.