Configuration Check Error in Managed System Configuration

[former_member185274]

Hi dear experts,

I come across a problem as the screenshot shows blew:

I check some relevant information, but no issues found:

1.

DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status

saphostexec running (pid = 7094)

sapstartsrv running (pid = 7097)

10:46:34 24.06.2014     LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp

saposcol running (pid = 7130)

DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile

SAPSYSTEMNAME = SAP

SAPSYSTEM = 99

service/porttypes = SAPHostControl SAPOscol SAPCCMS

DIR_LIBRARY = /usr/sap/hostctrl/exe

DIR_EXECUTABLE = /usr/sap/hostctrl/exe

DIR_PROFILE = /usr/sap/hostctrl/exe

DIR_GLOBAL = /usr/sap/hostctrl/exe

DIR_INSTANCE = /usr/sap/hostctrl/exe

DIR_HOME = /usr/sap/hostctrl/work

service/admin_users = daaadm

service/logfile_000 = /tmp/s

service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc

service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc

service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc

And the version of hostagent is up-to-date.

2.The URL

- http://<SMDhost>:1128/SAPOscol/?wsdl

- http://<SMDhost>:1128/SAPHostControl/?wsdl

can be accessed.

3.The step 3 in managed systems configuration is executed successfully.

4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.

5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.

Now I have no idea how to proceed, please give me some advice, thank you in advance.

Best Regards,

Pany Pan

[former_member185239 · Accepted solution]

Hi Pany

Kindly check the below two sapnote

1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a...

1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution...

Moreover , you need to check/verify/maintain the parameter in configtool

ThreadManager -> MaxThreadCount	Total number of Diagnostics Agents * 2 + 50	1250
ThreadManager -> InitialThreadCount	Total number of Diagnostics Agents * 1.5	900
ThreadManager -> MinThreadCount	Total number of Diagnostics Agents	600
ConnectionManipulator -> maxSoTimeOutConnections	Total number of Diagnostics Agents * 1.35	810
ConnectionManipulator -> MaxParallelUsers	Total number of Diagnostics Agents + 50	650

In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki 

guide check the section Required Solution Manager Java Stack Settings (Scalability)

I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,

minthreadcount , maxSoTimeOutConnections.

With Regards

Ashutosh Chaturvedi

[former_member185274 · Accepted solution]

Hi Ashutosh,

Thank you for your reply, I finally resolve this issue by update the hostagent, restart SMD in managed system side and change the parameter you mentioned above in solman side. There are only three or four SMDs in my landscape, I think the default value for the parameters is large enough, so I didn't try to enlarge the value yesterday. It's really weird. Anyway, thank you very much.

Best Regards,

Pany Pan

[former_member199290 · Accepted solution]

In my case SAP Host Agent on the managed system was down. Bringing the host agent up resolved the errors.No need to change the parameters as I also don't have a lot of agents connecting to Solman.

Thanks.

[v_veeramalla]

Provide the dumps , if any.

//Venkat

[former_member185274]

Hi Venkat,

But how can I find the dumps?

Thank you.

Pany