Error Setsockopt So Keep Alive Invalid Argument Solaris

HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris SSH Error messages User Name Remember Me? Password Solaris / OpenSolaris This forum is for the discussion of Solaris and OpenSolaris. General Sun, SunOS and Sparc related questions also go here. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 08-03-2006, 12:04 AM #1 UltraSoul Member Registered: Dec 2004 Location: Japan Distribution: REDHAT9.0, Mandrake10.1 Posts: 404 Rep: SSH Error messages I got mant same messags as follows, But ssh is in normal operation. The error messages really increases my /var/adm/messages size. Some idears? Thank you very much. Jul 8 03:10:49 sys52 sshd[1342]: [ID 800047 auth.error] error: setsockopt SO_KEEPALIVE: Invalid argument Jul 1 08:23:51 sys52 sshd[26345]: [ID 800047 auth.error] error: accept: Software caused connection abort Last edited by UltraSoul; 08-04-2006 at 12:12 AM. UltraSoul View Pub

sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi, I'm trying to SSH with portforwarding to the OmniOS VM (with two aggregated passthrough NICs) on ESXi, but I keep getting "sshd[695]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument" in messages. Normal SSH works fine. Anyone have any tips/advice? Thank you. Please see below for details. Client ssh command: "ssh -L 4200:localhost:4243 username at server.hostname" It seems to connect normal, but when my CrashPlan clients try to connect I get this in messages: "Jun 29 http://www.linuxquestions.org/questions/solaris-opensolaris-20/ssh-error-messages-470299/ 22:42:43 hostname sshd[695]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument Jun 29 22:45:35 hostname last message repeated 1 time Jun 29 22:52:50 hostname sshd[1081]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument" The CrashPlan service is running fine and listening on port 4242. "#ps aux |grep java root 566 0.0 4.1152228126744 ? S 01:55:21 0:25 /usr/bin/java -Dfi … " "#netstat -na http://lists.omniti.com/pipermail/omnios-discuss/2013-June/000989.html | grep LISTEN | grep 42 *.4242 *.* 0 0 65880 0 LISTEN ::ffff:127.0.0.1.4243 *.* 0 0 128000 0 LISTEN *.4242 *.* 0 0 65880 0 LISTEN" I have tried setting this in sshd_config, but did not work: "AllowTcpPortforwarding yes GatewayPorts yes" This is my sshd_config: # # Copyright (c) 2001, 2010, Oracle and/or its affiliates. All rights reserved. # # Configuration file for sshd(1m) (see also sshd_config(4)) # # Protocol versions supported # # The sshd shipped in this release of Solaris has support for major versions # 1 and 2. It is recommended due to security weaknesses in the v1 protocol # that sites run only v2 if possible. Support for v1 is provided to help sites # with existing ssh v1 clients/servers to transition. # Support for v1 may not be available in a future release of Solaris. # # To enable support for v1 an RSA1 key must be created with ssh-keygen(1). # RSA and DSA keys for protocol v2 are created by /etc/init.d/sshd if they # do not already exist, RSA1 keys for protocol v1 are

(Pacific Daylight Time) On Thu, 19 Sep 2002 address@hidden wrote: > Dan Peterson writes: > > > > Why doesn't either the CVS server process or the https://lists.nongnu.org/archive/html/info-cvs/2002-09/msg00231.html TCP connection timeout? > > Good question. The CVS server uses the https://www.experts-exchange.com/questions/21270122/Can-not-SSH-into-newly-built-server-Installed-SSH-with-pkgadd-it-does-not-work.html KEEPALIVE socket option, if > available, to detect broken connections. KEEPALIVE tells the system to > periodically ping the other side of an idle connection and break the > connection if it fails to get a response in a reasonable amount of time. > The fact that error setsockopt your connections are still in the ESTABLISHED state > implies that this isn't working on your system -- many systems take a > number of hours to detect a broken connection, but not 20 days. As of > CVS 1.11.1, CVS will syslog any errors it receives setting KEEPALIVE, so > check your syslog. Well, I do see error setsockopt so several errors (84 over a 3.5 month period) related to KEEPALIVE: ... error setting KEEPALIVE: Invalid argument But the interesting thing is, none of the current list of 15 procs older than 24 hours logged one of these KEEPALIVE message. At least I assume I should see the same process id in /var/adm/messages as the current "hung" process? What does "Invalid argument" in the context of setsockopt mean anyway? The Solaris man page for setsockopt doesn't even show that EINVAL is a valid error response. > If there aren't any errors, that implies that your system is accepting > the option but ignoring it, which is extremely unfriendly, to say the > least. You may want to check with some Solaris experts to see if > there's some kind of option to enable it. reply via email to [Prev in Thread] Current Thread [Next in Thread] Hung CVS server processes, Dan Peterson, 2002/09/19 Re: Hung CVS server processes, Larry Jones, 2002/09/19 Re: Hung CVS server processes, Dan Peterson<= Re: Hung CVS server processes, Lar

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Can not SSH into newly built server. Installed SSH with pkgadd it does not work Want to Advertise Here? Solved Can not SSH into newly built server. Installed SSH with pkgadd it does not work Posted on 2005-01-11 Unix OS 2 Verified Solutions 4 Comments 1,393 Views Last Modified: 2013-12-27 We have a server that was built by a "user". He forgot packages such as ssh and ipsec. I ftped in and installed : pkgadd -d . SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr SUNWsshu When I try to ssh in I get the error: Password: Connection to 47.42.84.98 closed by remote host. Connection to 47.42.84.98 closed. If I go to the messages file and do a cat messages | grep ssh: Jan 10 13:52:29 wncym3 sshd[375]: [ID 800047 auth.error] error: accept: Software caused connection abort Jan 10 17:08:52 wncym3 sshd[9170]: [ID 800047 auth.error] error: setsockopt SO_KEEPALIVE: Invalid argument When performing an nmap the port 22 shows up just fine What am I missing. 0 Question by:TIMFOX123 Facebook Twitter LinkedIn Google LVL 40 Best Solution byjlevie Were the OpenSSH packages that you installed specfically for this version of Solaris? Go to Solution 4 Comments LVL 40 Overall: Level 40 Unix OS 13 Message Accepted Solution by:jlevie2005-01-11 Were the OpenSSH packages that you installed specfically for this version of Solaris? 0 LVL 38 Overall: Level 38 Unix OS 13 Message Assisted Solution by:wesly_chen2005-01-11 Hi, Here is the previous question: http://www.experts-exchange.com/Operating_Systems/Solaris/Q_21268761.html > server sshd[process ID]: error: setsockopt SO_KEEPALIVE: Invalid argument In order to resolve this issue you need to set "KeepAlive no" in the /etc/ssh/sshd_config file. Regards, Wesly 0 LVL 40 Overall: Level 40 Unix OS 13 Message Expert Comment by:jlevie2005-01-11 Actually I think that error is an artifact of and is caused by the first error. 0 Message Author Co