From cfowler@outpostsentinel.com Sun Dec 1 20:03:26 2002 Received: from cfowler.outpostsentinel.com (dsl-64-129-133-253.telocity.com [64.129.133.253]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id gB243PpI004667 for ; Sun, 1 Dec 2002 20:03:26 -0800 (PST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id gB2448r12619 for ; Sun, 1 Dec 2002 23:04:09 -0500 Subject: Re: Q: May conserver log to syslog? From: cfowler To: users@conserver.com In-Reply-To: <20021130180945.GB12759@underdog.stansell.org> References: <20021130180945.GB12759@underdog.stansell.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 01 Dec 2002 23:04:08 -0500 Message-Id: <1038801849.12527.11.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I hacked something similar into my version. Plus the buffers are available via SSL and a web browser connection. 2nd there is no easy way to destroy our log files. Yet another addition. We store our data in Kernel memory. Not files in /var/log or anywhere else. This also required modifications to Replay(). The answer is that with enough time you can easily add this feature. I'm not sure I agree that Syslog is a good spot. It could get busy in that file if you get a lot of output. But I would suggest that you use a line read method and place the console output in there by line. Now when it comes to general conserver messages, I log them to syslog. I have a mechanism that any daemon output on STDOUT or STDERR magically finds it's way into SYSLOG. This is with no modifications to any of the code itself. We had to add this for other daemons as well. On Sat, 2002-11-30 at 13:09, Bryan Stansell wrote: > On Fri, Nov 29, 2002 at 10:20:17AM +0100, Kjell Andresen wrote: > > On Thu, 28 Nov 2002, Kjell Andresen wrote: > > > > > http://www.conserver.com/FAQ didn't say anything about logging to > > > or via syslog. > > > I think it might be a good idea to maintain a second copy at some > > > loghost in order to be able to now what's been done if or when attacked. > > > > No answer to this one yet. > > nope, no current way of doing that within conserver. i suppose you > could hack something together by running conserver and piping the > output to a tool that would both log the data locally and send it > remotely (i'm think of something like a remote 'tee' command). but, i > don't have anything like that. the syslog idea is already in the TODO > file as a reminder that it would be useful...can't say when it would be > added, though. > > Bryan > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From kjell@beta.uio.no Thu Dec 5 01:51:56 2002 Received: from pat.uio.no (IDENT:7411@pat.uio.no [129.240.130.16]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id gB59ptpI024176 for ; Thu, 5 Dec 2002 01:51:56 -0800 (PST) Received: from beta.uio.no ([129.240.186.52]) by pat.uio.no with esmtp (Exim 2.12 #7) id 18Jsfe-00048z-00; Thu, 5 Dec 2002 10:51:50 +0100 Received: from kjell (helo=localhost) by beta.uio.no with local-esmtp (Exim 2.12 #1) id 18Jsfd-0000df-00; Thu, 5 Dec 2002 10:51:49 +0100 Date: Thu, 5 Dec 2002 10:51:49 +0100 (MET) From: Kjell Andresen To: users@conserver.com Subject: Swap Digi C/CON-16 rack[-aix] rj45? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Hello! I've inherited two unused 220-230V: Digi C/CON-16 RACK-AIX rj45 P/N: (1P) 50000598-02 I want to exchange these with a couple: Digi C/CON-16 RACK rj45 P/N: (1P) 50000598-01 or P/N: (1P) 50000598-03 If you have any piece of advice according compatible consentrators maybe with more serial ports I'm most grateful! Regards, Kjell Andresen Systems administrator, University of Oslo, Norway Center for Information Technology Services and Department of Geophysics From Ed.Brown@fmr.com Mon Dec 9 17:05:57 2002 Received: from maillnx-us312.fmr.com (maillnx-us312.fmr.com [192.223.178.27]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id gBA15upI010278 for ; Mon, 9 Dec 2002 17:05:56 -0800 (PST) Received: from virmro110nts.fmr.com (virmro110nts.fmr.com [172.26.5.98]) by maillnx-us312.fmr.com (Switch-2.2.4/Switch-2.2.4) with SMTP id gBA15sw18859 for ; Mon, 9 Dec 2002 20:05:54 -0500 Received: by msgmmk102nts.fmr.com with Internet Mail Service (5.5.2654.89) id ; Mon, 9 Dec 2002 20:05:54 -0500 Message-ID: <9AE9901EE93CA44187ECEA9E1A774D552EF45B@MSGMROCLA2WIN.DMN1.FMR.COM> From: "Brown, Ed" To: "'users@conserver.com'" Subject: more on reinitialization Date: Mon, 9 Dec 2002 20:05:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) Content-Type: text/plain; charset="iso-8859-1" Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I am currently testing conserver on a SUN E220 with a Lantronix scs4805 using openssh v3. If I start up 4 connections at a time, all 48 sessions connect without a problem, resulting in 14 conserver processes. However, when I attempt to bring up all 48 at once, the system is hammered for four-plus minutes while conserver reinitializes the connections, generating 13,000 plus messages into the conserver log file such as these: conserver (4609): port38: exit(255) [Mon Dec 9 17:48:54 2002] conserver (4609): port38: automatic reinitialization [Mon Dec 9 17:48:54 2002] conserver (4540): port2: exit(255) [Mon Dec 9 17:48:54 2002] conserver (4540): port2: automatic reinitialization [Mon Dec 9 17:48:54 2002] conserver (4589): port17: exit(255) [Mon Dec 9 17:48:54 2002] conserver (4589): port17: automatic reinitialization [Mon Dec 9 17:48:54 2002] conserver (4609): port38: exit(255) [Mon Dec 9 17:48:54 2002] conserver (4609): port38: automatic reinitialization [Mon Dec 9 17:48:54 2002] After four minutes, conserver calms down and all 48 connections are valid. But obviously I'd like to bring all 48 up quietly and efficiently. So I'd certainly appreciate help in resolving this. Here are some typical .cf entries port45:|/usr/bin/ssh -l -t "direct 45" ::/var/log/console/port45.log:1hab: port46:|/usr/bin/ssh -l -t "direct 46" ::/var/log/console/port46.log:1hab: port47:|/usr/bin/ssh -l -t "direct 47" ::/var/log/console/port47.log:1hab: port48:|/usr/bin/ssh -l -t "direct 48" ::/var/log/console/port48.log:1hab: From bryan@stansell.org Mon Dec 9 17:24:15 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id gBA1OFpI011529 for ; Mon, 9 Dec 2002 17:24:15 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id gBA1OFXw011528 for users@conserver.com; Mon, 9 Dec 2002 17:24:15 -0800 (PST) Date: Mon, 9 Dec 2002 17:24:15 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: more on reinitialization Message-ID: <20021210012415.GA10315@underdog.stansell.org> References: <9AE9901EE93CA44187ECEA9E1A774D552EF45B@MSGMROCLA2WIN.DMN1.FMR.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9AE9901EE93CA44187ECEA9E1A774D552EF45B@MSGMROCLA2WIN.DMN1.FMR.COM> User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: yowsers. well, i have a suggestion and a question. first the question. are there any indications of why the ssh process exits with a 255 in the log files (like /var/log/port38.log)? that might help explain exactly why things are going wild. my suggestion is this. there is a usleep(100000) in conserver/consent.c:757. you could try copying that to line 873 as well (just before the VirtDev() call). my theory (which perhaps the logfile could confirm) is that the lantronix can't handle many socket connections (ssh or not) at once. the code should probably have the delay anyway, as most program being executed are going to create socket connections. the usleep() was in there originally to handle older cisco equipment that couldn't take almost-simultaneous socket connections (an ultra2 overpowered it) - and i'm sure other equipment have similar issues - probably even semi-recent equipment. anyway, that's my theory and a possible work-around. if 1/10 of a second isn't enough, crank it up a little. let me know if i was at all on track and if the usleep() helps, ok? Bryan On Mon, Dec 09, 2002 at 08:05:48PM -0500, Brown, Ed wrote: > I am currently testing conserver on a SUN E220 with a Lantronix scs4805 > using openssh v3. If I start up 4 connections at a time, all 48 sessions > connect without a problem, resulting in 14 conserver processes. However, > when I attempt to bring up all 48 at once, the system is hammered for > four-plus minutes while conserver reinitializes the connections, generating > 13,000 plus messages into the conserver log file such as these: > > conserver (4609): port38: exit(255) [Mon Dec 9 17:48:54 2002] > conserver (4609): port38: automatic reinitialization [Mon Dec 9 17:48:54 > 2002] > conserver (4540): port2: exit(255) [Mon Dec 9 17:48:54 2002] > conserver (4540): port2: automatic reinitialization [Mon Dec 9 17:48:54 > 2002] ... > After four minutes, conserver calms down and all 48 connections are valid. > But obviously I'd like to bring all 48 up quietly and efficiently. So I'd > certainly appreciate help in resolving this. Here are some typical .cf > entries From skolupae@sonic.net Thu Dec 12 11:30:18 2002 Received: from a.smtp-out.sonic.net (a.smtp-out.sonic.net [208.201.224.38]) by underdog.stansell.org (8.12.6/8.12.6) with SMTP id gBCJUIpI009273 for ; Thu, 12 Dec 2002 11:30:18 -0800 (PST) Received: (qmail 10377 invoked from network); 12 Dec 2002 19:30:17 -0000 Received: from ultra.sonic.net (208.201.224.22) by a.smtp-out.sonic.net with SMTP; 12 Dec 2002 19:30:17 -0000 Received: from sonic.net (ssl.sonic.net [208.201.224.119]) by ultra.sonic.net (8.11.6/8.8.5) with SMTP id gBCJUHE03220 for ; Thu, 12 Dec 2002 11:30:17 -0800 Message-Id: <200212121930.gBCJUHE03220@ultra.sonic.net> X-envelope-info: Date: Thu, 12 Dec 2002 19:30:17 -0000 To: Subject: Conserver platform - perle/cyclades OK? From: X-Mailer: TWIG 2.7.5 X-Client-IP: 65.197.179.123 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Hello All, We are about to have our first experience using a console server at a small operation having ~20 servers in a nearby single room. I fixed on a pair of candidate platforms to run conserver, the Cyclades TS2000 and Perle CS9000. Finding no signficant negative opinions in the list archives for these two, it seems they are more or less equally desirable. Does anyone out there think one would be better than the other, or are the CS9000 and TS2000 equally good platforms? Regards, S. Kolupaev