From jfn@dassic.com Tue Oct 1 07:46:12 2002 Received: from mail.dassic.com (164.Red-80-59-188.pooles.rima-tde.net [80.59.188.164]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g91EkBKW008251 for ; Tue, 1 Oct 2002 07:46:12 -0700 (PDT) Received: by mail.dassic.com (Postfix, from userid 537) id 43B0424087; Tue, 1 Oct 2002 16:46:06 +0200 (CEST) Received: from 194.224.100.28 ( [194.224.100.28]) as user jfn@localhost by webmail.dassic.com with HTTP; Tue, 1 Oct 2002 16:46:06 +0200 Message-ID: <1033483566.3d99b52e35c33@webmail.dassic.com> Date: Tue, 1 Oct 2002 16:46:06 +0200 From: Jesper Frank Nemholt To: users@conserver.com Subject: Compiling 7.2.3 in Tru64 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 194.224.100.28 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: Hi! I'm normally running it in Linux, but today I tried to compile under Tru64 V4.0F patchkit 7 and Tru64 V5.1A patchkit 3. Both bombed out (Compaq CC/make & GCC/gmake) with the same error : group.c: In function `CheckPass': group.c:410: `pwd' undeclared (first use in this function) group.c:410: (Each undeclared identifier is reported only once group.c:410: for each function it appears in.) group.c:411: `retval' undeclared (first use in this function) make[1]: *** [group.o] Error 1 make[1]: Leaving directory `/usr/users/un19102/src/conserver- 7.2.3/conserver' make: *** [all] Error 1 I can compile if I drop the if/endif around these lines in conserver/group.c : #if HAVE_GETSPNAM struct passwd *pwd; struct spwd *spwd; int retval = AUTH_SUCCESS; #endif; /Jesper From bryan@stansell.org Wed Oct 2 13:45:12 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g92KjCKW024173 for ; Wed, 2 Oct 2002 13:45:12 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g92KjCC7024172 for users@conserver.com; Wed, 2 Oct 2002 13:45:12 -0700 (PDT) Date: Wed, 2 Oct 2002 13:45:12 -0700 From: Bryan Stansell To: users@conserver.com Subject: Re: Compiling 7.2.3 in Tru64 Message-ID: <20021002204512.GA23990@underdog.stansell.org> References: <1033483566.3d99b52e35c33@webmail.dassic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1033483566.3d99b52e35c33@webmail.dassic.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: gack...yep, if you compile 7.2.3 on a non-shadow file system without PAM, you'll get this. sorry about that folks. The next rev will have the #if only around the 'struct spwd' line. thanks for trying it and getting the word out! Bryan > I can compile if I drop the if/endif around these lines in > conserver/group.c : > > #if HAVE_GETSPNAM > struct passwd *pwd; > struct spwd *spwd; > int retval = AUTH_SUCCESS; > #endif; > > /Jesper > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users From brian@specialtyll.com Thu Oct 3 10:06:40 2002 Received: from firewall.specialtyll.com ([204.252.27.90]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g93H6dKW006438 for ; Thu, 3 Oct 2002 10:06:39 -0700 (PDT) Received: from eintein ([192.168.29.89]) by firewall.specialtyll.com (8.11.6/8.11.6) with SMTP id g93H6aB25606 for ; Thu, 3 Oct 2002 13:06:36 -0400 From: "Brian Moriarty" To: Subject: Conserver Protocol Date: Thu, 3 Oct 2002 13:06:21 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Virus-Scanned: by amavis-milter (http://amavis.org/) 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 have a Windows program which I am writing that I want to be able to connect to a conserver. I am about to go through the console.c to figure out the protocol, but I was wondering if it is documented anywhere. Thanks, Brian Brian Moriarty Specialty Loose Leaf, Inc. 1 Cabot Street Holyoke, MA 01040 (413) 532-0106 x344 brian@specialtyll.com From ernie.oporto@viragelogic.com Thu Oct 3 10:15:52 2002 Received: from webshield.viragelogic.com ([63.150.53.109]) by underdog.stansell.org (8.12.6/8.12.6) with SMTP id g93HFqKW006523 for ; Thu, 3 Oct 2002 10:15:52 -0700 (PDT) Received: from gateway.fm.viragelogic.com(129.200.9.1) by webshield.viragelogic.com via csmap id 17124; Thu, 03 Oct 2002 10:15:03 -0700 (PDT) Message-ID: <003601c26b00$42bfbff0$78c0c90a@nj.viragelogic.com> From: "Ernie Oporto" To: "Brian Moriarty" , References: Subject: Re: Conserver Protocol Date: Thu, 3 Oct 2002 10:13:57 -0700 Organization: Virage Logic Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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: Note, console.c already compiles under Cygwin. Let me know if you need a copy of the console.exe I compiled. Ernie ----- Original Message ----- From: "Brian Moriarty" To: Sent: Thursday, October 03, 2002 10:06 AM Subject: Conserver Protocol > I have a Windows program which I am writing that I want to be able to > connect to a conserver. I am about to go through the console.c to figure > out the protocol, but I was wondering if it is documented anywhere. > > Thanks, > Brian > > Brian Moriarty > Specialty Loose Leaf, Inc. > 1 Cabot Street > Holyoke, MA 01040 > (413) 532-0106 x344 > brian@specialtyll.com > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > From bryan@stansell.org Fri Oct 4 13:37:43 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g94KbhKW021904 for ; Fri, 4 Oct 2002 13:37:43 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g94KbhSi021903 for users@conserver.com; Fri, 4 Oct 2002 13:37:43 -0700 (PDT) Date: Fri, 4 Oct 2002 13:37:43 -0700 From: Bryan Stansell To: users@conserver.com Subject: Re: Conserver Protocol Message-ID: <20021004203743.GD21479@underdog.stansell.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: On Thu, Oct 03, 2002 at 01:06:21PM -0400, Brian Moriarty wrote: > I have a Windows program which I am writing that I want to be able to > connect to a conserver. I am about to go through the console.c to figure > out the protocol, but I was wondering if it is documented anywhere. nope. it's not really documented anywhere but within the code (unfortunately). you can do pass a -D to the console client and see the interaction for various commands (like 'console -D console', 'console -D -w', 'console -D -q', etc). that's probably the quickest and easiest way to see what's going on. hope that helps. Bryan From anders@totem.fix.no Sun Oct 6 06:06:41 2002 Received: from totem.fix.no (postfix@totem.fix.no [80.91.32.29]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g96D6fKW017117; Sun, 6 Oct 2002 06:06:41 -0700 (PDT) Received: by totem.fix.no (Postfix, from userid 1000) id 88AC02028D; Sun, 6 Oct 2002 15:06:54 +0200 (CEST) Date: Sun, 6 Oct 2002 15:06:54 +0200 From: Anders Nordby To: Bryan Stansell Cc: users@conserver.com Subject: Re: conserver 7.2.3 and LISA 2002 Message-ID: <20021006130654.GA27545@totem.fix.no> References: <20020923220545.GA26964@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020923220545.GA26964@underdog.stansell.org> User-Agent: Mutt/1.4i X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 X-message-flag: Outlook : A program to spread viri, but it can do mail too. 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: Hi, On Mon, Sep 23, 2002 at 03:05:45PM -0700, Bryan Stansell wrote: > Second, I wanted folks to know that I'm planning on being at the LISA > conference this year (Nov 3-8, http://www.usenix.org/events/lisa02/). > Well, one part, anyway. Specifically, there are plans of having a > conserver BOF (like two years ago), and I'm planning on being there (a > lot of great things came out of the BOF and went into the code last > time). If you're either going to the conference or just in the > neighborhood (Philadelphia), it would be a blast to see you there! > I'll be more than happy to talk about conserver or my current > occupation of traveling full-time out of a backpack (tips on places to > visit throughout the world greatly appreciated - and if you have > pictures, even better). I'll give you one guess as to why I'm not > attending the rest of the conference. ;-) How are things going with the BOF? I am going to LISA this year, and would like to attend. Cheers, -- Anders. From iainr@inf.ed.ac.uk Sun Oct 6 06:29:58 2002 Received: from scarp.dcs.ed.ac.uk (scarp.dcs.ed.ac.uk [129.215.42.241]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g96DTtKW017338 for ; Sun, 6 Oct 2002 06:29:57 -0700 (PDT) Received: from testnode2.inf.ed.ac.uk ([129.215.32.124] helo=inf.ed.ac.uk ident=iainr) by scarp.dcs.ed.ac.uk with esmtp (Exim 3.12 #1) id 17yBTj-00071P-00 for users@conserver.com; Sun, 06 Oct 2002 14:29:51 +0100 Message-ID: <3DA03ACF.7030204@inf.ed.ac.uk> Date: Sun, 06 Oct 2002 14:29:51 +0100 From: Iain Rae User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.1) Gecko/20020930 X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@conserver.com Subject: Re: conserver 7.2.3 and LISA 2002 References: <20020923220545.GA26964@underdog.stansell.org> <20021006130654.GA27545@totem.fix.no> X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Anders Nordby wrote: > Hi, > > On Mon, Sep 23, 2002 at 03:05:45PM -0700, Bryan Stansell wrote: > >>Second, I wanted folks to know that I'm planning on being at the LISA >>conference this year (Nov 3-8, http://www.usenix.org/events/lisa02/). >>Well, one part, anyway. Specifically, there are plans of having a >>conserver BOF (like two years ago), and I'm planning on being there (a >>lot of great things came out of the BOF and went into the code last >>time). If you're either going to the conference or just in the >>neighborhood (Philadelphia), it would be a blast to see you there! >>I'll be more than happy to talk about conserver or my current >>occupation of traveling full-time out of a backpack (tips on places to >>visit throughout the world greatly appreciated - and if you have >>pictures, even better). I'll give you one guess as to why I'm not >>attending the rest of the conference. ;-) > > > How are things going with the BOF? I am going to LISA this year, and > would like to attend. > > Cheers, > I'll be there as well. From bryan@stansell.org Mon Oct 7 19:09:25 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9829OKW005639 for ; Mon, 7 Oct 2002 19:09:24 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9829Osf005638 for users@conserver.com; Mon, 7 Oct 2002 19:09:24 -0700 (PDT) Date: Mon, 7 Oct 2002 19:09:24 -0700 From: Bryan Stansell To: users@conserver.com Subject: LISA BoF and SSL support Message-ID: <20021008020924.GB5495@underdog.stansell.org> References: <20020923220545.GA26964@underdog.stansell.org> <20021006130654.GA27545@totem.fix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021006130654.GA27545@totem.fix.no> 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: i just got email from zonker (who's organizing it with the lisa folks) and it's in progress...there's really no reason why they would deny it. so, folks should plan on it happening. heck, worst case we don't get an official room and we just crash a local pub or some place they don't mind a large group getting together. all the details will be on the bof board at the conference. bofs happen either tuesday or wednesday night (the request was for tuesday). anyway, i'm looking forward to it! as for SSL support, i've got another set of patches (things are looking pretty strong to me - and it integrates all the other fixes to 7.2.3 that folks have been sending me). unfortunately, i haven't been able to find an internet cafe that will let me attach my laptop (i'm actually surprised places let you do that - for fear of viruses and all, ya know). hopefully i'll have something for folks within the next few days (can't take *that* long to find a place, right?). Bryan On Sun, Oct 06, 2002 at 03:06:54PM +0200, Anders Nordby wrote: > How are things going with the BOF? I am going to LISA this year, and > would like to attend. From zonker@jeffk.com Mon Oct 7 21:11:51 2002 Received: from jeffk.com (client13.fre.communitycolo.net [216.218.240.162]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g984BpKW006608 for ; Mon, 7 Oct 2002 21:11:51 -0700 (PDT) Received: (from zonker@localhost) by jeffk.com (8.12.4/8.12.4) id g984BZlV015344; Mon, 7 Oct 2002 21:11:35 -0700 Date: Mon, 7 Oct 2002 21:11:35 -0700 From: "David K. Z. Harris" To: conserver-users@conserver.com Cc: "David K. Z. Harris" Subject: Conserer BoF at LISA 2002 Message-ID: <20021007211135.A6816@jeffk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i 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: According to the USENIX LISA 2002 event staff, the Conserver BoF will be held in Salon K from 7pm to 9pm on Wednesday, November 6th. (Salon K is located on the 5th floor of the Philadelphia Marriott.) Besides having Bryan in town, we look forward to another great gathering of the Conserver community for some brainstorming on future featres, and discussing interesting new tools that play well with Conserver. Charlie Fisher (Computone, now Symbiat) will be providing some hardware for a show & tell session. I'll be bringing a few things as well, so folks can get a good look and feel for some gear that they may want to deploy next year. Cary Roberts (TellMe) is also working with Rackable Systems, to try and get a PIC-Dog-equipped server for folks to see. Cross your fingers! Our last BoF (LISA 2000) was a great boost to the Conserver community, and we're hoping to find some new friends in Philadelphia this year! I've guessed at 50 participants, based on the crowd that came in 2000. (And, considering how many stayed with us going into the second hour, after the alcohol-enhanced vendor- sponsored BoFs had opened, I was really pleased with the whole evening. I hope many of you can join us in November.) -Z- From bryan@stansell.org Thu Oct 10 14:04:34 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9AL4YKW003659; Thu, 10 Oct 2002 14:04:34 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9AL4Y2b003658; Thu, 10 Oct 2002 14:04:34 -0700 (PDT) Date: Thu, 10 Oct 2002 14:04:34 -0700 From: Bryan Stansell To: users@conserver.com, announce@conserver.com Subject: beta OpenSSL patches available Message-ID: <20021010210434.GE13658@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: The second round of patches for OpenSSL support within conserver is available. There are still some changes that will be necessary before they're all official, but it's a pretty strong set of code (at least on my boxes). The support for certificates may or may not actually work (I tried quickly one night with self-signed certificates and the OpenSSL library kept complaining about them - I'm pretty sure I created them wrong), and the encryption only current happens when you connect to a console (not when you're doing a 'console -i', for example). But, without the certificates and the 100% encryption, I've been very successful in hiding the client/server traffic from tcpdump. ;-) You can find them at ftp://ftp.conserver.com/conserver/openssl-patches/ or http://www.conserver.com/openssl-patches/ in the file 7.2.3-to-7.2.4-beta1.patch. I'm hoping that either one or two more rounds of changes will result in the final 7.2.4. I'm not expecting to get everything related to OpenSSL fully functional and stabilized, but it should be close. If you're able to spend a little time just doing a compile test on a system (especially HP-UX, AIX, or other "troublemakers"), I'd love to know if you run into issues (like the whole shadow password build bug in 7.2.3). And now, the complete list of changes... version 7.2.4 (): - added --with-openssl for client/server encryption - added -E option to client and server to allow for non-encrypted connections (encryption is the default if compiled in) - added -c option so credentials (certificate and key) can be exchanged between client and server - expanded -V output to show what optional bits actually got compiled into the code (libwrap, regex, etc) - compilation errors on non-shadow file systems without using --with-pam - reported by Jesper Frank Nemholt - client now prefers $LOGNAME, then $USER, then the current uid for it's -l default - suggested by Dave Stuit - putting back socklen_t usage - it's the right thing to do, so tell me where it breaks things Bryan From bryan@stansell.org Mon Oct 14 14:20:33 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9ELKXKW014249; Mon, 14 Oct 2002 14:20:33 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9ELKXlZ014248; Mon, 14 Oct 2002 14:20:33 -0700 (PDT) Date: Mon, 14 Oct 2002 14:20:33 -0700 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Subject: conserver 7.2.4 is available Message-ID: <20021014212033.GD29063@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: I've decided to go ahead and release 7.2.4 as it stands (there have been a couple changes since the 7.2.4-beta1 patch). There are a couple of reasons for this. First, the build issues with regard to shadow password support just made my stomach turn - I really goofed there and getting a working version out makes me much calmer. Second, there are some major changes necessary for the OpenSSL code to really work like I would want. 7.2.4 gives you basic console encryption without breaking any backwards-compatibility with older clients and servers (assuming you use the -E flag). It doesn't, however, encrypt things like 'console -w' output, and, even worse, 'console -q' (which could send the root password). To fix these things, I'm going to have to change the client-server protocol to such an extent that it will break backwards-compatibility and I figured I'd take conserver from 7.2.4 to 7.3.0 when doing so. The good news, however, is that encryption and certificates do work (for me, at least). I've provided my script (contrib/maketestcerts) to show how I created and tested things. Even without certificates, the encryption will be negotiated and things will look like garbage on the wire. Check the man pages for details on the new features. If anyone finds any problems, please let me know. I'm sure there will be some compatibility issues with platforms like HP-UX/64-bit and AIX (there always are), but I'd love to work through them with you and find a solid fix. And, for the official record, all the changes in this release... version 7.2.4 (Oct 14, 2002): - added --with-openssl for some client/server encryption - added -E option to client and server to allow for non-encrypted connections (encryption is the default if compiled in) - added -c option so credentials (certificate and key) can be exchanged between client and server - expanded -V output to show what optional bits actually got compiled into the code (libwrap, regex, etc) - compilation errors on non-shadow file systems without using --with-pam - reported by Jesper Frank Nemholt - client now prefers $LOGNAME, then $USER, then the current uid for its -l default - suggested by Dave Stuit - putting back socklen_t usage - it's the right thing to do, so tell me where it breaks things - configure options --with-cffile and --with-pwdfile now recognize fully-qualified pathnames - suggested by Kjell Andresen Bryan Stansell From slammert@panasas.com Mon Oct 14 22:13:01 2002 Received: from localhost.localdomain (pa-gbg-ts-03-024-197-052-186.winbeam.com [24.197.52.186]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9F5CxKW017734 for ; Mon, 14 Oct 2002 22:13:00 -0700 (PDT) Received: from panasas.com (palantir [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g9F5Cui19748 for ; Tue, 15 Oct 2002 01:12:57 -0400 Message-ID: <3DABA3D8.30004@panasas.com> Date: Tue, 15 Oct 2002 01:12:56 -0400 From: Steve Lammert Organization: Panasas, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: users@conserver.com Subject: Automatic reinitialization, revisited References: <20021014212033.GD29063@underdog.stansell.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Hi. I've been a contented user of Conserver for several years, and currently have about 900 serial ports under management at three sites. Over time, we've used various Annex products, the Digi EtherLite, Cyclades TS-x000, and local devices, all with little or no trouble. However, an attempt by one of our sites to try something new has generated major headaches for me. They've purchased four 64-port Cyclades Ze cards and installed them in an x86 box running FreeBSD 4.3. Cyclades provides a device driver (current version 2.1.1) which is then compiled into the BSD kernel. After the subsequent reboot, one ends up with a slough of /dev/ttyCxx entries to talk to. The fortunate thing is that the cards were installed in the machine which is our Conserver at that site. Here's the unfortunate thing: We can talk to these devices just fine using "tip" and similar tools, but have (so far) been unable to get Conserver to make use of them. A simple conserver.cf entry of the form: beta2-5-1:/dev/ttyCd6:9600p:&: produces a string of error messages in /var/log/conserver of the form: conserver (6804): beta2-5-1: exit(3) [Mon Oct 14 21:51:39 2002] conserver (6804): beta2-5-1: automatic reinitialization [Mon Oct 14 21:51:39 2002] New messages appear once per second, per serial line. Imagine the spew if you have 256 of these defined (:-(} If this looks familiar, it may be because you recall a similar thread started by Malcolm Gibbs back in May. His problems, though, seemed to center on reinitialization loops for lines which were actually down (not in use). In my case, these lines are connected and active -- if I kill the conserver daemons (or just comment out the relevant lines and kill -HUP), then connect to the device using "tip", I can have a perfectly acceptable session. As a workaround, we've configured Conserver to use "| tip " in order to get things working. But, gack, I really don't want to have 256 "tip" sessions running all the time... Is anyone out there using a similar setup (Cyclades Ze on FreeBSD?). If so, was there any magic involved (e.g. settings in dev/cz/config.h before recompiling the kernel) in getting the devices to play nice with the Conserver? or did it "just work" for you? Thanks, Steve L -- -- steve lammert software engineer voice: +1-412-323-3500 slammert@panasas.com panasas, inc fax: +1-412-323-3511 From bryan@conserver.com Tue Oct 15 08:58:44 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9FFwhKW025780 for ; Tue, 15 Oct 2002 08:58:43 -0700 (PDT) Received: (from www@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9FFwhVU025779 for users@conserver.com; Tue, 15 Oct 2002 08:58:43 -0700 (PDT) To: users@conserver.com Subject: Re: Automatic reinitialization, revisited Message-ID: <1034697523.3dac3b33a0c7c@www.stansell.org> Date: Tue, 15 Oct 2002 08:58:43 -0700 (PDT) From: bryan@conserver.com References: <20021014212033.GD29063@underdog.stansell.org> <3DABA3D8.30004@panasas.com> In-Reply-To: <3DABA3D8.30004@panasas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 24.203.252.235 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: Quoting Steve Lammert : > A simple conserver.cf entry of the form: > > beta2-5-1:/dev/ttyCd6:9600p:&: > > produces a string of error messages in /var/log/conserver of the form: > > conserver (6804): beta2-5-1: exit(3) [Mon Oct 14 21:51:39 2002] > conserver (6804): beta2-5-1: automatic reinitialization [Mon Oct 14 that's bizarre. the "exit(3)" indicates that conserver thinks the console type is a program ("|blah" syntax) instead of a device file ("/blah" syntax). you're really getting these? something is just very wrong, if so. something you can do is run conserver with the -D flag (redirect things to a file) and then kill it after it's tried to start up. that will dump the internal tables and we can look and see what the console types are set to, what the path names are, etc. could be something is getting munched when it's reading the config file. or something else bad is happening. whatever the case, the error and the console specifications just don't match, so something very wrong is happening (which could explain the lack of functionality). Bryan From bryan@conserver.com Tue Oct 15 09:03:05 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9FG35KW025850 for ; Tue, 15 Oct 2002 09:03:05 -0700 (PDT) Received: (from www@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9FG35Je025849 for users@conserver.com; Tue, 15 Oct 2002 09:03:05 -0700 (PDT) To: users@conserver.com Subject: asking for a vote Message-ID: <1034697785.3dac3c3974399@www.stansell.org> Date: Tue, 15 Oct 2002 09:03:05 -0700 (PDT) From: bryan@conserver.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 24.203.252.235 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: if you have any opinion, please respond to me directly, instead of the list, so i can count opinions. basically, i'm looking at the client-server protocol and wondering if it's really a good idea for folks to be able to do a 'console -i', 'console -w', etc, without providing a username and password (if passwords are required via the conserver.passwd file). currently, anyone can connect to a conserver process, retrieve information, and then possibly use it against you. this seems like a bad idea to me, and i was thinking conserver should not give out *any* information without first going through the user verification process (if required by the config files). what do folks think? is anyone out there using the fact that you can poll for information without first authenticating? i could see automated scripts breaking, or perhaps other cases where it won't work. the biggest issue i see is that access is restricted to certain consoles. i figured that if you could authenticate to *any* console, you could poll for information (in the new model). thoughts? Bryan From slammert@panasas.com Tue Oct 15 09:45:55 2002 Received: from localhost.localdomain (gw2.panasas.com [65.194.124.178]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9FGjsKW026184; Tue, 15 Oct 2002 09:45:54 -0700 (PDT) Received: from panasas.com (palantir [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g9FGjmg21400; Tue, 15 Oct 2002 12:45:48 -0400 Message-ID: <3DAC463C.1020109@panasas.com> Date: Tue, 15 Oct 2002 12:45:48 -0400 From: Steve Lammert Organization: Panasas, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: bryan@conserver.com CC: users@conserver.com Subject: Re: Automatic reinitialization, revisited References: <20021014212033.GD29063@underdog.stansell.org> <3DABA3D8.30004@panasas.com> <1034697523.3dac3b33a0c7c@www.stansell.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: oops. I obviously cut-and-pasted from the wrong part of the log. My apologies. I just generated a fresh set of errors. The following conserver.cf entry: beta2-5-1:/dev/ttyCc8:9600p:&: produced an endless string of errors, viz: conserver (23228): beta2-5-1: automatic reinitialization [Tue Oct 15 09:39:26 2002] conserver (23228): lost carrier on beta2-5-1 (/dev/ttyCc8)! [Tue Oct 15 09:39:29 2002] conserver (23228): beta2-5-1: automatic reinitialization [Tue Oct 15 09:39:29 2002] conserver (23228): lost carrier on beta2-5-1 (/dev/ttyCc8)! [Tue Oct 15 09:39:32 2002] No exit() call this time. (:-)} bryan@conserver.com wrote: > Quoting Steve Lammert : > >>A simple conserver.cf entry of the form: >> >> beta2-5-1:/dev/ttyCd6:9600p:&: >> >>produces a string of error messages in /var/log/conserver of the form: >> >> conserver (6804): beta2-5-1: exit(3) [Mon Oct 14 21:51:39 2002] >> conserver (6804): beta2-5-1: automatic reinitialization [Mon Oct 14 >> > > that's bizarre. the "exit(3)" indicates that conserver thinks the console > type is a program ("|blah" syntax) instead of a device file ("/blah" syntax). > you're really getting these? something is just very wrong, if so. something > you can do is run conserver with the -D flag (redirect things to a file) and > then kill it after it's tried to start up. that will dump the internal tables > and we can look and see what the console types are set to, what the path names > are, etc. could be something is getting munched when it's reading the config > file. or something else bad is happening. > > whatever the case, the error and the console specifications just don't match, > so something very wrong is happening (which could explain the lack of > functionality). > > Bryan > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > -- -- steve lammert software engineer voice: +1-412-323-3500 slammert@panasas.com panasas, inc fax: +1-412-323-3511 From psmith@physics.purdue.edu Tue Oct 15 11:17:03 2002 Received: from franklin.physics.purdue.edu (franklin.physics.purdue.edu [128.210.146.222]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9FIH3KW026861 for ; Tue, 15 Oct 2002 11:17:03 -0700 (PDT) Received: from physics.purdue.edu (curie.physics.purdue.edu [128.210.68.223]) by franklin.physics.purdue.edu (Postfix) with ESMTP id 6630F2100E; Tue, 15 Oct 2002 13:17:02 -0500 (EST) Received: by physics.purdue.edu (Postfix, from userid 12494) id 244C217; Tue, 15 Oct 2002 13:17:02 -0500 (EST) Date: Tue, 15 Oct 2002 13:17:02 -0500 From: Preston Smith To: Steve Lammert Cc: users@conserver.com Subject: Re: Automatic reinitialization, revisited Message-ID: <20021015181702.GA68235@curie.physics.purdue.edu> References: <20021014212033.GD29063@underdog.stansell.org> <3DABA3D8.30004@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DABA3D8.30004@panasas.com> User-Agent: Mutt/1.3.25i 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: On Tue, Oct 15, 2002 at 01:12:56AM -0400, Steve Lammert (slammert@panasas.com) wrote: > The fortunate thing is that the cards were installed in the machine > which is our Conserver at that site. Here's the unfortunate thing: We > can talk to these devices just fine using "tip" and similar tools, but > have (so far) been unable to get Conserver to make use of them. > > produces a string of error messages in /var/log/conserver of the form: > > conserver (6804): beta2-5-1: exit(3) [Mon Oct 14 21:51:39 2002] > conserver (6804): beta2-5-1: automatic reinitialization [Mon Oct 14 > 21:51:39 2002] > > New messages appear once per second, per serial line. Imagine the spew > if you have 256 of these defined (:-(} > > Is anyone out there using a similar setup (Cyclades Ze on FreeBSD?). If > so, was there any magic involved (e.g. settings in dev/cz/config.h > before recompiling the kernel) in getting the devices to play nice with > the Conserver? or did it "just work" for you? I couldn't get FreeBSD 4-STABLE to work with conserver on a Cyclades-Z either. We had our conserver system running FreeBSD 3.2 for some time, but I upgraded it to 4-STABLE last month, and ran into exactly the same problem you encountered. Other telecom programs could talk to the Cyclades-Z fine, but not conserver. I checked with the other guys who reported this problem a couple months ago, and nobody'd seemed to have found a solution. (One of the previous posters is from your site, if I recall..) I wrestled with it for a day or so, but wound up just installing Linux on the aforementioned conserver server. Worked fine, then. Never tracked down if it was a problem with FreeBSD in general, the cz driver, or something within conserver. But at least you know it's not just you. -- Preston Smith UNIX Analyst Purdue University Physics Computer Network GPG Fingerprint: 6D27 5DAA F58D C42B 7A6B 8F48 04E4 2465 F353 03F6 From cfowler@outpostsentinel.com Wed Oct 16 04:10:17 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 g9GBAGKW007319 for ; Wed, 16 Oct 2002 04:10:17 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9GBB5011940; Wed, 16 Oct 2002 07:11:05 -0400 Subject: Re: Automatic reinitialization, revisited From: cfowler To: Preston Smith Cc: Steve Lammert , users@conserver.com In-Reply-To: <20021015181702.GA68235@curie.physics.purdue.edu> References: <20021014212033.GD29063@underdog.stansell.org> <3DABA3D8.30004@panasas.com> <20021015181702.GA68235@curie.physics.purdue.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 16 Oct 2002 07:11:05 -0400 Message-Id: <1034766666.11796.10.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: If this is truly the case then it must be a slight tty settings in FreeBSD. Maybe you guys would not mind figuring out what is wrong and sending this list a patch? On Tue, 2002-10-15 at 14:17, Preston Smith wrote: > On Tue, Oct 15, 2002 at 01:12:56AM -0400, Steve Lammert (slammert@panasas.com) wrote: > > The fortunate thing is that the cards were installed in the machine > > which is our Conserver at that site. Here's the unfortunate thing: We > > can talk to these devices just fine using "tip" and similar tools, but > > have (so far) been unable to get Conserver to make use of them. > > > > produces a string of error messages in /var/log/conserver of the form: > > > > conserver (6804): beta2-5-1: exit(3) [Mon Oct 14 21:51:39 2002] > > conserver (6804): beta2-5-1: automatic reinitialization [Mon Oct 14 > > 21:51:39 2002] > > > > New messages appear once per second, per serial line. Imagine the spew > > if you have 256 of these defined (:-(} > > > > Is anyone out there using a similar setup (Cyclades Ze on FreeBSD?). If > > so, was there any magic involved (e.g. settings in dev/cz/config.h > > before recompiling the kernel) in getting the devices to play nice with > > the Conserver? or did it "just work" for you? > > I couldn't get FreeBSD 4-STABLE to work with conserver on a Cyclades-Z > either. > > We had our conserver system running FreeBSD 3.2 for some time, but I > upgraded it to 4-STABLE last month, and ran into exactly the same problem > you encountered. Other telecom programs could talk to the Cyclades-Z fine, > but not conserver. I checked with the other guys who reported this problem > a couple months ago, and nobody'd seemed to have found a solution. (One > of the previous posters is from your site, if I recall..) > > I wrestled with it for a day or so, but wound up just installing Linux > on the aforementioned conserver server. Worked fine, then. Never tracked > down if it was a problem with FreeBSD in general, the cz driver, or > something within conserver. But at least you know it's not just you. > > -- > Preston Smith > UNIX Analyst Purdue University Physics Computer Network > GPG Fingerprint: 6D27 5DAA F58D C42B 7A6B 8F48 04E4 2465 F353 03F6 > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From corey@rentec.com Tue Oct 22 07:46:40 2002 Received: from ram.rentec.com (ram.rentec.com [192.5.35.66]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9MEkdKW024763 for ; Tue, 22 Oct 2002 07:46:40 -0700 (PDT) Received: from grizzly.rentec.com (IDENT:1@grizzly.rentec.com [192.5.35.162]) by ram.rentec.com (8.12.1/8.12.1) with ESMTP id g9MEkYVI024056 for ; Tue, 22 Oct 2002 10:46:34 -0400 (EDT) Received: (from corey@localhost) by grizzly.rentec.com (8.11.6+Sun/8.11.6) id g9MEkY723339; Tue, 22 Oct 2002 10:46:34 -0400 (EDT) X-Authentication-Warning: grizzly.rentec.com: corey set sender to corey@rentec.com using -f Subject: polling consoles From: Corey Hirschman To: users@conserver.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 22 Oct 2002 10:46:34 -0400 Message-Id: <1035297994.1067.41.camel@grizzly> 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 was wondering if there is any way for conserver to test the connection between itself and the consoles it is aware of. We run into a problem that if a terminal server goes down unexpectedly, conserver will not realize that the TCP connections have been broken and will keep them marked as up. The terminal server, once back up, no longer knows about the connections so none of the console messages are put into the logs, until conserver is either restarted or an explicit connection is made to each machine. A similar problem occurs if one of the nodes in our cluster crashes. Once it is fixed and brought back up, conserver does not kill the bad connection and reestablish a connection with the node until an explicit connection is made to the node. I know this popped up on the list about a year ago and at that time there was nothing that could be done within conserver. I was wondering if there is now a way to monitor connection status and if not get suggestions as to how to best implement it. Corey From cfowler@outpostsentinel.com Tue Oct 22 07:51:45 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 g9MEpiKW024825 for ; Tue, 22 Oct 2002 07:51:44 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9MErF022957; Tue, 22 Oct 2002 10:53:15 -0400 Subject: Re: polling consoles From: cfowler To: Corey Hirschman Cc: users@conserver.com In-Reply-To: <1035297994.1067.41.camel@grizzly> References: <1035297994.1067.41.camel@grizzly> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Oct 2002 10:53:14 -0400 Message-Id: <1035298395.24952.55.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 have this same problem with the console client. We have been embedding conserver and rebooting our embedded devices often. So when someone reboots a device console does not know of that connection death. On Tue, 2002-10-22 at 10:46, Corey Hirschman wrote: > I was wondering if there is any way for conserver to test the connection > between itself and the consoles it is aware of. > > We run into a problem that if a terminal server goes down unexpectedly, > conserver will not realize that the TCP connections have been broken and > will keep them marked as up. The terminal server, once back up, no > longer knows about the connections so none of the console messages are > put into the logs, until conserver is either restarted or an explicit > connection is made to each machine. > > A similar problem occurs if one of the nodes in our cluster crashes. > Once it is fixed and brought back up, conserver does not kill the bad > connection and reestablish a connection with the node until an explicit > connection is made to the node. > > I know this popped up on the list about a year ago and at that time > there was nothing that could be done within conserver. I was wondering > if there is now a way to monitor connection status and if not get > suggestions as to how to best implement it. > > Corey > > > > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From cfowler@outpostsentinel.com Tue Oct 22 08:10:28 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 g9MFARKW024973 for ; Tue, 22 Oct 2002 08:10:27 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9MFBu028652; Tue, 22 Oct 2002 11:11:56 -0400 Subject: Re: polling consoles From: cfowler To: cfowler Cc: Corey Hirschman , users@conserver.com In-Reply-To: <1035298395.24952.55.camel@cfowler.outpostsentinel.com> References: <1035297994.1067.41.camel@grizzly> <1035298395.24952.55.camel@cfowler.outpostsentinel.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Oct 2002 11:11:56 -0400 Message-Id: <1035299517.24952.61.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: My problem is that I only get to Error("lost connection"); After console.c attempts a write. I also get garbage displayed on tty after the lost connection message is displayed. I'm tracking that down now! On Tue, 2002-10-22 at 10:53, cfowler wrote: > I have this same problem with the console client. We have been > embedding conserver and rebooting our embedded devices often. So when > someone reboots a device console does not know of that connection death. > > > On Tue, 2002-10-22 at 10:46, Corey Hirschman wrote: > > I was wondering if there is any way for conserver to test the connection > > between itself and the consoles it is aware of. > > > > We run into a problem that if a terminal server goes down unexpectedly, > > conserver will not realize that the TCP connections have been broken and > > will keep them marked as up. The terminal server, once back up, no > > longer knows about the connections so none of the console messages are > > put into the logs, until conserver is either restarted or an explicit > > connection is made to each machine. > > > > A similar problem occurs if one of the nodes in our cluster crashes. > > Once it is fixed and brought back up, conserver does not kill the bad > > connection and reestablish a connection with the node until an explicit > > connection is made to the node. > > > > I know this popped up on the list about a year ago and at that time > > there was nothing that could be done within conserver. I was wondering > > if there is now a way to monitor connection status and if not get > > suggestions as to how to best implement it. > > > > Corey > > > > > > > > > > _______________________________________________ > > users mailing list > > users@conserver.com > > https://www.conserver.com/mailman/listinfo/users > > > > > > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From corey@rentec.com Tue Oct 22 08:41:52 2002 Received: from wren.rentec.com (rtc12-9.rentec.com [65.213.84.9]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9MFfpKW025220 for ; Tue, 22 Oct 2002 08:41:51 -0700 (PDT) Received: from grizzly.rentec.com (IDENT:1@grizzly.rentec.com [192.5.35.162]) by wren.rentec.com (8.12.1/8.12.1) with ESMTP id g9MFfVWe018855; Tue, 22 Oct 2002 11:41:31 -0400 (EDT) Received: (from corey@localhost) by grizzly.rentec.com (8.11.6+Sun/8.11.6) id g9MFfVG23386; Tue, 22 Oct 2002 11:41:31 -0400 (EDT) X-Authentication-Warning: grizzly.rentec.com: corey set sender to corey@rentec.com using -f Subject: Re: polling consoles From: Corey Hirschman To: cfowler Cc: users@conserver.com In-Reply-To: <1035300870.24952.73.camel@cfowler.outpostsentinel.com> References: <1035297994.1067.41.camel@grizzly> <1035300870.24952.73.camel@cfowler.outpostsentinel.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 22 Oct 2002 11:41:31 -0400 Message-Id: <1035301291.1067.47.camel@grizzly> 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: You seem to have a greater problem than I do. :) Once the terminal server is back up, I can do console , conserver then realizes the connection is really not up and does a reset to bring it up. After that I am good to go. The problem is that I have to do that to reestablish the connection, or restart conserver. It would be better (at least I think so) if conserver did this automatically at a time specified in minutes on the command line when conserver is launched or perhaps in the conserver.cf file. This way, any console messages will continue to be logged automatically after only a short interruption. On Tue, 2002-10-22 at 11:34, cfowler wrote: > Here is a chnage I made to console.c form 7.2.3 It needs a tweak but it > clears up the garbage on connection loss. > > > Index: console.c > ================================================================== > RCS file: /u01/ENS/CVS/outpost/src/conserver/console/console.c,v > retrieving revision 1.2 > diff -u -r1.2 console.c > --- console.c 16 Oct 2002 18:00:55 -0000 1.2 > +++ console.c 22 Oct 2002 15:32:15 -0000 > @@ -1113,11 +1113,9 @@ > > /* anything from socket? */ > if (FD_ISSET(fileFDNum(pcf), &rmask)) { > - if ((nc = fileRead(pcf, acMesg, sizeof(acMesg))) == 0) { > - if (justProcessedUrg) { > - printf("\n"); > - Error("lost connection"); > - } > + if ((nc = fileRead(pcf, acMesg, sizeof(acMesg))) <= 0) { > + printf("\n"); > + Error("lost connection"); > break; > } > if (fStrip) { > @@ -1141,6 +1139,9 @@ > c2cooked(); > if (fVerbose) > printf("Console %s closed.\n", pcMach); > + > + printf("\n"); > + > return 0; > } > > > > On Tue, 2002-10-22 at 10:46, Corey Hirschman wrote: > > I was wondering if there is any way for conserver to test the connection > > between itself and the consoles it is aware of. > > > > We run into a problem that if a terminal server goes down unexpectedly, > > conserver will not realize that the TCP connections have been broken and > > will keep them marked as up. The terminal server, once back up, no > > longer knows about the connections so none of the console messages are > > put into the logs, until conserver is either restarted or an explicit > > connection is made to each machine. > > > > A similar problem occurs if one of the nodes in our cluster crashes. > > Once it is fixed and brought back up, conserver does not kill the bad > > connection and reestablish a connection with the node until an explicit > > connection is made to the node. > > > > I know this popped up on the list about a year ago and at that time > > there was nothing that could be done within conserver. I was wondering > > if there is now a way to monitor connection status and if not get > > suggestions as to how to best implement it. > > > > Corey > > > > > > > > > > _______________________________________________ > > users mailing list > > users@conserver.com > > https://www.conserver.com/mailman/listinfo/users > > > > > > > From cfowler@outpostsentinel.com Tue Oct 22 09:39:56 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 g9MGdrKW025629 for ; Tue, 22 Oct 2002 09:39:55 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9MGfJ028981; Tue, 22 Oct 2002 12:41:20 -0400 Subject: Re: polling consoles From: cfowler To: Corey Hirschman Cc: users@conserver.com In-Reply-To: <1035301291.1067.47.camel@grizzly> References: <1035297994.1067.41.camel@grizzly> <1035300870.24952.73.camel@cfowler.outpostsentinel.com> <1035301291.1067.47.camel@grizzly> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Oct 2002 12:41:19 -0400 Message-Id: <1035304881.24952.80.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: Yea I see. I've modified my conserver daemon to send notifications of these conditions. I need this condition to tell administrators that the managed device is down. Of course I use SNMP traps to do this. I pretty much all the time know what state any console is in. ] On Tue, 2002-10-22 at 11:41, Corey Hirschman wrote: > You seem to have a greater problem than I do. :) > > Once the terminal server is back up, I can do console , > conserver then realizes the connection is really not up and does a reset > to bring it up. After that I am good to go. The problem is that I have > to do that to reestablish the connection, or restart conserver. It > would be better (at least I think so) if conserver did this > automatically at a time specified in minutes on the command line when > conserver is launched or perhaps in the conserver.cf file. This way, > any console messages will continue to be logged automatically after only > a short interruption. > > > On Tue, 2002-10-22 at 11:34, cfowler wrote: > > Here is a chnage I made to console.c form 7.2.3 It needs a tweak but it > > clears up the garbage on connection loss. > > > > > > Index: console.c > > ================================================================== > > RCS file: /u01/ENS/CVS/outpost/src/conserver/console/console.c,v > > retrieving revision 1.2 > > diff -u -r1.2 console.c > > --- console.c 16 Oct 2002 18:00:55 -0000 1.2 > > +++ console.c 22 Oct 2002 15:32:15 -0000 > > @@ -1113,11 +1113,9 @@ > > > > /* anything from socket? */ > > if (FD_ISSET(fileFDNum(pcf), &rmask)) { > > - if ((nc = fileRead(pcf, acMesg, sizeof(acMesg))) == 0) { > > - if (justProcessedUrg) { > > - printf("\n"); > > - Error("lost connection"); > > - } > > + if ((nc = fileRead(pcf, acMesg, sizeof(acMesg))) <= 0) { > > + printf("\n"); > > + Error("lost connection"); > > break; > > } > > if (fStrip) { > > @@ -1141,6 +1139,9 @@ > > c2cooked(); > > if (fVerbose) > > printf("Console %s closed.\n", pcMach); > > + > > + printf("\n"); > > + > > return 0; > > } > > > > > > > > On Tue, 2002-10-22 at 10:46, Corey Hirschman wrote: > > > I was wondering if there is any way for conserver to test the connection > > > between itself and the consoles it is aware of. > > > > > > We run into a problem that if a terminal server goes down unexpectedly, > > > conserver will not realize that the TCP connections have been broken and > > > will keep them marked as up. The terminal server, once back up, no > > > longer knows about the connections so none of the console messages are > > > put into the logs, until conserver is either restarted or an explicit > > > connection is made to each machine. > > > > > > A similar problem occurs if one of the nodes in our cluster crashes. > > > Once it is fixed and brought back up, conserver does not kill the bad > > > connection and reestablish a connection with the node until an explicit > > > connection is made to the node. > > > > > > I know this popped up on the list about a year ago and at that time > > > there was nothing that could be done within conserver. I was wondering > > > if there is now a way to monitor connection status and if not get > > > suggestions as to how to best implement it. > > > > > > Corey > > > > > > > > > > > > > > > _______________________________________________ > > > users mailing list > > > users@conserver.com > > > https://www.conserver.com/mailman/listinfo/users > > > > > > > > > > > > > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From bryan@conserver.com Tue Oct 22 14:38:42 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9MLcgKW027975 for ; Tue, 22 Oct 2002 14:38:42 -0700 (PDT) Received: (from www@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9MLcgJS027974 for users@conserver.com; Tue, 22 Oct 2002 14:38:42 -0700 (PDT) To: users@conserver.com Subject: Re: polling consoles Message-ID: <1035322722.3db5c5620b604@www.stansell.org> Date: Tue, 22 Oct 2002 14:38:42 -0700 (PDT) From: bryan@conserver.com References: <1035297994.1067.41.camel@grizzly> <1035298395.24952.55.camel@cfowler.outpostsentinel.com> In-Reply-To: <1035298395.24952.55.camel@cfowler.outpostsentinel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 216.209.128.132 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: Quoting cfowler : > I have this same problem with the console client. We have been > embedding conserver and rebooting our embedded devices often. So when > someone reboots a device console does not know of that connection > death. assuming you're still using the code based on what is released on conserver.com, you will get notifications to all the clients if you actually kill the conserver daemon (gracefully) instead of just halting the operating system or sending it a SIGKILL. just my 2 cents, for now. Bryan From cfowler@outpostsentinel.com Tue Oct 22 14:43:32 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 g9MLhVKW028058; Tue, 22 Oct 2002 14:43:31 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9MLj7002503; Tue, 22 Oct 2002 17:45:08 -0400 Subject: Re: polling consoles From: cfowler To: bryan@conserver.com Cc: users@conserver.com In-Reply-To: <1035322722.3db5c5620b604@www.stansell.org> References: <1035297994.1067.41.camel@grizzly> <1035298395.24952.55.camel@cfowler.outpostsentinel.com> <1035322722.3db5c5620b604@www.stansell.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Oct 2002 17:45:07 -0400 Message-Id: <1035323108.2290.13.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: Oops. Sorry I confused some. Yes it is based on conserver.com. I get snmp traps when any console drops its DTR. On Tue, 2002-10-22 at 17:38, bryan@conserver.com wrote: > Quoting cfowler : > > I have this same problem with the console client. We have been > > embedding conserver and rebooting our embedded devices often. So when > > someone reboots a device console does not know of that connection > > death. > > assuming you're still using the code based on what is released on > conserver.com, you will get notifications to all the clients if you > actually kill the conserver daemon (gracefully) instead of just halting > the operating system or sending it a SIGKILL. > > just my 2 cents, for now. > > Bryan > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From bryan@conserver.com Tue Oct 22 14:43:57 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9MLhvKW028067 for ; Tue, 22 Oct 2002 14:43:57 -0700 (PDT) Received: (from www@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9MLhvea028066 for users@conserver.com; Tue, 22 Oct 2002 14:43:57 -0700 (PDT) To: users@conserver.com Subject: Re: polling consoles Message-ID: <1035323037.3db5c69d0d5f6@www.stansell.org> Date: Tue, 22 Oct 2002 14:43:57 -0700 (PDT) From: bryan@conserver.com References: <1035297994.1067.41.camel@grizzly> In-Reply-To: <1035297994.1067.41.camel@grizzly> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 216.209.128.132 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: Quoting Corey Hirschman : > I was wondering if there is any way for conserver to test the > connection > between itself and the consoles it is aware of. you know, that's a good question. i'm not sure if there is, but it would be an interesting feature to add. perhaps, since most terminal vendors use the "reverse-telnet" stuff we can send a noop-type telnet escape sequence if there hasn't been activity. but, that doesn't really help in other cases, such as an ssh connection done via the "|/usr/local/bin/ssh..." type syntax...that too will just sorta hang and not notice an abrupt drop in a terminal server. so, for a general case, i don't have any good ideas...but perhaps we can do something for the telnet-based terminal servers. anyone have any other bright ideas? some socket-level thing we can do? although that doesn't help the ssh-type stuff...ugh. we can't send regular traffic, that's for sure. Bryan From cfowler@outpostsentinel.com Tue Oct 22 14:46:03 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 g9MLk3KW028138; Tue, 22 Oct 2002 14:46:03 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id g9MLld002514; Tue, 22 Oct 2002 17:47:39 -0400 Subject: Re: polling consoles From: cfowler To: bryan@conserver.com Cc: users@conserver.com In-Reply-To: <1035323037.3db5c69d0d5f6@www.stansell.org> References: <1035297994.1067.41.camel@grizzly> <1035323037.3db5c69d0d5f6@www.stansell.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 22 Oct 2002 17:47:39 -0400 Message-Id: <1035323259.30595.15.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: What about SOKEEPALIVE? On Tue, 2002-10-22 at 17:43, bryan@conserver.com wrote: > Quoting Corey Hirschman : > > I was wondering if there is any way for conserver to test the > > connection > > between itself and the consoles it is aware of. > > you know, that's a good question. i'm not sure if there is, but it > would be an interesting feature to add. perhaps, since most terminal > vendors use the "reverse-telnet" stuff we can send a noop-type telnet > escape sequence if there hasn't been activity. but, that doesn't > really help in other cases, such as an ssh connection done via the > "|/usr/local/bin/ssh..." type syntax...that too will just sorta hang > and not notice an abrupt drop in a terminal server. > > so, for a general case, i don't have any good ideas...but perhaps we > can do something for the telnet-based terminal servers. > > anyone have any other bright ideas? some socket-level thing we can do? > although that doesn't help the ssh-type stuff...ugh. > > we can't send regular traffic, that's for sure. > > Bryan > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users > > From corey@rentec.com Thu Oct 24 08:41:18 2002 Received: from wren.rentec.com (rtc12-9.rentec.com [65.213.84.9]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9OFfHKW022246 for ; Thu, 24 Oct 2002 08:41:18 -0700 (PDT) Received: from grizzly.rentec.com (IDENT:1@grizzly.rentec.com [192.5.35.162]) by wren.rentec.com (8.12.1/8.12.1) with ESMTP id g9OFf5We020174 for ; Thu, 24 Oct 2002 11:41:05 -0400 (EDT) Received: (from corey@localhost) by grizzly.rentec.com (8.11.6+Sun/8.11.6) id g9OFf4g24706; Thu, 24 Oct 2002 11:41:04 -0400 (EDT) X-Authentication-Warning: grizzly.rentec.com: corey set sender to corey@rentec.com using -f Subject: Re: polling consoles From: Corey Hirschman To: users@conserver.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 24 Oct 2002 11:41:04 -0400 Message-Id: <1035474064.1067.81.camel@grizzly> 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: As of version 7.2.4 conserver is actually using SOKEEPALIVE. This explains that weird 2 hour behavior I was seeing. If I killed the power on the console server and then powered it back up, I would get no logging for 2 hours. Then a keepalive packet would be sent to all the connections that were marked as up. Since they were really bad connections at that point, they would be marked as down. Conserver would then do it's auto up and reestablish the connections. So this pretty much takes care of polling the machines. You do lose 2 hours of logging (unless you feel like playing with TCP), but that is better than it not coming up at all. Corey From bryan@conserver.com Thu Oct 24 20:52:08 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.6/8.12.6) with ESMTP id g9P3q8KW027292 for ; Thu, 24 Oct 2002 20:52:08 -0700 (PDT) Received: (from www@localhost) by underdog.stansell.org (8.12.6/8.12.6/Submit) id g9P3q8rJ027291 for users@conserver.com; Thu, 24 Oct 2002 20:52:08 -0700 (PDT) To: users@conserver.com Subject: Re: polling consoles Message-ID: <1035517928.3db8bfe808fbf@www.stansell.org> Date: Thu, 24 Oct 2002 20:52:08 -0700 (PDT) From: bryan@conserver.com References: <1035474064.1067.81.camel@grizzly> In-Reply-To: <1035474064.1067.81.camel@grizzly> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 216.209.225.128 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: actually, it was there before that...can't check on when it got into the code, but 7.2.2 had it as well (heck, could have been there since 7.0.0). the only sad part is that it will take a couple hours (for at least some operating systems) for the keepalive packet to go out...would be nice to have something a bit quicker. but, at least it's something, as you say. ;-) Bryan Quoting Corey Hirschman : > As of version 7.2.4 conserver is actually using SOKEEPALIVE. This > explains that weird 2 hour behavior I was seeing. If I killed the > power > on the console server and then powered it back up, I would get no > logging for 2 hours. Then a keepalive packet would be sent to all the > connections that were marked as up. Since they were really bad > connections at that point, they would be marked as down. Conserver > would then do it's auto up and reestablish the connections. So this > pretty much takes care of polling the machines. You do lose 2 hours of > logging (unless you feel like playing with TCP), but that is better > than > it not coming up at all. > > Corey > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users >