on 11-24-2014 1:32 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 -> 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 |
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.