Which version of SSH are you using?
If it's from HP, review the release notes of that SSH version (should be available at docs.hp.com). There might be a recommendation to install some patches.
The error message is related to a setsockopt() system call. "man 2 setsockopt" for more information.
The "Invalid argument" error, or EINVAL, is described in the man page as follows:
"The level or optlen value is not valid; or optval is the NULL address; or the protocol connection has been released."
The words "level", "optlen" and "optval" refer to the arguments of the setsockopt() system call.
Note the last possible cause of the EINVAL error: "...or the protocol connection has been released."
My wild guess:
This might be caused by a port scan, possibly using some "stealthy" method: sshd receives something that initially looks like a new connection, but when sshd gets to the point of running setsockopt(), the connection is already gone.
If it was me, I'd like to set up a network sniffer to pick up the first few packets of each connection incoming to the sshd port of your server.
Then find out if the beginning of each connection looks like a standard TCP three-way handshake or something different: it might be that the "client" always aborts the connection in the earliest possible phase. If anomalous connections are found, you might want to look where they're coming from.
MK
MK
