From marc.franquesa@l3jane.net Fri Apr 1 22:45:31 2016 Received: from chevy.l3jane.net (190.red-2-139-187.staticip.rima-tde.net [2.139.187.190]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id u31MjShG021780 for ; Fri, 1 Apr 2016 22:45:30 GMT Received: from [172.31.109.179] (slide.l3jane.net [172.31.109.179]) (Authenticated sender: mark) by chevy.l3jane.net (Postfix) with ESMTPSA id DEC9D85E for ; Sat, 2 Apr 2016 00:45:26 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 chevy.l3jane.net DEC9D85E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=l3jane.net; s=mail; t=1459550726; bh=AWa4+bDaxAAWVKF1xNPKwfwZPAa1uXyvfu3vaU8y8Ks=; h=Subject:From:Reply-To:To:Date:From; b=Grbv4KeZYmbF0wiW/uaC/h8JOekNKJVmfwZgp0rWSN1GIj+MW3O/yIqFVGxXLKg34 ANR8Rxxiy9tLLJc4Gg76uLydfXOB3z6Haa8UJc9PbGbtVEfQX9IrPKoppUCJn3Z6uy CFdN9MLj7XGQ5DvbF1AGnOFzbdI8TzITFwMhbvq8= Message-ID: <1459550726.8338.4.camel@slide> Subject: FTDI Consoles appear down From: Marc Franquesa Reply-To: mark@l3jane.net To: users@conserver.com Date: Sat, 02 Apr 2016 00:45:26 +0200 Organization: Lady 3Jane Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.001 () BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, SPF_PASS X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 22:45:31 -0000 Hi all After trashing with some traditional console servers (old refurbished cyclades), I discovered conserver and give it a try to test it as a replacment. Good software, almost everything I need and easy to access, so I started to migrate my serial connections to conserver to finally power down the cyclades and have a quite silent room ;) Although I'm having some console issues, some consoles are considered 'down' while they're not. If I launch minicom (also tried screen) directly to the serial port it works perfectly. I'm not using any special configuration for any serial port (either on minicom or conserver) a part from de baudrate. After some tests and tried new devices/serial, identified that the the consoles that are shown as 'down', all are based on FTDI chip, while the ones that work are based on the Prolific PL2302 chip. As all the 'down' FTDI devices work with minicom (but not with conserver) I supose is due some obscure setting or some check that does conserver that makes it consider them down although they are not. So what can I try? How conserver decides a console is down? Is there any special setting required for FTDI? or how can I check what is doing minicom that doens't do conserver to open the serial port? Thanks much From cfowler@outpostsentinel.com Sat Apr 2 00:02:12 2016 Received: from zcs-mta.vps-host.net (abairportauthority.com [69.89.1.77] (may be forged)) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id u32029QZ027056 (version=TLSv1.2 cipher=ADH-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 2 Apr 2016 00:02:11 GMT Received: from localhost (localhost [127.0.0.1]) by zcs-mta.vps-host.net (Postfix) with ESMTP id 4B82A813FD61; Fri, 1 Apr 2016 20:02:08 -0400 (EDT) Received: from zcs-mta.vps-host.net ([127.0.0.1]) by localhost (zcs-mta.vps-host.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id WuZA2eybjczk; Fri, 1 Apr 2016 20:02:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs-mta.vps-host.net (Postfix) with ESMTP id A1AE08177715; Fri, 1 Apr 2016 20:02:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs-mta.vps-host.net Received: from zcs-mta.vps-host.net ([127.0.0.1]) by localhost (zcs-mta.vps-host.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id QRM7aDp7ee3K; Fri, 1 Apr 2016 20:02:05 -0400 (EDT) Received: from enterprisemail2.vps-host.net (enterprisemail2.vps-host.net [10.0.6.109]) by zcs-mta.vps-host.net (Postfix) with ESMTP id 8145B813FD61; Fri, 1 Apr 2016 20:02:05 -0400 (EDT) Date: Fri, 1 Apr 2016 20:02:05 -0400 (EDT) From: Chris Fowler To: mark@l3jane.net Cc: users@conserver.com Message-ID: <1334129913.16169088.1459555325334.JavaMail.zimbra@outpostsentinel.com> In-Reply-To: <1459550726.8338.4.camel@slide> References: <1459550726.8338.4.camel@slide> Subject: Re: FTDI Consoles appear down MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16169087_320121555.1459555325333" X-Mailer: Zimbra 8.6.0_GA_1178 (ZimbraWebClient - GC49 (Linux)/8.6.0_GA_1178) Thread-Topic: FTDI Consoles appear down Thread-Index: 1UuGSQekFpGCzbyKJCoSZAr0UtHE1A== X-Spam-Score: 0.516 () BAYES_00, HTML_MESSAGE, RDNS_NONE, SPF_HELO_PASS, URIBL_SBL X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 00:02:12 -0000 ------=_Part_16169087_320121555.1459555325333 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Is conserver using DCD as a method? This is how I detect cable disconnects in 7.2.X. > From: "Marc Franquesa via users" > To: users@conserver.com > Sent: Friday, April 1, 2016 6:45:26 PM > Subject: FTDI Consoles appear down > Hi all > After trashing with some traditional console servers (old refurbished > cyclades), I discovered conserver and give it a try to test it as a > replacment. > Good software, almost everything I need and easy to access, so I started > to migrate my serial connections to conserver to finally power down the > cyclades and have a quite silent room ;) > Although I'm having some console issues, some consoles are considered > 'down' while they're not. If I launch minicom (also tried screen) > directly to the serial port it works perfectly. I'm not using any > special configuration for any serial port (either on minicom or > conserver) a part from de baudrate. > After some tests and tried new devices/serial, identified that the the > consoles that are shown as 'down', all are based on FTDI chip, while the > ones that work are based on the Prolific PL2302 chip. > As all the 'down' FTDI devices work with minicom (but not with > conserver) I supose is due some obscure setting or some check that does > conserver that makes it consider them down although they are not. > So what can I try? How conserver decides a console is down? Is there any > special setting required for FTDI? or how can I check what is doing > minicom that doens't do conserver to open the serial port? > Thanks much > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users ------=_Part_16169087_320121555.1459555325333 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Is conserver using DCD as a method? This is= how I detect cable disconnects in 7.2.X.



From: "= Marc Franquesa via users" <users@conserver.com>
To: users@c= onserver.com
Sent: Friday, April 1, 2016 6:45:26 PM
Subject= : FTDI Consoles appear down
Hi all

After trashing with some traditional console s= ervers (old refurbished
cyclades), I discovered conserver and give it a = try to test it as a
replacment.

Good software, almost everything = I need and easy to access, so I started
to migrate my serial connections= to conserver to finally power down the
cyclades and have a quite silent= room ;)

Although I'm having some console issues, some consoles are = considered
'down' while they're not. If I launch minicom (also tried scr= een)
directly to the serial port it works perfectly. I'm not using anyspecial configuration for any serial port (either on minicom or
conser= ver) a part from de baudrate.

After some tests and tried new devices= /serial, identified that the the
consoles that are shown as 'down', all = are based on FTDI chip, while the
ones that work are based on the Prolif= ic PL2302 chip.

As all the 'down' FTDI devices work with minicom (bu= t not with
conserver) I supose is due some obscure setting or some check= that does
conserver that makes it consider them down although they are = not.

So what can I try? How conserver decides a console is down? Is = there any
special setting required for FTDI? or how can I check what is = doing
minicom that doens't do conserver to open the serial port?

= Thanks much


_______________________________________________
u= sers mailing list
users@conserver.com
https://www.conserver.com/mailm= an/listinfo/users
------=_Part_16169087_320121555.1459555325333-- From john@stoffel.org Sat Apr 2 00:16:51 2016 Received: from mailrelay.lanline.com (mailrelay.lanline.com [216.187.10.16]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id u320GmFO028351 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 2 Apr 2016 00:16:50 GMT Received: from mycroft.westnet.com (Mycroft.westnet.com [216.187.52.7]) by mailrelay.lanline.com (8.14.5/8.14.5) with ESMTP id u320CvOm045176; Fri, 1 Apr 2016 20:12:57 -0400 (EDT) (envelope-from john@stoffel.org) Received: from quad.stoffel.org (66-189-26-192.dhcp.oxfr.ma.charter.com [66.189.26.192]) (authenticated bits=0) by mycroft.westnet.com (8.14.4/8.14.4) with ESMTP id u31NvOD5028238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Apr 2016 19:57:24 -0400 (EDT) Received: by quad.stoffel.org (Postfix, from userid 1000) id D748AAB1C1; Fri, 1 Apr 2016 20:16:45 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <22271.3949.846873.790880@quad.stoffel.home> Date: Fri, 1 Apr 2016 20:16:45 -0400 From: "John Stoffel" To: mark@l3jane.net Cc: users@conserver.com Subject: Re: FTDI Consoles appear down In-Reply-To: <1459550726.8338.4.camel@slide> References: <1459550726.8338.4.camel@slide> X-Mailer: VM 8.2.0b under 24.4.1 (x86_64-pc-linux-gnu) X-Virus-Scanned: clamav-milter 0.98.1 at mycroft X-Virus-Status: Clean X-Spam-Score: -1.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 00:16:51 -0000 Can you share your configuration for your serial ports? Esp the FTDI ones? I suspect you just need to tweak the settings a bit, but it's hard to make suggestions until we see what you're using. You can also look in the conserver archives for some hints. I found one that *might* be useful: console ttyb { type device; device /dev/term/b; protocol raw; baud 9600; parity odd; options cstopb; } But it gives you the idea... maybe. From bryan@conserver.com Sat Apr 2 05:08:55 2016 Received: from [192.168.0.204] (c-98-207-6-47.hsd1.ca.comcast.net [98.207.6.47]) (authenticated bits=0) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPSA id u3258sJk013949 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 2 Apr 2016 05:08:55 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=conserver.com; s=s0001; t=1459573735; bh=Z8PHVYsLtu27xiFyyw80Uf3MXAz2Kph8F+BDg0ovo5A=; h=From:Subject:Date:References:In-Reply-To:To; b=FYiIKzp7fagqoSBZzvWAOS6uwmSVZFa3V+xaMWXGtgdtxOT9XoVzoVVyLGIl2j6jq dm3Pfiy0xxQNgJgCU6aXg640AH0irdX2BG3R8/M77LtD6JTp+xNxfCEMIXAjeBMwoZ jVFL9hdfoegubblgFXER4Y7b1RbdLUw0BgioHP99Z8De7LyzBaR6uL4r5peJuNarKr dP6efEHMsDl1rXf3s6R3Gl21Dz3CMrlB/Z5X6IBpP4Zn8RDMd+qd0dk0+LtltmWeia JZuXPXWnO31OkyRMZFdwQABogTa8+aQwWRQv8THx9a0emJso9K+DdMaJ3Q1Dgf1kPO /TcUiGEqOviZg== From: Bryan Stansell Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: FTDI Consoles appear down Message-Id: Date: Fri, 1 Apr 2016 22:08:54 -0700 References: <1459550726.8338.4.camel@slide> <22271.3949.846873.790880@quad.stoffel.home> In-Reply-To: <22271.3949.846873.790880@quad.stoffel.home> To: users@conserver.com X-Mailer: iPhone Mail (13E233) X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by underdog.stansell.org id u3258sJk013949 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 05:08:55 -0000 Conserver doesn't do anything with carrier detect and such (for better or worse). A lot of times, however, there is both a "tty" device and "cu" device created for serial ports (maybe always on UNIX-type systems, not 100% sure). If you're using the tty device, switching to the cu device might successfully bypass a carrier detect-type issue. Just a random thought. As was said already, more specifics to the list might help. Bryan From cfowler@outpostsentinel.com Sat Apr 2 12:16:01 2016 Received: from zcs-mta.vps-host.net (abairportauthority.com [69.89.1.77] (may be forged)) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id u32CFvCV016228 (version=TLSv1.2 cipher=ADH-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 2 Apr 2016 12:16:00 GMT Received: from localhost (localhost [127.0.0.1]) by zcs-mta.vps-host.net (Postfix) with ESMTP id ED3C5813C501; Sat, 2 Apr 2016 08:15:54 -0400 (EDT) Received: from zcs-mta.vps-host.net ([127.0.0.1]) by localhost (zcs-mta.vps-host.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 4zfm8VBfSmrO; Sat, 2 Apr 2016 08:15:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs-mta.vps-host.net (Postfix) with ESMTP id C9AE9813F509; Sat, 2 Apr 2016 08:15:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs-mta.vps-host.net Received: from zcs-mta.vps-host.net ([127.0.0.1]) by localhost (zcs-mta.vps-host.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yv031IMfQMgE; Sat, 2 Apr 2016 08:15:52 -0400 (EDT) Received: from enterprisemail2.vps-host.net (enterprisemail2.vps-host.net [10.0.6.109]) by zcs-mta.vps-host.net (Postfix) with ESMTP id A7433813F031; Sat, 2 Apr 2016 08:15:52 -0400 (EDT) Date: Sat, 2 Apr 2016 08:15:52 -0400 (EDT) From: Chris Fowler To: Bryan Stansell Cc: users@conserver.com Message-ID: <758451913.16229124.1459599352312.JavaMail.zimbra@outpostsentinel.com> In-Reply-To: References: <1459550726.8338.4.camel@slide> <22271.3949.846873.790880@quad.stoffel.home> Subject: Re: FTDI Consoles appear down MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16229123_1179204689.1459599352311" X-Mailer: Zimbra 8.6.0_GA_1178 (ZimbraWebClient - GC49 (Linux)/8.6.0_GA_1178) Thread-Topic: FTDI Consoles appear down Thread-Index: xj2TSvLFC9BzfjZm/2K4/wNeuKeJIQ== X-Spam-Score: 0.516 () BAYES_00, HTML_MESSAGE, RDNS_NONE, SPF_HELO_PASS, URIBL_SBL X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 12:16:01 -0000 ------=_Part_16229123_1179204689.1459599352311 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit > From: "Bryan Stansell via users" > To: users@conserver.com > Sent: Saturday, April 2, 2016 1:08:54 AM > Subject: Re: FTDI Consoles appear down > Conserver doesn't do anything with carrier detect and such (for better or > worse). A lot of times, however, there is both a "tty" device and "cu" device > created for serial ports (maybe always on UNIX-type systems, not 100% sure). If > you're using the tty device, switching to the cu device might successfully > bypass a carrier detect-type issue. Just a random thought. I probably modded my version for -CLOCAL. ------=_Part_16229123_1179204689.1459599352311 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


From: "Br= yan Stansell via users" <users@conserver.com>
To: users@con= server.com
Sent: Saturday, April 2, 2016 1:08:54 AM
Subject= : Re: FTDI Consoles appear down
Conserver doesn't do anything with carrier detect and s= uch (for better or worse). A lot of times, however, there is both a "tty" d= evice and "cu" device created for serial ports (maybe always on UNIX-type s= ystems, not 100% sure). If you're using the tty device, switching to the cu= device might successfully bypass a carrier detect-type issue. Just a rando= m thought.


I probably modded my ve= rsion for -CLOCAL.  
------=_Part_16229123_1179204689.1459599352311-- From marc.franquesa@l3jane.net Sat Apr 2 22:07:44 2016 Received: from chevy.l3jane.net (190.red-2-139-187.staticip.rima-tde.net [2.139.187.190]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id u32M7fGR002523 for ; Sat, 2 Apr 2016 22:07:43 GMT Received: from [172.31.109.188] (rydell.l3jane.net [172.31.109.188]) (Authenticated sender: mark) by chevy.l3jane.net (Postfix) with ESMTPSA id 2574AAB for ; Sun, 3 Apr 2016 00:07:39 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 chevy.l3jane.net 2574AAB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=l3jane.net; s=mail; t=1459634859; bh=PO79CUZBhh/v8mK6JocWadcpmyefKzkDuRDLeakKLag=; h=Subject:From:Reply-To:To:Date:In-Reply-To:References:From; b=EIVA7khLsCkRdt84UoAhip1+6dvjbYZ6MrJ303a0FPiZhxU8NX2QgrfUhwMpRg7UT 5a4hLDkmPmGj+Aahs2mIFL2B6D5MFpr8g23u3RaojKGdkbifLpFmASXiSdohA31Goz 1nQF0JxSnqAob6bXA9SNVNL83mEa9sg1AZz0Lgv8= Message-ID: <1459634859.3952.14.camel@rydell> Subject: Re: FTDI Consoles appear down From: Marc Franquesa Reply-To: mark@l3jane.net To: users@conserver.com Date: Sun, 03 Apr 2016 00:07:39 +0200 In-Reply-To: <22271.3949.846873.790880@quad.stoffel.home> References: <1459550726.8338.4.camel@slide> <22271.3949.846873.790880@quad.stoffel.home> Organization: Lady 3Jane Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.001 () BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, SPF_PASS X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2016 22:07:44 -0000 On vie, 2016-04-01 at 20:16 -0400, John Stoffel wrote: > Can you share your configuration for your serial ports? Esp the FTDI > ones? I suspect you just need to tweak the settings a bit, but it's > hard to make suggestions until we see what you're using. Sure, here is my configuration (with some added comments for clarification): config * { primaryport 3109; defaultaccess rejected; logfile /srv/con-buffer/local-server.log; } default * { timestamp 1hab; baud 115200; parity none; logfile /srv/con-buffer/con-&.log; logfilemax 2m; motd "----- Out-Of-Band Management Console Server -----"; options unloved; rw *; master localhost; protocol raw; } # This console doesn't work (it shows as down) console plug { aliases ender; device /dev/serial/by-id/usb-FTDI_SheevaPlug_JTAGKey_FT2232D_B_FTVB6MLG-if01-port0; master localhost; type device; } # This one works console cubie { aliases wigan; device /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.3:1.0-port0; master localhost; type device; } # This is a RaspberryPi, it works console pi2 { aliases mona; device /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.4:1.0-port0; master localhost; type device; } # Router, it doesn't work console mikrotik { aliases ax-ginza; baud 115200; device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AI0388XH-if00-port0; master localhost; type device; } > You can also look in the conserver archives for some hints. I found > one that *might* be useful: > > console ttyb { > type device; > device /dev/term/b; > protocol raw; > baud 9600; > parity odd; > options cstopb; > } This configuration shouldn't work for me, I need no parity, a 1 stop bit. As addtiional info (also for the rest of replies which I'm very grateful for), some facts: - None of the devices is a 'real/pure' serial (RS232), all are USB serial devices based on Prolific PL232 or FTDI2232 variants. - Maybe (not sure of this) this is the reason I have not 'cu' device (in reference to the reply given by Bryan Stansell - For the same fact I think they didn't implement any DCD, CTS, or any other serial feature. I think they simply work as 'null-modem' RxTx >From my point of view, the most important fact is that with a very basic (simply configured speed, no parity, 8bit, 1stop) configuration for minicom and conserver, one works and the other don't, so I think more about some pre-check conserver is doing that minicom not. In reference to the comment by Chris Fowler, I don't know if conserver is using DCD, didn't found any thing in the configuration neither the documentation. Thanks much for feedback and the quick responses. Regards From john@stoffel.org Sun Apr 3 01:17:18 2016 Received: from mailrelay.lanline.com (mailrelay.lanline.com [216.187.10.16]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id u331HFTN019003 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 3 Apr 2016 01:17:17 GMT Received: from mycroft.westnet.com (Mycroft.westnet.com [216.187.52.7]) by mailrelay.lanline.com (8.14.5/8.14.5) with ESMTP id u331DN2b057771; Sat, 2 Apr 2016 21:13:23 -0400 (EDT) (envelope-from john@stoffel.org) Received: from quad.stoffel.org (66-189-26-192.dhcp.oxfr.ma.charter.com [66.189.26.192]) (authenticated bits=0) by mycroft.westnet.com (8.14.4/8.14.4) with ESMTP id u330vhp3011414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Apr 2016 20:57:44 -0400 (EDT) Received: by quad.stoffel.org (Postfix, from userid 1000) id 89C99AB1D0; Sat, 2 Apr 2016 21:17:11 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <22272.28439.522190.368826@quad.stoffel.home> Date: Sat, 2 Apr 2016 21:17:11 -0400 From: "John Stoffel" To: mark@l3jane.net Cc: users@conserver.com Subject: Re: FTDI Consoles appear down In-Reply-To: <1459634859.3952.14.camel@rydell> References: <1459550726.8338.4.camel@slide> <22271.3949.846873.790880@quad.stoffel.home> <1459634859.3952.14.camel@rydell> X-Mailer: VM 8.2.0b under 24.4.1 (x86_64-pc-linux-gnu) X-Virus-Scanned: clamav-milter 0.98.1 at mycroft X-Virus-Status: Clean X-Spam-Score: -1.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 01:17:18 -0000 So have you tried just bringing the console up with the ^Eco command? Does that work? Have you tried printing out the status of the port when using minicom? You might try starting up 'console' with the -v option to get more info. And also turning on the debugging output. Does the log file have any output? John From marc.franquesa@l3jane.net Mon Apr 4 16:01:19 2016 Received: from chevy.l3jane.net (190.Red-2-139-187.staticIP.rima-tde.net [2.139.187.190]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id u34G1Fqr026867 for ; Mon, 4 Apr 2016 16:01:17 GMT Received: from www.l3jane.net (wigan.l3jane.net [172.31.108.132]) (Authenticated sender: mark) by chevy.l3jane.net (Postfix) with ESMTPSA id F3F92856; Mon, 4 Apr 2016 18:01:11 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 chevy.l3jane.net F3F92856 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=l3jane.net; s=mail; t=1459785672; bh=NrZGk9yuysZ/L0IlGJn3TWZCfbEcYzUe/EiYa5FJeYk=; h=Date:From:Subject:To:Cc:In-Reply-To:References:From; b=GKna14a6MwJ/8MAdC+8WA+9wEBDs5JgxAuzB8uEaVeDGb2Aq+aIg15EQhhYbucn5N QkIqYjya+wB+0HDNCVGKunU+IbLdPJe3lBTljTcnbdb1hymZMsGaIRXwKMzW9KtRa5 Ywr9mFnzm0IGaJGW86TeN7TpeKvGO8sLCFAxages= Mime-Version: 1.0 Date: Mon, 04 Apr 2016 16:01:11 +0000 Content-Type: text/plain; charset="utf-8" Message-ID: <1a7ee7ce856453bed0f2ef9ba2732cc0@www.l3jane.net> X-Mailer: RainLoop/1.8.2.291 From: mark@l3jane.net Subject: Re: FTDI Consoles appear down To: "John Stoffel" Cc: users@conserver.com In-Reply-To: <22272.28439.522190.368826@quad.stoffel.home> References: <22272.28439.522190.368826@quad.stoffel.home> <1459550726.8338.4.camel@slide> <22271.3949.846873.790880@quad.stoffel.home> <1459634859.3952.14.camel@rydell> X-Spam-Score: -2.001 () BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, SPF_PASS X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by underdog.stansell.org id u34G1Fqr026867 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 16:01:19 -0000 Hi, Finally worked!, I'm quite sorry as finally was due a permissions problem: When I tried to launch the conserver daemon with debug enabled I've seen that all prior non-working consoles shown now as Up. After supicious checks I realized that I was 'debugging' conserver as root user (instead of the usual 'conservr' user), so I checked and: crw-rw-r-- 1 root plugdev 188, 3 Apr 4 16:48 /dev/serial/by-id/usb-FTDI_SheevaPlug_JTAGKey_FT2232D_B_FTVB6MLG-if01-port0 crw-rw---- 1 root dialout 188, 6 Mar 17 16:11 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.3:1.0-port0 crw-rw---- 1 root dialout 188, 9 Apr 4 17:30 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.4:1.0-port0 crw-rw---- 1 root dialout 188, 7 Apr 4 17:29 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.1:1.0-port0 crw-rw---- 1 root dialout 188, 8 Mar 17 15:18 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.3:1.0-port0 crw-rw-r-- 1 root plugdev 188, 5 Apr 4 17:42 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AI0388XH-if00-port0 crw-rw-r-- 1 root plugdev 188, 4 Apr 4 17:42 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00LUS9-if00-port0 ~# id conservr uid=111(conservr) gid=20(dialout) groups=20(dialout) The fact that it only happened with FTDI devices made me, erroneoulsy, suspect of HW/driver/serial issue. Although really was due the fact the FTDI devices are configured in conserver.cf by dev ID while the rest by path, and some udev rules (which give dialup permissions) didn't worked over them. Yes, novice mistake. Big mistake from my side. I'm very sorry for the time, but thanks for the hints which although pointing to some other reasons, allowed me to find my error. Thanks All From marc.franquesa@l3jane.net Thu Apr 21 11:08:21 2016 Received: from chevy.l3jane.net (190.red-2-139-187.staticip.rima-tde.net [2.139.187.190]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id u3LB8HQa010624 for ; Thu, 21 Apr 2016 11:08:20 GMT Received: from [172.31.109.188] (rydell.l3jane.net [172.31.109.188]) (Authenticated sender: mark) by chevy.l3jane.net (Postfix) with ESMTPSA id CCBFA20F for ; Thu, 21 Apr 2016 13:08:15 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.9.2 chevy.l3jane.net CCBFA20F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=l3jane.net; s=mail; t=1461236895; bh=RHd1A/+HjQFBa3lcYEjGksLrONd9VgOwN42wh91LzrI=; h=Subject:From:Reply-To:To:Date:In-Reply-To:References:From; b=I9FAawlvsj3DH+L0DF5JlYBAzyy3mboQVym3zHe5LeC19Ao5DbPq4sEMF30DwT6jG gbKIWa7oBnFhTXZhX1t3If/TwJXYW9NCrW13U91uAS3XtClLFZ5O335/Mm6aos8G1Q 9ERv3GfXdYXFtj63I4cEjj2cVpksCiWzp7LRVfVg= Message-ID: <1461236895.26852.2.camel@rydell> Subject: Re: FTDI Consoles appear down From: Marc Franquesa Reply-To: mark@l3jane.net To: users@conserver.com Date: Thu, 21 Apr 2016 13:08:15 +0200 In-Reply-To: <1459550726.8338.4.camel@slide> References: <1459550726.8338.4.camel@slide> Organization: Lady 3Jane Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.001 () BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, SPF_PASS X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 11:08:21 -0000 As a matter of more information, after finding that conserver user didn't have permissions over the serials in question, found that all worked except for one. The scenario was almost the same: it worked with minicom but not with conserver. After some 'debugging' found that conserver didn't have permissions over the logfile for that console ;). Thanks all for the help From john@stoffel.org Thu Apr 21 15:27:26 2016 Received: from mailrelay3.lanline.com (mailrelay3.lanline.com [216.187.10.24]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id u3LFRN47020589 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Apr 2016 15:27:26 GMT Received: from mycroft.westnet.com (Mycroft.westnet.com [216.187.52.7]) by mailrelay3.lanline.com (8.14.5/8.14.5) with ESMTP id u3LFMujc016810; Thu, 21 Apr 2016 11:22:56 -0400 (EDT) (envelope-from john@stoffel.org) Received: from quad.stoffel.org (66-189-26-192.dhcp.oxfr.ma.charter.com [66.189.26.192]) (authenticated bits=0) by mycroft.westnet.com (8.14.4/8.14.4) with ESMTP id u3LF66ic026974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2016 11:06:07 -0400 (EDT) Received: by quad.stoffel.org (Postfix, from userid 1000) id 8C216AB2CD; Thu, 21 Apr 2016 11:27:20 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <22296.61784.538538.138631@quad.stoffel.home> Date: Thu, 21 Apr 2016 11:27:20 -0400 From: "John Stoffel" To: mark@l3jane.net Cc: users@conserver.com Subject: Re: FTDI Consoles appear down In-Reply-To: <1461236895.26852.2.camel@rydell> References: <1459550726.8338.4.camel@slide> <1461236895.26852.2.camel@rydell> X-Mailer: VM 8.2.0b under 24.4.1 (x86_64-pc-linux-gnu) X-Virus-Scanned: clamav-milter 0.98.1 at mycroft X-Virus-Status: Clean X-Spam-Score: -0.277 () BAYES_00,URIBL_SBL X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 15:27:27 -0000 >>>>> "Marc" == Marc Franquesa via users writes: Marc> As a matter of more information, after finding that conserver user Marc> didn't have permissions over the serials in question, found that all Marc> worked except for one. Marc> The scenario was almost the same: it worked with minicom but not with Marc> conserver. Marc> After some 'debugging' found that conserver didn't have permissions over Marc> the logfile for that console ;). Sounds like conserver could use some better error logging in those cases to help find the problems. From tm@fwt.fr Fri Apr 29 09:51:03 2016 Received: from mta.92320.com (mta.92320.com [149.202.10.7]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id u3T9p1gU014574 for ; Fri, 29 Apr 2016 09:51:03 GMT Received: from Vostro3560tmu (vpn.ntrippilot.com [149.202.10.12]) by mta.92320.com (Postfix) with ESMTPSA id 51BC460365 for ; Fri, 29 Apr 2016 11:51:01 +0200 (CEST) From: "Thierry Museux - www.fwt.fr" To: Subject: concole help message Date: Fri, 29 Apr 2016 11:51:00 +0200 Message-ID: <057701d1a1fc$a34fc6c0$e9ef5440$@fwt.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdGh/AWxgEU8aRy1TAKL5Kc1rXwgig== Content-Language: fr X-Antivirus: avast! (VPS 160428-2, 28/04/2016), Outbound message X-Antivirus-Status: Clean X-Spam-Score: -1.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 09:51:03 -0000 How to suppress the starting help message: console mystream [Enter `^Ec?' for help] Or [Enter `^Ec?' for help] [spying] -- Tmu --