cancel
Showing results for 
Search instead for 
Did you mean: 

Weird error during Managed system configuration

symon_braunbaer
Participant
0 Kudos

Dear Experts,

I am facing those strange errors during step 8 of the managed system's configuration:

Could you please kindly advise on how to solve those without opening an OSS message... Many thanks in advance!!

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Symon,

You need to follow below recommendations.

Regards,

divyanshu_srivastava3
Active Contributor
0 Kudos

Also, for missing fqdn, please refer

1786051 - Configuration check when adding managed system returns "No FQDN found in Host"

symon_braunbaer
Participant
0 Kudos

Hello to all of you and MANY thanks for providing so many correct answers!

The tables with the recommendations have fixed the problem, now I just have a yellow warning

about No FQDN found in Host... . I went quickly through Note 1786051 and the other notes and references that it points to. But in the end, it is not completely clear to me what has to be done.

I have tried to edit the profile of this Java system and I have added the following line:

SAPLOCALHOSTFULL = $(SAPLOCALHOST).<ourdomain.com>

But this caused much more errors:

and I realized that the warnings are still there. Perhaps I would need to restart the managed system,

but it is production and it can't be restarted that easily. Also, I need to do this for about 15 more

systems and if I would need to restart them all, I'd get mad...

Furthermore, maybe this can be addressed via the /etc/hosts. The definition for the this system

looks like this:

> cat /etc/hosts

#

# Internet host table

#

::1     localhost

127.0.0.1       localhost

172.18.63.198   <our_saphost> loghost

I will try to speak with our Solaris admins, whether it's possible to have FQDN in /etc/hosts. Kindly let me know if this would solve the warning.

UPDATE: The /etc/hosts file has been updated with an alias to the FQDN.

Furthermore, I have updated the instance profile, as per the attachment in SAP note 1611483 - Solution Manager 7.1 - Outside Discovery Common Error Messages:

SAPFQDN = wdf.sap.corp
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)

The warning is still persisting:

<SID>~JAVA': No FQDN found in Host: <our_saphost>

Answers (2)

Answers (2)

former_member185239
Active Contributor
0 Kudos

Hi Symon,

Also do check the below thread

With Regards

Ashutosh Chaturvedi

former_member185239
Active Contributor
0 Kudos

Hi Symon,

You need to maintain the below parameters in configtool of solman system in dispatcher threadmanager and Connection manager as per your system and diagnostic agent.

Also do follow the sapnote 1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"

Max Heap Size in MB (JVM Parameter -Xmx)

Total number of Diagnostics Agents * 0.5 (Minimum 128MB)300 MB
ThreadManager -> MaxThreadCountTotal number of Diagnostics Agents * 2 + 501250
ThreadManager -> InitialThreadCountTotal number of Diagnostics Agents * 1.5900
ThreadManager -> MinThreadCountTotal number of Diagnostics Agents600

ConnectionManipulator -> maxSoTimeOutConnections

Total number of Diagnostics Agents * 1.35810
ConnectionManipulator -> MaxParallelUsersTotal number of Diagnostics Agents + 50

650

With Regards

Ashutosh Chaturvedi