From phil@ticketmaster.com Thu Dec 1 14:03:18 2005 Received: from sun1rly4.tmcs.net (sun1rly4.tmcs.net [209.104.55.100]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jB1M3ABM028690 for ; Thu, 1 Dec 2005 14:03:15 -0800 (PST) Received: from metallica.office.tmcs ([172.28.61.111]) by sun1rly4.tmcs.net (8.12.10/8.12.9/200406301403) with ESMTP id jB1M38Zv006736 for ; Thu, 1 Dec 2005 14:03:08 -0800 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by metallica.office.tmcs (Postfix) with ESMTP id 62E1E100055 for ; Thu, 1 Dec 2005 14:03:07 -0800 (PST) Message-ID: <438F731A.3030404@ticketmaster.com> Date: Thu, 01 Dec 2005 14:03:06 -0800 From: Phil Dibowitz User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@conserver.com Subject: Re: conserver -> cyclade, ssh timeouts References: In-Reply-To: X-Enigmail-Version: 0.92.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB4AED7A8604C539435D40444" X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 22:03:19 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB4AED7A8604C539435D40444 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit nathan r. hruby wrote: > On Mon, 10 Oct 2005, Phil Dibowitz wrote: > > >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Hey folks, >> >>So I've brought conserver to my next company - or at least I'm trying to. ;) >> >>I'm having a problem where the ssh connection from conserver to the >>cyclades times out, and the ssh client sees it happen, and thus >>conserver sees it happen - but the cyclade never sees this happen, and >>thus the sock_sshd for that port lives on and the cyclade can never connect. >> >>I know this is more of a cyclades question and less of a conserver >>question - but I figure this is probably one of the best places to ask >>if anyone's run into this. >> > > > FWIW, cyclades has a mailing list for users at cyusers@cyclades.com. It's > a very low traffic list and their support folks and lower middle > management do monitor the list and take problem reports seriously. This > list is not easy to find on their website, which I think is part of the > reason it's low traffic :) Hmm. So I'm no longer convinced this is entirely a cyclades issue. But it kinda depends on whether I'm reading the conserver logs right. Conserver gets a console up: [Wed Nov 30 16:40:56 2005] conserver (6459): [swx3.sys.adm1] console up The ssh connection is somehow killed: [Wed Nov 30 18:41:26 2005] conserver (6459): [swx3.sys.adm1] exit(255) It then retries for an hour: [Wed Nov 30 18:41:26 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization [Wed Nov 30 18:41:35 2005] conserver (6459): [swx3.sys.adm1] exit(255) [Wed Nov 30 18:41:35 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization [Wed Nov 30 18:41:47 2005] conserver (6459): [swx3.sys.adm1] exit(255) [Wed Nov 30 18:41:47 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization [Wed Nov 30 18:42:00 2005] conserver (6459): [swx3.sys.adm1] exit(255) [Wed Nov 30 18:42:00 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization It then backs off for 30 seconds and brings it up successfully (does this "up" means it's back to tring again, or it was able to successfully bring the console up??): [Wed Nov 30 19:30:01 2005] conserver (6459): ERROR: [swx3.sys.adm1] initialization rate exceeded: forcing down [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] console up At which point it almost immediately dies again: [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] exit(255) [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization Sometimes it'll stay up for a few seconds or so: [Thu Dec 1 01:29:56 2005] conserver (6459): [swx3.sys.adm1] console up [Thu Dec 1 01:30:00 2005] conserver (6459): [swx3.sys.adm1] exit(255) [Thu Dec 1 01:30:00 2005] conserver (6459): [swx3.sys.adm1] automatic reinitialization I'm sending a report to cyclades as well - but I'd thought I'd run this by the other experts here. ;) -- Phil Dibowitz P: 310-360-2330 C: 213-923-5115 Unix Admin, Ticketmaster.com --------------enigB4AED7A8604C539435D40444 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDj3Ma9q0UmHR94IoRAqNmAJ4q1RT597BKdyoTYX4W/brAGdXauQCeIvdF KYscyjPUAhrzUo7Op7+XGJo= =+uyo -----END PGP SIGNATURE----- --------------enigB4AED7A8604C539435D40444-- From bryan@stansell.org Thu Dec 1 23:01:29 2005 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jB271Twl002038 for ; Thu, 1 Dec 2005 23:01:29 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.13.5/8.13.5/Submit) id jB271S3W002037 for users@conserver.com; Thu, 1 Dec 2005 23:01:28 -0800 (PST) Date: Thu, 1 Dec 2005 23:01:28 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: conserver -> cyclade, ssh timeouts Message-ID: <20051202070128.GY363@underdog.stansell.org> References: <438F731A.3030404@ticketmaster.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438F731A.3030404@ticketmaster.com> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.39 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 07:01:29 -0000 On Thu, Dec 01, 2005 at 02:03:06PM -0800, Phil Dibowitz wrote: > [Wed Nov 30 19:30:01 2005] conserver (6459): ERROR: [swx3.sys.adm1] > initialization rate exceeded: forcing down > [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] automatic > reinitialization > [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] console up > At which point it almost immediately dies again: > > [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] exit(255) > [Wed Nov 30 19:30:56 2005] conserver (6459): [swx3.sys.adm1] automatic > reinitialization here's the deal with these messages. if a console is forced down (like above), then when it succeeds in coming back up the 'console up' message is generated. when it goes down, it retries, and all is well, no 'console up' is displayed (not sure why, but there was reasoning at the time). that's the real difference between all your logs. in general, conserver is forking off the command, seeing it exit with a -1 (255 since it's printing as unsigned) and retrying. they seem to stay running about 4 seconds, before they exit. since this is a command and conserver has no idea if the command is succeeding or not (as long as it forks of it assumes so), it marks it as up (for about 4 seconds) and catches it dying and retries. looks like it was respawning a bit quicker above, so it hit the reinitialization rate...but that doesn't really deviate from the general behavior. it doesn't look like a conserver issue to me (it's doing what i think it should, at least). it sounds like the ssh connection isn't being dropped on the cyclades side (since it probably didn't get a FIN packet, for whatever reason?) and keeping the port in use. conserver can't tell what's really going on since the command could be doing anything. i'd suggest having what conserver forks off do some logging somewhere to see if ssh is getting a connection refused or failing to authenticate or what...might help diagnose the issue. the fact the fork, ssh, etc is taking so long makes me think it might not be just a simple "connection refused". Bryan From stoffj@taec.toshiba.com Mon Dec 5 08:38:54 2005 Received: from mailhost.taec.toshiba.com (mailhost.taec.com [209.243.128.33]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jB5Gcleu003905 for ; Mon, 5 Dec 2005 08:38:52 -0800 (PST) Received: from sekrit.taec.toshiba.com (IDENT:U2FsdGVkX19nhGQscldlGIVazmsKwuz+w+JwjUE1sQ8@sekrit.taec.toshiba.com [209.243.166.44]) by mailhost.taec.toshiba.com (8.12.7/8.12.7) with ESMTP id jB5Gcd27002420; Mon, 5 Dec 2005 08:38:39 -0800 (PST) Received: (from stoffj@localhost) by sekrit.taec.toshiba.com (8.13.1/8.13.1/Submit) id jB5GccNX006821; Mon, 5 Dec 2005 11:38:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17300.27918.269119.915837@sekrit.taec.toshiba.com> Date: Mon, 5 Dec 2005 11:38:38 -0500 From: "John Stoffel" To: "David K. Z. Harris" Subject: Re: Conserver/Consoles BoF at LISA 05? In-Reply-To: <20051201043810.GA17135@jeffk.com> References: <20051201043810.GA17135@jeffk.com> X-Mailer: VM 7.19 under Emacs 21.4.1 X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Cc: users@conserver.com, Zonker at BigBand X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 16:38:55 -0000 >>>>> "David" == David K Z Harris writes: David> I know that the idea has been suggested before, but I'll stir David> the bucket again here... I'm at LISA this year, and I'd be happy to meet up with other Conserver users. Getting some vendor support for a single network control channel to manage/control all ports on a single device would be great. I'm not sure I'll be at the Vendor BOFs, I don'[t have any of their gear. But I'd be happy to goto a Digi or Avocent BOF, though I really hate the Avocent DSview KVM stuff. Just having a Conserver & KVM box would be good. I mean BOF. Ugh... John From mdaigle@yorku.ca Tue Dec 6 11:41:51 2005 Received: from tweety.ccs.yorku.ca (tweety.ccs.yorku.ca [130.63.236.216]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jB6JfcRY021349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 6 Dec 2005 11:41:48 -0800 (PST) Received: from [127.0.0.1] (ulysses.ops.yorku.ca [130.63.237.152]) by tweety.ccs.yorku.ca (8.13.4/8.13.4/Debian-3) with ESMTP id jB6JfWrr027408 for ; Tue, 6 Dec 2005 14:41:34 -0500 Message-ID: <4395E96A.4070803@yorku.ca> Date: Tue, 06 Dec 2005 14:41:30 -0500 From: Mike Daigle User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en, en-us MIME-Version: 1.0 To: users@conserver.com Subject: Perle CS9000 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:41:52 -0000 HI Gang: I posted a few weeks ago asking about comments on the Raritan products. Got enough bad news to steer away from that stuff. Now I am looking at the PERLE CS9000 console servers based on just the attractive price tag. Looks like it should serve as a basic console server and I can let conserver do all the logging, port mapping and stuff that it does well. Anybody out there have good or bad experience with these devices? -- Mike Daigle \ | | Network Operations Project Supervisor \| /\ |~ |/ Computing and Network Services | \/ | |\ Room 011 Steacie Science Library UNIVERSITY Email: mdaigle@yorku.ca 4700 Keele St. Toronto Phone: 736-2100 ext.22730 Ontario, Canada M3J 1P3 For thousands of years mankind lived just like the animals; Then something happened that unleashed the power of his imagination; He learned to talk. -- Pink Floyd From lorne_vaught@symantec.com Tue Dec 6 14:03:45 2005 Received: from silver.veritas.com (silver.veritas.com [143.127.12.111]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jB6M3bO9022161 for ; Tue, 6 Dec 2005 14:03:42 -0800 (PST) Received: from unknown (HELO dub1xchecnpin01.enterprise.veritas.com) ([166.98.48.51]) by silver.veritas.com with ESMTP; 06 Dec 2005 14:03:33 -0800 Received: from SVLXCHCON2.enterprise.veritas.com ([10.137.18.172]) by dub1xchecnpin01.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Dec 2005 22:03:31 +0000 Received: from megami.veritas.com ([10.137.16.7]) by SVLXCHCON2.enterprise.veritas.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 6 Dec 2005 14:03:28 -0800 Received: (1735 bytes) by megami.veritas.com via sendmail with P:smtp/R:smart_host/T:smtp (sender: ) id for ; Tue, 6 Dec 2005 14:03:28 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #15 built 2001-Aug-30) Message-Id: To: Mike Daigle Subject: Re: Perle CS9000 In-reply-to: Your message of "Tue, 06 Dec 2005 14:41:30 EST." <4395E96A.4070803@yorku.ca> Date: Tue, 06 Dec 2005 14:03:28 -0800 From: lorne vaught X-OriginalArrivalTime: 06 Dec 2005 22:03:28.0910 (UTC) FILETIME=[E391D2E0:01C5FAB0] X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Cc: users@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 22:03:45 -0000 >HI Gang: >I posted a few weeks ago asking about comments on the Raritan products. >Got enough bad news to steer away from that stuff. > >Now I am looking at the PERLE CS9000 console servers based on just the >attractive price tag. Looks like it should serve as a basic console >server and I can let conserver do all the logging, port mapping and >stuff that it does well. > >Anybody out there have good or bad experience with these devices? I've had good experience with Perle CS9024's over the last 3-4 years or so. I currently have 15 CS9024's and 2 CS9032's running conserver7.2.7. I encountered a bug in Perle's FW that had issues with conserver8.x.x, but Bryan Stansell worked with Perle to correct the problem and I think we're in good shape now. Hopefully, in the next 2 weeks, I'll migrate our config over to conserver8.1.12. We converted over to perle's from digi's and microannex's that I inherited from a previoius administrator. I've had less HW trouble with 17 perles than I had with 2 digi's and 4 microannex's. Bryan reported that Perle Support/Engineering was easy to do business with, and I have to agree. They have a "limited" lifetime warranty, and I've used it a couple of times. If you send them a failed unit, they will fix/replace it for as long as you own it. Lorne From Mark.Wedel@Sun.Com Thu Dec 22 14:37:54 2005 Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jBMMblHi024759 for ; Thu, 22 Dec 2005 14:37:52 -0800 (PST) Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id jBMMbiD7002272 for ; Thu, 22 Dec 2005 15:37:44 -0700 (MST) Received: from domus.sfbay.sun.com (domus.SFBay.Sun.COM [10.6.64.11]) by sfbaymail2sca.sfbay.sun.com (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id jBMMbi2f025826 for ; Thu, 22 Dec 2005 14:37:44 -0800 (PST) Received: from [129.146.108.170] (sleipner.SFBay.Sun.COM [129.146.108.170]) by domus.sfbay.sun.com (Trusted Solaris (8.11.7)/8.11.6) with ESMTP id jBMMbf507272 for ; Thu, 22 Dec 2005 14:37:41 -0800 (PST) Message-ID: <43AB2B03.2080608@Sun.Com> Date: Thu, 22 Dec 2005 14:38:59 -0800 From: Mark Wedel User-Agent: Mail/News 1.4 (X11/20050928) MIME-Version: 1.0 To: users@conserver.com Subject: ssh/initcmd problem/bug? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 22:37:55 -0000 Running conserver 8.12 on solaris 9/sparc. I have a console entry set up like: console somehost { break 2; type exec; initcmd "/export/connect-script"; exec ssh -l admin somehost; } This works all fine when I add the console and send the signal to conserver - the ssh command is run, and initcmd does its thing. This also works if conserver automatically re-runs this, for example, if a user logged out/exited the ssh session. The problem is that if a user uses the (re)open option (^Eco) - I'll see the output from the ssh connection, but no input gets passed along to ssh - this basically makes it such that the console is basically useless. If I go and remove the entry from the config file, signal conserver, then re-add it, all is well again. But this isn't a very convenient solution. I'd think this is a bug someplace in the code given that the other operations work expectedly. I don't have this problem that use the built in connection interface (host/port) with initcmd - only those using ssh (that is the only exec command I am using right now). From andyh@hall.gl Mon Dec 26 17:23:47 2005 Received: from mail.hall.wireless.pipex.net (69-74-19-212-un.wireless.as15758.net [212.19.74.69]) by underdog.stansell.org (8.13.5/8.13.5) with ESMTP id jBR1NcMM001191 for ; Mon, 26 Dec 2005 17:23:44 -0800 (PST) Received: by mail.hall.wireless.pipex.net (Postfix, from userid 1004) id 0BF18261849; Tue, 27 Dec 2005 01:23:36 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on qaqortoq.hall.gl X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.1.0 Received: from nt1.hall.gl (nt1.hall.gl [10.0.0.1]) by mail.hall.wireless.pipex.net (Postfix) with SMTP id 3E0A126183A for ; Tue, 27 Dec 2005 01:23:30 +0000 (GMT) Received: FROM bfs.hall.gl BY nt1.hall.gl ; Tue Dec 27 01:23:29 2005 0000 Received: from ANDYH5150 (10.0.0.91) by bfs.hall.gl (Worldmail 1.3.167) for users@conserver.com; 27 Dec 2005 01:23:29 +0000 From: "Andy Hall" To: Subject: Problem with SSH console Date: Tue, 27 Dec 2005 01:23:44 -0000 Message-ID: <00e201c60a84$2e51ee40$5b00000a@hall.gl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E3_01C60A84.2E51EE40" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Thread-Index: AcYKhC2MzywerJSoQQulSv3jSWW5wQ== X-Spam-Score: -4.285 () BAYES_00,HTML_60_70,HTML_MESSAGE X-Scanned-By: MIMEDefang 2.39 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.6 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 01:23:47 -0000 This is a multi-part message in MIME format... ------=_NextPart_000_00E3_01C60A84.2E51EE40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Greetings. I have just been installing Conserver 8.1.12 on a Linux host in order to use a mix of fitted serial ports and outbound connections to certain hosts. Most of this is working as expected, but I am having difficulty using SSH. Basically, conserver seems to be cycling with repeated retries of the SSH client. I have tested the SSH client standalone and it works fine. e.g. # ssh -v OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f Usage: ssh [options] host [command] Options: -l user Log in using this user name. # ssh -landyh 10.0.0.5 Password: Last login: Tue Dec 27 00:24:30 2005 from 10.0.0.3 If I run ps -ax I can see the execution attempts of the SSH client, but these fail and a new one is spawned. >From the log [Tue Dec 27 01:18:01 2005] conserver (19791): [myhost] exit(255) [Tue Dec 27 01:18:01 2005] conserver (19791): [myhost] automatic reinitialization [Tue Dec 27 01:18:02 2005] conserver (19791): [myhost] exit(255) [Tue Dec 27 01:18:02 2005] conserver (19791): [myhost] automatic reinitialization Here is an extract from the conserver.cf file console myhost { type exec; exec /usr/bin/ssh -lsshuser 10.0.0.5; } console catsw { type exec; exec telnet 10.0.0.8; } I imagine that this is not directly a conserver problem (or is it?). Presumably the 255 is a return code from the SSH client? I have tried the ssh command with and without the full pathname on the front and with and without -t as an option. Any ideas? thanks /andy ------=_NextPart_000_00E3_01C60A84.2E51EE40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline     Greetings.   I have=20 just been installing Conserver 8.1.12 on a Linux host in order to use a mix= of=20 fitted serial ports and outbound connections to certain hosts.  &= nbsp;=20 Most of this is working as expected, but I am having difficulty using=20 SSH.   Basically, conserver seems to be cycling with repeated ret= ries=20 of the SSH client.   I have=20 tested the SSH client standalone and it works fine.  =20 e.g.   # ssh=20 -v
OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
Usage: = ssh=20 [options] host [command]
Options:
  -l user   &nb= sp;=20 Log in using this user name.
<snip>     # ssh=20 -landyh 10.0.0.5
Password:
Last login: Tue Dec 27 00:24:30 2005 from= =20 10.0.0.3 <snip>     If I run ps -ax I=20 can see the execution attempts of the SSH client, but these fail and a new = one=20 is spawned.    From the=20 log     [Tue Dec 27 01:18:01=20 2005] conserver (19791): [myhost] exit(255)
[Tue Dec 27 01:18:01 2005]= =20 conserver (19791): [myhost] automatic reinitialization
[Tue Dec 27 01:18= :02=20 2005] conserver (19791): [myhost] exit(255)
[Tue Dec 27 01:18:02 2005]= =20 conserver (19791): [myhost] automatic reinitialization
  Here is=20 an extract from the conserver.cf file     console myhost=20 {            &n= bsp;            = ;            &n= bsp;            = ;        =20
        type=20 exec;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;        =20
        exec /usr/bin/ssh  -lss= huser=20 10.0.0.5;           =         =20
}           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;     =20
            = ;            &n= bsp;            = ;            &n= bsp;            = ;      =20
console catsw=20 {            &n= bsp;            = ;            &n= bsp;            = ;   =20
        type=20 exec;           &nbs= p;            &= nbsp;           &nbs= p;           =20
        exec telnet=20 10.0.0.8;           =             &nb= sp;            =   
       }=20     I imagine=20 that this is not directly a conserver problem (or is it?).  =20 Presumably the 255 is a return code from the SSH client?   I have=20 tried the ssh command with and without the full pathname on the front and w= ith=20 and without -t as an option.     Any=20 ideas?     thanks       /andy               ------=_NextPart_000_00E3_01C60A84.2E51EE40--