From rkirkpat@rkirkpat.net Fri Aug 26 04:08:47 2005 Received: from saratoga.rkirkpat.net (saratoga.rkirkpat.net [66.93.122.3]) by underdog.stansell.org (8.13.4/8.13.4) with ESMTP id j7QB8cX3027669 for ; Fri, 26 Aug 2005 04:08:44 -0700 (PDT) Received: from magellan.rkirkpat.net (magellan.rkirkpat.net [192.168.7.3]) by saratoga.rkirkpat.net (Postfix) with ESMTP id 826707189F for ; Fri, 26 Aug 2005 05:08:35 -0600 (MDT) Received: by magellan.rkirkpat.net (Postfix, from userid 1000) id 2181C9DE4B; Fri, 26 Aug 2005 05:08:35 -0600 (MDT) Received: from localhost (localhost [127.0.0.1]) by magellan.rkirkpat.net (Postfix) with ESMTP id 0DCBD14027 for ; Fri, 26 Aug 2005 05:08:35 -0600 (MDT) Date: Fri, 26 Aug 2005 05:08:35 -0600 (MDT) From: Ryan Kirkpatrick X-Sender: rkirkpat@magellan.rkirkpat.net To: users@conserver.com Subject: Conserver Problems: Slow Start & SSL Errors Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463811321-1281561346-1125054515=:10970" 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: Fri, 26 Aug 2005 11:08:48 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463811321-1281561346-1125054515=:10970 Content-Type: TEXT/PLAIN; charset=US-ASCII I recently setup Conserver 8.1.11 on a Debian Woody Linux system. The system has a 200MHz Pentium I processor, 96MB RAM, and 48 serial ports (3x RocketPort 8J PCI cards, 3x BocaLan BB-1008 ISA cards). This hardware used to run Debian Potato with Conserver 6.x or 7.x (don't remember). Conserver 8, for the most part, is working fine. But there are two problems I have been unable to solve: *) When I try and connect with the console client, even from the local machine, it takes 2-5 seconds for the connection to occur. This is even longer than it takes to SSH into the system in the first place. I have SSL turned off, and I have DNS resolution setup correctly. From 'top', it looks like a lot of CPU time is being used by conserver during the connection start up. The older versions of Conserver was nearly instantaneous on connection. *) More seriously, when I connect with '-A' to display the last ten lines, eight times out of ten, the last ten lines are displayed, and then console exits with the error 'console: FileRead(): SSL error on fd 3'. As I said above, I am not using SSL at all. Connections attempts without '-A' never fail. My configuration is attached (without all 48 port definitions for the sake of brevity). Does anyone have any recommendations on how to solve these problems? Conserver is excellent software, and would be perfect if I could just solve these problems. Thanks! --------------------------------------------------------------------------- | "For to me to live is Christ, and to die is gain." | | --- Philippians 1:21 (KJV) | --------------------------------------------------------------------------- | Ryan Kirkpatrick | Boulder, Colorado | http://www.rkirkpat.net/ | --------------------------------------------------------------------------- ---1463811321-1281561346-1125054515=:10970 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="conserver.cf" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="conserver.cf" IyAvZXRjL2NvbnNlcnZlci9jb25zZXJ2ZXIuY2YgOjogQ29uU2VydmVyIENv bmZpZ3VyYXRpb24NCg0KIyBDb25maWd1cmUgdGhlIHNlcnZlci4NCmNvbmZp ZyAqIHsNCiAgZGFlbW9ubW9kZSAgICB5ZXM7ICAgICAgICAjIFJ1biBhcyBh IGRhZW1vbi4NCiAgZGVmYXVsdGFjY2VzcyByZWplY3RlZDsgICAjIFVuYXV0 aG9yaXplZCBob3N0cyBkZW5pZWQgYWNjZXNzIQ0KICBzc2xyZXF1aXJlZCAg IG9mZjsgICAgICAgICMgRG8gbm90IHVzZSBTU0wuDQogIGF1dG9jb21wbGV0 ZSAgeWVzOyAgICAgICAgIyBBYmxlIHRvIHVzZSBwYXJ0aWFsIHBvcnQgbmFt ZXMuDQoNCiAgIyBMb2cgZmlsZSBmb3IgZ2VuZXJhbCBtZXNzYWdlcy4NCiAg bG9nZmlsZSAgICAgICAvdmFyL2xvZy9jb25zZXJ2ZXIvX19tYXN0ZXJfXzsN Cn0NCg0KIyBFc3RhYmxpc2ggYWNjZXNzIGNvbnRyb2wuDQphY2Nlc3MgKiB7 DQogICMgT25seSBhbGxvdyBjb25uZWN0aW9ucyBmcm9tIHRoaXMgbWFjaGlu ZS4NCiAgdHJ1c3RlZCBsb2NhbGhvc3QsY29uc29sZTsNCn0NCg0KIyBEZWZh dWx0IGNvbnNvbGUgY29uZmlndXJhdGlvbi4NCmJyZWFrIDEgeyBzdHJpbmcg Ilx6IjsgfQ0KZ3JvdXAgYWRtaW5zIHsgdXNlcnMgcm9vdDsgfQ0KZGVmYXVs dCAqIHsNCiAgbWFzdGVyICAgICAgbG9jYWxob3N0OyAgICAjIFRoaXMgbWFj aGluZSBpcyBjb25zb2xlIG1hc3Rlci4NCiAgYmF1ZCAgICAgICAgOTYwMDsg ICAgICAgICAjIFN0YW5kYXJkIGJhdWQgcmF0ZS4NCiAgYnJlYWsgICAgICAg MTsgICAgICAgICAgICAjIFN0YW5kYXJkIGJyZWFrIGlzIHNlcmlhbCBicmVh ay4NCiAgdHlwZSAgICAgICAgZGV2aWNlOyAgICAgICAjIEFsbCBjb25zb2xl cyBhcmUgc2VyaWFsIHBvcnRzLg0KICBkZXZpY2UgICAgICAvZGV2L3R0eUN4 OyAgICMgU2VyaWFsIGRldmljZSBuYW1lIHRlbXBsYXRlLg0KICBkZXZpY2Vz dWJzdCB4PXAwMmQ7ICAgICAgICMgeCBpbiBhYm92ZSBpcyBwb3J0IyBhcyAy IGRpZ2l0IGRlY2ltYWwgbnVtYmVyLg0KICBob3N0ICAgICAgICBub25lOyAg ICAgICAgICMgVHJpZ2dlciB1c2FnZSBvZiBwb3J0IyBpbiBhYm92ZSBzdWJz dGl0dXRpb24uDQoNCiAgIyBPcHRpb25zIGFyZSBubyBYT04vWE9GRiBmbG93 IGNvbnRyb2wsIHVzZSBoYXJkd2FyZSBpbnN0ZWFkLCBhbmQgdXNlDQogICMg bm8gcGFyaXR5LiBSZW1haW5kaW5nIG9wdGlvbnMgYXJlIGxlZnQgYXQgZGVm YXVsdC4NCiAgb3B0aW9ucyAgICAgIWl4b247DQogIG9wdGlvbnMgICAgICFp eGFueTsNCiAgb3B0aW9ucyAgICAgIWl4b2ZmOw0KICBvcHRpb25zICAgICBj cnRzY3RzOw0KICBwYXJpdHkgICAgICBub25lOw0KDQogICMgTG9nIGZpbGUg cGVyIHBvcnQgbmFtZSwgcm90YXRlZCBhdCAyMDBrQnl0ZXMsIGFuZCB0aW1l c3RhbXAgYWRkZWQgZXZlcnkNCiAgIyAgIDE3IG1pbnV0ZXMgb3IgdXBvbiBh Y3Rpdml0eSAoYXR0YWNoL2RldGFjaC9idW1wKSBvciBicmVhay4NCiAgbG9n ZmlsZSAgICAgL3Zhci9sb2cvY29uc2VydmVyLyY7DQogIGxvZ2ZpbGVtYXgg IDIwMGs7DQogIHRpbWVzdGFtcCAgIDE3bWFiOw0KDQogICMgRGVmYXVsdCBh Y2Nlc3MgY29udHJvbCBpcyBhZG1pbnMsIGFuZCBhZG1pbnMgb25seSwgaGF2 ZSByZWFkL3dyaXRlIGFjY2Vzcy4NCiAgcm8gIiI7DQogIHJ3IGFkbWluczsN Cn0NCg0KIyBUaGUgY29uc29sZXM6IE5hbWVzIGFyZSBieSB0aGUgaG9zdG5h bWUgb2YgdGhlIG1hY2hpbmUgY29ubmVjdGVkIHRvLCBpZiBhbnkuDQojIElm IG5vdCBjb25uZWN0ZWQgdG8gYW55IG1hY2hpbmUsIHRoZW4ganVzdCB0aGUg b2YgdGhlIGZvcm0gJ3BvcnR7bnVtfScuDQpjb25zb2xlIHN3aXRjaCAgICAg ICAgeyBwb3J0IDE7IH0NCi4uLg0K ---1463811321-1281561346-1125054515=:10970-- From bryan@stansell.org Mon Aug 29 11:49:19 2005 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.13.4/8.13.4) with ESMTP id j7TInJBh006756 for ; Mon, 29 Aug 2005 11:49:19 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.13.4/8.13.4/Submit) id j7TInJtZ006755 for users@conserver.com; Mon, 29 Aug 2005 11:49:19 -0700 (PDT) Date: Mon, 29 Aug 2005 11:49:18 -0700 From: Bryan Stansell To: users@conserver.com Subject: Re: Conserver Problems: Slow Start & SSL Errors Message-ID: <20050829184918.GG19884@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.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: Mon, 29 Aug 2005 18:49:19 -0000 On Fri, Aug 26, 2005 at 05:08:35AM -0600, Ryan Kirkpatrick wrote: > *) When I try and connect with the console client, even from the local > machine, it takes 2-5 seconds for the connection to occur. This is even > longer than it takes to SSH into the system in the first place. I have SSL > turned off, and I have DNS resolution setup correctly. From 'top', it > looks like a lot of CPU time is being used by conserver during the > connection start up. The older versions of Conserver was nearly > instantaneous on connection. actually, you probably have ssl on, but don't realize it. if you run 'conserver -V' and see openssl in the options: section, you've got it. the config you shared shows 'sslrequired: off', which just means it can allow a non-ssl client to connect, but still offers it and tries to use it. if you run 'console -E ' then you'll attempt a non-ssl connection (which should be nice and fast). you can add an 'sslenabled off;' to a .consolerc file (in a config block) if you'd like it off by default (the console manpage talks about that file). > *) More seriously, when I connect with '-A' to display the last ten lines, > eight times out of ten, the last ten lines are displayed, and then console > exits with the error 'console: FileRead(): SSL error on fd 3'. As I said > above, I am not using SSL at all. Connections attempts without '-A' never > fail. this one i can't reproduce (yet, anyway). i didn't use your config file, but, in theory, that shouldn't matter (and it would be kinda hard to since i don't have useful serial ports on my box). what version of openssl are you using? perhaps it's worth upgrading as a test? though, i haven't seen issues like this at all...so, i'm shootin' in the dark here. Bryan From rkirkpat@rkirkpat.net Tue Aug 30 07:20:46 2005 Received: from saratoga.rkirkpat.net (saratoga.rkirkpat.net [66.93.122.3]) by underdog.stansell.org (8.13.4/8.13.4) with ESMTP id j7UEKV96020237 for ; Tue, 30 Aug 2005 07:20:40 -0700 (PDT) Received: from magellan.rkirkpat.net (magellan.rkirkpat.net [192.168.7.3]) by saratoga.rkirkpat.net (Postfix) with ESMTP id 7AB01717E3 for ; Tue, 30 Aug 2005 08:20:26 -0600 (MDT) Received: by magellan.rkirkpat.net (Postfix, from userid 1000) id 330BC9DE4B; Tue, 30 Aug 2005 08:20:26 -0600 (MDT) Received: from localhost (localhost [127.0.0.1]) by magellan.rkirkpat.net (Postfix) with ESMTP id 26A6513FF2 for ; Tue, 30 Aug 2005 08:20:26 -0600 (MDT) Date: Tue, 30 Aug 2005 08:20:26 -0600 (MDT) From: Ryan Kirkpatrick X-Sender: rkirkpat@magellan.rkirkpat.net To: users@conserver.com Subject: Re: Conserver Problems: Slow Start & SSL Errors In-Reply-To: <20050829184918.GG19884@underdog.stansell.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, 30 Aug 2005 14:20:46 -0000 On Mon, 29 Aug 2005, Bryan Stansell wrote: > On Fri, Aug 26, 2005 at 05:08:35AM -0600, Ryan Kirkpatrick wrote: > > *) When I try and connect with the console client, even from the local > > machine, it takes 2-5 seconds for the connection to occur. > actually, you probably have ssl on, but don't realize it. That was it! I did not realize that the 'console' client used SSL by default, or even that SSL was compiled in (using Debian testing package backported). Once I added '-E' connections sped up greatly! Thanks! > > *) More seriously, when I connect with '-A' to display the last ten lines, > > eight times out of ten, the last ten lines are displayed, and then console > > exits with the error 'console: FileRead(): SSL error on fd 3'. > > this one i can't reproduce (yet, anyway). i didn't use your config > file, I did a bit more testing on this problem, and I can rule out OpenSSL as the cause. I recompiled conserver and console w/o OpenSSL support, and while I did not get the SSL error message on connect w/replay, it still disconnected me after the replay. Looking at the general logfile, it appears the conserver process I am connecting to is generating a 'Signal 11' when I ask for a replay. So, conserver is not just dropping the connection, but actually crashing. I looked into the log files causing a crash on replay and the ones that do not. I found the following: *) If the end of the log file contains all data from the serial port (e.g. error message from my router's console), then I can connect w/replay w/o a problem. No crashes, no sudden disconnects. *) If the end of the log file contains only log events (i.e. '^[-- .*]' lines) of MARK and console up/down messages (e.g. there has been no input from the serial port in a long time), then when I connect w/replay I am disconnected after the replay and conserver crashes. *) If the above log file has an attach AND a detach log event appended to it (either via connect w/o replay, or via manual cut'n paste), then when I connect w/replay everything works fine, no crashes, no sudden disconnects. Where, the end of the file is the last 10-20 lines. Therefore, it looks like the replay log parsing algorthim is choking on lines of only MARK and console up/down messages at the end of log files. Hopefully this helps you get closer to solving, or at least duplicating this problem. Let me know if there is anyway else I can help in solving this problem. Thanks. TTYL. --------------------------------------------------------------------------- | "For to me to live is Christ, and to die is gain." | | --- Philippians 1:21 (KJV) | --------------------------------------------------------------------------- | Ryan Kirkpatrick | Boulder, Colorado | http://www.rkirkpat.net/ | --------------------------------------------------------------------------- From bryan@stansell.org Tue Aug 30 14:58:13 2005 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.13.4/8.13.4) with ESMTP id j7ULwCFI023078 for ; Tue, 30 Aug 2005 14:58:13 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.13.4/8.13.4/Submit) id j7ULwCkh023077 for users@conserver.com; Tue, 30 Aug 2005 14:58:12 -0700 (PDT) Date: Tue, 30 Aug 2005 14:58:12 -0700 From: Bryan Stansell To: users@conserver.com Subject: Re: Conserver Problems: Slow Start & SSL Errors Message-ID: <20050830215812.GK19884@underdog.stansell.org> References: <20050829184918.GG19884@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Tue, 30 Aug 2005 21:58:14 -0000 well, i've been trying to reproduce the problem. i'm failing to find a logfile combo that'll trigger the error. would you be willing to send me a copy of your logfile (or whatever portion is necessary) so i can reproduce it on my system and track down the bug? thanks! Bryan On Tue, Aug 30, 2005 at 08:20:26AM -0600, Ryan Kirkpatrick wrote: > *) If the end of the log file contains only log events (i.e. '^[-- .*]' > lines) of MARK and console up/down messages (e.g. there has been no input > from the serial port in a long time), then when I connect w/replay I am > disconnected after the replay and conserver crashes. > > Where, the end of the file is the last 10-20 lines. Therefore, it looks > like the replay log parsing algorthim is choking on lines of only MARK and > console up/down messages at the end of log files. Hopefully this helps you > get closer to solving, or at least duplicating this problem. > > Let me know if there is anyway else I can help in solving this problem. > Thanks. TTYL.