Technical Monitoring - Message Server displayed STOPPED

[Private_Member_19084]

Hi experts,

in our Technical Monitoring I have one managed system, on which the message server is displayed as "stopped".

But the MS is definitly running.

The destinations in LMDB are ok. Also I did already remove completly the monitoring and assigned the templates again.
Also DAA and hostctrl was restarted.

Any ideas?

Thank you

[divyanshu_srivastava3 · Accepted solution]

What do you see in logs ?

Can you share the screenshot and system type ?

[Private_Member_19084 · Accepted solution]

Which logs can I check?

DAA?

[divyanshu_srivastava3 · Accepted solution]

Yes, the agent logs.. also in LMDB can you see message server node of this system ?

[Private_Member_19084 · Accepted solution]

I will check the log.

Yes LMDB seems to be ok

[Private_Member_19084 · Accepted solution]

Which log is it exactly?
In workcenter the errors are empty.

[divyanshu_srivastava3 · Accepted solution]

I would say, you check 2 places.

One is the log directory of your DAA agent and another is CCMSPING(if used)

Regards,

[divyanshu_srivastava3 · Accepted solution]

Manually restart sapstartsrv for your host on which your MS is running.

Regards,

[Private_Member_19084 · Accepted solution]

This is also what I was already thinking...
That this process is not running correct

How can I restart the process on Linux?
And it is not required to stop the SID for this or?

[divyanshu_srivastava3 · Accepted solution]

"sapcontrol -nr $$ -function StopService"

"sapcontrol -nr $$ -function StartService"

This is what you can use to start sapstartsrv.

[Private_Member_19084 · Accepted solution]

thx, but stop of SID is not required, right?

[divyanshu_srivastava3 · Accepted solution]

better, you take a full restart.

However, you can restart service.

[Private_Member_19084 · Accepted solution]

thx for help...I made the restart, maybe it takes a while.

If not enough I will also restart the complete sap system.

[divyanshu_srivastava3 · Accepted solution]

Thanks for the update.

I would suggest you restart the complete SAP system including the agents.

Once this is done, make sure no old processes of startsrv are running.

Even in profiles, you can adjust service/protectedwebmethods parameters according to SAP Note 927637 - Web service authentication in sapstartsrv as of Release 7.00

Once all done, execute cleanipc for all instances and start SAP and DAA agent.

Regards,

[Private_Member_19084 · Accepted solution]

I've done a full restart of SID and also DAA.

It also seems not to be a authority problem.

I tried the following now, I did change the ASCS port number in LMDB to a wrong one, and the check still did display "STOPPED".

So for me it seems as something is wrong with the check.

KR

[divyanshu_srivastava3 · Accepted solution]

Hi Christian,

Few more things that we can check.

What is your managed system OS ?

Is it AIX ? - if yes, the mount /proc file system and see if that work.

Use command "sapcontrol -nr <sysnr> -function GetProcessList" to get the status of message server.

Other thing is - have a look at these two notes and try to match you system contents.

1853096 - Availability Metric: ABAP Message Server Status displays "No

process found for: msg_server(.*)"

1916237 - ABAP Central Service not available alert in Technical Monitoring

Do this much and share the results.

Regards,

[Private_Member_19084 · Accepted solution]

I checked both notes.

The first 1 I've already found - not relevant as it is the correct template.

Second one, also not relevant as the system is correctly in SLD.

Also if I re-sync the LMDB I get the corre entries for message server and central instance.

Output of your command:

msg_server, MessageServer, GREEN, Running, 2014....

enserver, EnqueueServer, GREEN, Running, 2014...

For for me it look ok, or?

[divyanshu_srivastava3 · Accepted solution]

That is OK.. means the srv service is generating the output and alias for msg server is correct.

[Private_Member_19084 · Accepted solution]

sooo....what next lol ?

[srinivasan_vinayagam]

Hi Christian,

Check LMDB related background jobs are running correctly.

[former_member185326]

Hello Christian,

I have faced similar problem. Issue is with the template metrics. Open the template you have assigned to this system and check for the message server process string. By default it is "msg_server*" given in the template. So, MAI looks for process with similar name. But in the system, message server process will be like this "ms.sap<SID>".

Hence, you will have to change the metric and give process name as "ms.sap*" or "ms.*" for the system to look out for the correct process.

Hope it helps.

Regards,

Shahid Ahmed

[Private_Member_19084]

I've already checked.

Naming seems to be ok

[former_member185326]

Can you please share screen capture of your template configuration and also the issue/ alert you are facing?

Regards,

Shahid

[Private_Member_19084]

Thats the thing:

[former_member185326]

As per screen shot of your template config, it is looking for process "msg_server*" which is not the case. Please change process name to "ms.*" and apply the template.

To cross check, you can search for "msg_server" process in your system at OS level using below command if you are on Unix platform:

ps -ef | grep msg_server

If you have stand alone central services instance, you'll find the process. If not, you'll find the process with "ms.sap<SID>". Hence, you'll have to change the template.

Let us know if it resolves.

Regards,

Shahid

[Private_Member_19084]

I can follow you.

Because this is the template of the ABAP System and not the template of the Central instance.

BUT!

I also have a homogenous system, which is using the same check and there it is working.

The template of this system contains the same check but also on this system msg_server is not running and I get an "Running" status.

So it is a bit confusing...

[Private_Member_19084]

Now I checked the template of the central instance (default template) and also there is the msg_server* checked....

And this is the newest CIM.

[Private_Member_19084]

so I tried ms.* in template.

Same result - stopped

[former_member185326]

This is strange issue... Would recommend opening a ticket with SAP Support.

Pls share solution when you get to fix it.,so it will be helpful for everyone.

Regards,

Shahid

[Former Member]

Hi Christian,

Could you able to fix this ?  I am facing the same issue. It would be very helpful if you could share the solution.

Thanks,

Phani.

[Private_Member_19084]

Hello Phani,

not really.

but it did get worse

Now a lot of them did switch to grey.

Kind regards

[hemanth2]

Hi Christian ,

Hope you are doing good.

Just a point here. Please refrain from just a restart of the nods or SCS individually. For consistency reasons, trigger a complete cluster restart.       

Thank you!

  ____________

  Kind Regards,

  Hemanth

  SAP AGS

[Former Member]

Hi Christian,

Check in metric trouble shooting in workcenter and failure extractors in extractors administration.Provide us error log if yu found any in above checks.

SOLMAN_WORKCENTER-->Technical monitoring -->select managed ssystem
-->in right handside place cursor on message server-->click on metric trouble shooting

Thanks,

Prakash

[Private_Member_19084]

Thx for help.
But there is no troubleshooting, because the metric thinks it is ok.

And the msg is really stopped.

So I just have reconfigure and documentation.