SSM startup problem after server reboot

[jbrzozowski]

Hi,

After restarting the server, the instance used for Central User Administration does not work properly, you can not log into the system through sapgui. In the log file: /usr/sap/SSM/DVEBMGS30/log/sapccm4x/sapstartsrv_ccms.log:

Mon Oct 21 13:15:37 2024
INFO: Runtime status of ABAP Instance SSM ssm_SSM_30 active
INFO: Runtime status of Java Instance SSM ssm_SSM_30 Starting the processes

[Thr 140737302972160]
Mon Oct 21 13:15:41 2024
INFO: Re-Initialization of CCMS Agent
INFO: ...stop Method Dispatcher.
INFO: Waiting for 1st method dispatcher thread to exit...

[Thr 140737295599360]
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LONGRUN_TD exits

[Thr 140737297700608]
Mon Oct 21 13:15:47 2024
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LOCAL_TD exits

[Thr 140737302972160]
INFO: Waiting for 2nd method dispatcher thread to exit...
INFO: Cleanup for static lib rfcoslib.
INFO: Cleanup for static lib alloglib.
INFO: Cleanup for static lib aljsflib.
INFO: ... download Shared Memory content into file system.
INFO: Download Agent Alerts and some current values to /usr/sap/SSM/DVEBMGS30/log/ALAGENTALERTS.
INFO: ... Download successful. Disconnecting from CCMS Memory.

Mon Oct 21 13:15:50 2024
INFO: ... reconnect to CCMS Memory.

INFO: Attached to Shared Memory Key 73 (size 60211232), no pool used

INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for ssm_SSM_30, created with version CCMS version 20060508, 64 bit single threaded, compiled at Jan 15 2013, kernel 7200_20020600_401, platform 390 (AMD/Intel x86_64 with Linu]
segment status WARM_UP
segment started at Mon Oct 21 13:15:21 2024
segment version 20060508

INFO: ALMTTREE, ALALERTS, ALPERFHI already uploaded to shared memory.
TID not found for [\###\MoniInfra_ssm_SSM_30\Tooldispatching (CCMS agent)\Messages]
TID not found for [\###\MoniInfra_ssm_SSM_30\Tooldispatching (CCMS agent)\Messages]
TID not found for [\###\MoniInfra_ssm_SSM_30\Tooldispatching (CCMS agent)\Messages]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_dispatcher*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_dispatcher*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_dispatcher*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_dispatcher*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_server*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_server*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_server*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_server*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_sdm*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_sdm*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_sdm*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\OperatingSystem\Monitored Processes\*jlaunch*-DSAPINFO=SSM_30_sdm*\ ssmadm: Process Count]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Status]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Availability]
TID not found for [\###\ssm_SSM_30\JAVA InstanceAsTask\Availability]
TID not found for [\###\Java Instance: ssm_SSM_30\Garbage Collection\GC of server0\Average Proportion of Total Time]
TID not found for [\###\Java Instance: ssm_SSM_30\Garbage Collection\GC of server0\Average Proportion of Total Time]
INFO: /usr/sap/SSM/DVEBMGS30/log/ALAGENTALERTS uploaded to shared memory.
INFO: updating shared memory runtime information of sapccm4x

INFO: Loading static lib rfcoslib with trace level 0.
RFCOSLIB: INFO: current trace level is 1 
RFCOSLIB: INFO: Semaphore Handling initialization successful.
RFCOSLIB: INFO: Trying to Register Objects 
RFCOSLIB: INFO: Operating system context exists. 
RFCOSLIB: INFO: no filter information in sapccmsr.ini found 
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: Creating Monitoring Object "CPU_Virtualization_Host"
RFCOSLIB: INFO: Creating Monitoring Object "System_Info_Virtual_System"
RFCOSLIB: INFO: OS monitoring: Operating System Tree created
INFO: Loading static lib alloglib with trace level 0.
ALLOGLIB: INFO: ok, no configuration for Logfile Monitoring. No entry LogFile <file_name> in configuration file /usr/sap/SSM/DVEBMGS30/log/sapccm4x/sapccmsr.ini found
INFO: Loading static lib aljsflib with trace level 0.
ALJSFLIB: INFO: initialize Java Startup Framework monitoring
ALJSFLIB: INFO: Startup Framework Monitoring: Instance Tree created
INFO: Working directory is /usr/sap/SSM/DVEBMGS30/log/sapccm4x
INFO: Configuration file /usr/sap/SSM/DVEBMGS30/log/sapccm4x/sapccmsr.ini opened.
INFO: PlugIn manager initialized successfully.


[Thr 140737297700608]

[Thr 140737295599360]
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LONGRUN_TD started
INFO: Threads of CCMS Web Service Agent: method dispatcher SAP_CCMS_AGNT_LOCAL_TD started

[Thr 140737295599360]
Mon Oct 21 13:16:00 2024
INFO: Runtime status of ABAP Instance SSM ssm_SSM_30 active, started at Mon Oct 21 13:15:21 2024

Mon Oct 21 13:17:10 2024
RFCOSLIB: INFO: Operating system context exists. 
RFCOSLIB: INFO: Operating system context belongs to CCMS agent 
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC

Mon Oct 21 13:17:50 2024
INFO: Runtime status of Java Instance SSM ssm_SSM_30 shutdown

Mon Oct 21 13:18:01 2024
INFO: Runtime status of ABAP Instance SSM ssm_SSM_30 shutdown
INFO: Runtime status of Java Instance SSM ssm_SSM_30 shutdown

[Thr 140737302972160]
Mon Oct 21 13:18:05 2024
INFO: Re-Initialization of CCMS Agent
INFO: ...stop Method Dispatcher.
INFO: Waiting for 1st method dispatcher thread to exit...

[Thr 140737297700608]
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LONGRUN_TD exits

[Thr 140737295599360]
INFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LOCAL_TD exits

[Thr 140737302972160]
INFO: Waiting for 2nd method dispatcher thread to exit...
INFO: Cleanup for static lib rfcoslib.
INFO: Cleanup for static lib alloglib.
INFO: Cleanup for static lib aljsflib.
INFO: ... download Shared Memory content into file system.
INFO: ... Download successful. Disconnecting from CCMS Memory.

Mon Oct 21 13:18:08 2024
INFO: ... reconnect to CCMS Memory.

INFO: no Shared Memory, using process local memory of size 60000000

INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for ssm_SSM_30, process local memory, created with version CCMS version 20060508, 64 bit multithreaded, compiled at Jan 15 2013, kernel 7200_20020600_401, platform 390 (AMD/Intel x86_64 with Linux)]
segment status WARM_UP
segment started at Mon Oct 21 13:18:08 2024
segment version 20060508

INFO: updating shared memory runtime information of sapccm4x

INFO: Loading static lib rfcoslib with trace level 0.
RFCOSLIB: INFO: current trace level is 1 
RFCOSLIB: INFO: Semaphore Handling initialization successful.
RFCOSLIB: INFO: Trying to Register Objects 
RFCOSLIB: INFO: Operating system context exists. 
RFCOSLIB: INFO: no filter information in sapccmsr.ini found 
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: OS monitoring: Operating System Tree created
INFO: Loading static lib alloglib with trace level 0.
ALLOGLIB: INFO: ok, no configuration for Logfile Monitoring. No entry LogFile <file_name> in configuration file /usr/sap/SSM/DVEBMGS30/log/sapccm4x/sapccmsr.ini found
INFO: Loading static lib aljsflib with trace level 0.
ALJSFLIB: INFO: initialize Java Startup Framework monitoring
ERROR: Startup Framework Monitoring: Error-100 can not find [J2EE Sessions] under TID <SUMM>:SSM :Java Instance: ssm_SSM_30:5:1:391:-1
ALJSFLIB: INFO: Startup Framework Monitoring: Instance Tree created
INFO: Working directory is /usr/sap/SSM/DVEBMGS30/log/sapccm4x
INFO: Configuration file /usr/sap/SSM/DVEBMGS30/log/sapccm4x/sapccmsr.ini opened.
INFO: PlugIn manager initialized successfully.


[Thr 
[Thr 140737297700608]
140737295599360]
INFO: Threads of CCMS Web Service Agent: method dispatcher SAP_CCMS_AGNT_LOCAL_TD startedINFO: Threads of CCMS Agent: method dispatcher SAP_CCMS_AGNT_LONGRUN_TD started


[Thr 140737297700608]
Mon Oct 21 13:18:18 2024
INFO: Runtime status of ABAP Instance SSM ssm_SSM_30 shutdown
RFCOSLIB: INFO: Operating system context exists. 
RFCOSLIB: INFO: Operating system context belongs to CCMS agent

Mon Oct 21 13:19:18 2024
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC
RFCOSLIB: INFO: Creating Monitoring Object "General"
ERROR: OS monitoring: Error-253 Can not create Monitoring Object [General]. Different MO with same name exists within same Monitoring Context. MO has to be unique in MC

We tried to perform the operation from the note 1503112. but without success. What else can we do?

[mamartins]

Did you changed the hostname of the server?

There is some mistake on your side, because it appears that the SSM instance is a JAVA one and you can't access JAVA instances with the SAP GUI. Also, a CUA instance is only ABAP, not JAVA...

Most certainly, this is a SOLMAN system, and they have 2 instances, an ABAP and a JAVA.

[jbrzozowski]

we have 3 separate systems. one with java, one with SOLMAN and this one with CUA.

The main problem is that you can't log in through SAPGUI. 
Connection failed
Error: partner 'IP_ADDRESS:3230' not reached

and on server side its look like after startsap there is process listening on 3230 port, but after several seconds, process disappears, and nothing listening on port 3230.

maybe I'm looking in the wrong logs?

[mamartins]

You have 3 different instances sharing the same server host? If so, maybe there are some TCP port conflict or maybe lack of RAM...