Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Outstanding Contributor.. Vince Laurent Outstanding Contributor..
Outstanding Contributor..
210 views

DP9: inet.log repeated errors

Jump to solution

(root@sapbck)# grep "Peer hostname" inet.log | uniq | wc -l

There are over 12k lines in my inetd.log with the stuff like following information:

Peer hostname check: request came from host s928-dbsapeq1.ssmhc.com (::ffff:165.104.129.172), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapep1.ssmhc.com (::ffff:165.104.141.119), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-apmgr1.ssmhc.com (::ffff:165.104.139.56), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapep1.ssmhc.com (::ffff:165.104.141.119), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapeq1.ssmhc.com (::ffff:165.104.129.172), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-apmgr1.ssmhc.com (::ffff:165.104.139.56), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapep1.ssmhc.com (::ffff:165.104.141.119), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapbp1.ssmhc.com (::ffff:165.104.129.103), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapep1.ssmhc.com (::ffff:165.104.141.119), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host w009-0405.ds.ad.ssmhc.com (::ffff:10.128.128.161), which is not host sapbck.ssmhc.com!
Peer hostname check: request came from host s928-dbsapep1.ssmhc.com (::ffff:165.104.141.119), which is not host sapbck.ssmhc.com!

What does it mean and how should I fix or should I even fix?

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: DP9: inet.log repeated errors

Jump to solution

To fix it see data Protector installation manual, chapter 6 under title: "Excessive logging to the inet.log file".

There you will find how to fix it.

Regards

Dionisio

2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: DP9: inet.log repeated errors

Jump to solution

To fix it see data Protector installation manual, chapter 6 under title: "Excessive logging to the inet.log file".

There you will find how to fix it.

Regards

Dionisio

Outstanding Contributor.. Vince Laurent Outstanding Contributor..
Outstanding Contributor..

Re: DP9: inet.log repeated errors

Jump to solution

@Dionisio Sciascia wrote:

To fix it see data Protector installation manual, chapter 6 under title: "Excessive logging to the inet.log file".

There you will find how to fix it.

Regards

Dionisio


Thanks!

Excessive logging to the inet.log file

If the clients are not secured and the Cell Manager is configured in the HPE Serviceguard environment or has multiple names or IP numbers, the inet.log file may contain many entries of the following type:
A request 0 came from host name.company.com which is not a Cell Manager of this client.
This happens because the client, which is not secured, recognizes only the primary hostname of the Cell Manager. Requests from any other clients are allowed, but logged to the inet.log file. When a client is secured, requests from the clients listed in the allow_hosts file are accepted, and are thus not logged. Requests from other clients are denied. Securing clients can be used as a workaround to prevent unnecessary entries in inet.log files. However, all possible client names for the Cell Manager should be listed in the allow_hosts file on each client. This enables access to the client also in case of a failover. If this workaround is for any reason not possible in your environment, you can secure the clients and specify * as an IP address range for the systems you want to allow access. This means that your clients will accept requests from all systems (any IP address) and will practically not be secured, but you will still resolve the excessive logging issue.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.