From wernli@in2p3.fr Wed Mar 7 15:03:33 2018 Received: from cczrelay01.in2p3.fr (cczrelay01.in2p3.fr [134.158.66.141]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w27F3Sij014214 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 7 Mar 2018 15:03:32 GMT Received: from ccfawe.in2p3.fr (ccfawe.in2p3.fr [134.158.231.43]) (authenticated bits=0) by cczrelay01.in2p3.fr (8.14.4/8.14.4) with ESMTP id w27F3QaU015972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 7 Mar 2018 16:03:26 +0100 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at cczrelay01 Received: by ccfawe.in2p3.fr (Postfix, from userid 3942) id 765841B4; Thu, 8 Mar 2018 00:03:38 +0900 (JST) Date: Wed, 7 Mar 2018 16:03:38 +0100 From: Fabien Wernli To: users@conserver.com Subject: IPMI SOL and break Message-ID: <20180307150338.3wibdwikohtr6nea@ccfawe.in2p3.fr> Reply-To: wernli@in2p3.fr Mail-Followup-To: users@conserver.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: CC-IN2P3 (CNRS) User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Score: 1.49 (*) BAYES_60,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 15:03:33 -0000 Hi, Has anyone been able to successfully trigger SysRq or equivalent using a break sequence for consoles of type IPMI? Cheers From glance@acc.umu.se Wed Mar 7 15:40:21 2018 Received: from mail.acc.umu.se (mail.acc.umu.se [130.239.18.156]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w27FeFhx016172 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 7 Mar 2018 15:40:18 GMT Received: from localhost (localhost.localdomain [127.0.0.1]) by amavisd-new (Postfix) with ESMTP id 6982344BA2 for ; Wed, 7 Mar 2018 16:40:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=acc.umu.se; s=mail1; t=1520437213; bh=Ta7SVOfA35gPVhmOYYnLkuVmLiNWAf/mw0Sbz3/ILAA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=mGaPF4gZjYdaXUvPkNFGLR1dqvNfKlG5W5HrDaujf1cAA4SOTEZ4Cz8HmuEg+xNWI dIF1jjDhO702wusXSGCQhWE1exdj27Vcn39f4I3O2KO2mcJzm6MrC+6LFTBjXXpfLC 0812pbT9HZDmDKi8eroDMZZqDLqXtV+A2wiW5DEsF5m1jRsnZ+HSufP/tgG1cqSibP KYNsspJCOCA2EgRj3BheK4Zns8p4eIz2AUnEAKWd8cD0bO8QjdaXXvCdxtBQ/s3Zx5 1yCea7HoQwv3rT2Xzrae7zc55GtSy4E5fuJt2of7Y1vKlBinYYGq/hYzu+nwaSc+57 GzxMIOvvz4ogA== Received: by mail.acc.umu.se (Postfix, from userid 24471) id 8238C44BA3; Wed, 7 Mar 2018 16:40:08 +0100 (CET) Date: Wed, 7 Mar 2018 16:40:08 +0100 From: Anton Lundin To: users@conserver.com Subject: Re: IPMI SOL and break Message-ID: <20180307154008.GP7010@hirohito.acc.umu.se> References: <20180307150338.3wibdwikohtr6nea@ccfawe.in2p3.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180307150338.3wibdwikohtr6nea@ccfawe.in2p3.fr> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: 0.689 () BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, SPF_PASS, T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 15:40:21 -0000 On 07 March, 2018 - Fabien Wernli via users wrote: > Hi, > > Has anyone been able to successfully trigger SysRq or equivalent > using a break sequence for consoles of type IPMI? My configuration is older than the ipmi support in conserver, so we just exec into ipmitool. For exec ipmitool consoles, you can send a break like: break 4 { string "\r\d~\dB"; } //Anton -- Anton Lundin From wernli@in2p3.fr Wed Mar 7 15:59:22 2018 Received: from cczrelay01.in2p3.fr (cczrelay01.in2p3.fr [134.158.66.141]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w27FxJKV016633 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 7 Mar 2018 15:59:22 GMT Received: from ccfawe.in2p3.fr (ccfawe.in2p3.fr [134.158.231.43]) (authenticated bits=0) by cczrelay01.in2p3.fr (8.14.4/8.14.4) with ESMTP id w27FxGcq022029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 7 Mar 2018 16:59:16 +0100 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at cczrelay01 Received: by ccfawe.in2p3.fr (Postfix, from userid 3942) id 791371C0; Thu, 8 Mar 2018 00:59:28 +0900 (JST) Date: Wed, 7 Mar 2018 16:59:28 +0100 From: Fabien Wernli To: Anton Lundin Cc: users@conserver.com Subject: Re: Re: IPMI SOL and break Message-ID: <20180307155928.gdymirzfd55vuzx4@ccfawe.in2p3.fr> Reply-To: wernli@in2p3.fr Mail-Followup-To: Anton Lundin , users@conserver.com References: <20180307150338.3wibdwikohtr6nea@ccfawe.in2p3.fr> <20180307154008.GP7010@hirohito.acc.umu.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180307154008.GP7010@hirohito.acc.umu.se> Organization: CC-IN2P3 (CNRS) User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Score: 1.49 (*) BAYES_60,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 15:59:22 -0000 On Wed, Mar 07, 2018 at 04:40:08PM +0100, Conserver Users's Mailing List wrote: > break 4 { string "\r\d~\dB"; } yes, we used to do that too, but now conserver is linked to freeipmi. The default break sequence of freeipmi's console executable doesn't work (&) From wernli@in2p3.fr Thu Mar 8 08:33:53 2018 Received: from cczrelay02.in2p3.fr (cczrelay02.in2p3.fr [134.158.66.142]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w288Xmqm019718 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 8 Mar 2018 08:33:51 GMT Received: from ccfawe.in2p3.fr (ccfawe.in2p3.fr [134.158.231.43]) (authenticated bits=0) by cczrelay02.in2p3.fr (8.14.4/8.14.4) with ESMTP id w288Xk5t020680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 8 Mar 2018 09:33:47 +0100 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at cczrelay02 Received: by ccfawe.in2p3.fr (Postfix, from userid 3942) id 4CD34318; Thu, 8 Mar 2018 17:33:59 +0900 (JST) Date: Thu, 8 Mar 2018 09:33:59 +0100 From: Fabien Wernli To: users@conserver.com Subject: Re: IPMI SOL and break Message-ID: <20180308083359.gf55uulwxbkv4wpl@ccfawe.in2p3.fr> Reply-To: wernli@in2p3.fr Mail-Followup-To: users@conserver.com References: <20180307150338.3wibdwikohtr6nea@ccfawe.in2p3.fr> <20180307154008.GP7010@hirohito.acc.umu.se> <20180307155928.gdymirzfd55vuzx4@ccfawe.in2p3.fr> <3zxXzP2dsMzDB5k@naiad.spacehopper.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3zxXzP2dsMzDB5k@naiad.spacehopper.org> Organization: CC-IN2P3 (CNRS) User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Score: -0.011 () BAYES_40,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 08:33:53 -0000 Hi, On Thu, Mar 08, 2018 at 01:31:28AM +0000, Stuart Henderson wrote: > Hi, I'm reading on gmane and the list is read-only there so I can't > quickly reply, so sending off-list: > > conserver's default "break 0" (\z) works for me on "type ipmi" consoles. > > If it works for you could you post this back to the list for the archives > please? Thanks. Thanks Stuart, it works indeed! From bryan@stansell.org Thu Mar 22 15:24:48 2018 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id w2MFOm4G023257; Thu, 22 Mar 2018 15:24:48 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=conserver.com; s=s0001; t=1521732288; bh=i4v2WPGBM89g9ag7RYdT4lYpoPy5nDPcR7qzDu5ASx8=; h=Date:From:To:Subject; b=FEEnnVfyKKw5RnzttSar2LfFcd3Qz7KfeLWSQzxVaNIWSS83PNhCBllJn5f3905fV dTYHwWBRaBEJZcEJFt5pv9Y+7ydPotVTrO+1wAcvl4Bhh7ZZu9LCRv17uWF1YBm1Lm LxEllQixVY6b9p0++PqvhAIS68CLFFLa5c+uG9YVFwShV0EU97FeHoSt4tfR7vuMgY w9EZjaj0doh9ViH23tRo/P5yLJvNp9hisHazAOcJ2D1QSMcQFAwtmz7lypK58IkX5b B4dYTwECWuOK3XZbfXBotwnP7Ks+Uz7sdqmqUgvlf9J63Scs14jVTRhIufTBdM3j8H +7slY6T4Kajkg== Received: (from bryan@localhost) by underdog.stansell.org (8.15.2/8.15.2/Submit) id w2MFOmwT023256; Thu, 22 Mar 2018 15:24:48 GMT Date: Thu, 22 Mar 2018 15:24:48 +0000 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Subject: Embracing github.com Message-ID: <20180322152442.GA22432@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2018 15:24:48 -0000 I wanted to let everyone know that I've converted the conserver releases into a git repository and pushed it to github. You can find it here: https://github.com/conserver/conserver You can now clone, fork, submit PRs, open issues, etc just like all the other cool kids these days. ;-) I've been meaning to move things into a git repo for quite a while, but the stability of the code (aside from the one major issue with recent openssl libraries - any openssl experts out there?) has kept me from doing it. Now I'm on a "simplification" kick and looking to github to manage the lifecycle of the software. The next step will be to update docs to point at github and start accumulating any issues and patches there. And if you need to pull tarballs, that's where to go now! Thanks! Bryan Stansell From stu@spacehopper.org Fri Mar 23 08:51:56 2018 Received: from naiad.spacehopper.org (naiad.spacehopper.org [195.95.187.26]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w2N8poWJ029832 (version=TLSv1.2 cipher=ADH-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 23 Mar 2018 08:51:53 GMT Received: by naiad.spacehopper.org (Postfix, from userid 1000) id 406y2Y2JsgzDB7l; Fri, 23 Mar 2018 08:51:49 +0000 (GMT) Date: Fri, 23 Mar 2018 08:51:49 +0000 From: Stuart Henderson To: users@conserver.com Subject: Re: Embracing github.com Message-ID: <20180323085149.GA35391@naiad.spacehopper.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180322152442.GA22432@underdog.stansell.org> User-Agent: Mutt/1.9.4 (2018-02-28) X-Spam-Score: 2.275 (**) BAYES_50,FAKE_REPLY_C,SPF_PASS,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 08:51:56 -0000 On 2018-03-22, Bryan Stansell wrote: > I wanted to let everyone know that I've converted the conserver releases > into a git repository and pushed it to github. You can find it here: > > https://github.com/conserver/conserver > > You can now clone, fork, submit PRs, open issues, etc just like all the > other cool kids these days. ;-) > > I've been meaning to move things into a git repo for quite a while, but > the stability of the code (aside from the one major issue with recent > openssl libraries - any openssl experts out there?) has kept me from > doing it. Now I'm on a "simplification" kick and looking to github to > manage the lifecycle of the software. The next step will be to update > docs to point at github and start accumulating any issues and patches > there. And if you need to pull tarballs, that's where to go now! I have a request (I maintain the conserver port on OpenBSD). Would it be possible to add uploaded tarballs as "assets" to the github releases please? The automatic "source code (tar.gz)" links on the releases page are to files which are automatically generated by git-archive and then cached for an unknown time. As confirmed by a github developer in private mail they're subject to change if they update their software stack, so aren't ideal for OS packagers who verify that downloaded files haven't changed. In the past github tried to keep these a bit more stable (including locally backing out changes to software they use affecting the files) but they seem to have stopped this now, we've been seeing checksum failures quite often recently in files distributed this way (even with files downloaded at the same time, but presumably from different github clusters). The manual method is on https://help.github.com/articles/creating-releases/ (note step 7), it can be automated too - various examples of this are at https://gist.github.com/stefanbuck/ce788fee19ab6eb0b4447a85fc99f447 and https://stackoverflow.com/questions/40733692/github-upload-release-assets-with-bash To show how it looks, here are a few other projects doing this: https://github.com/libevent/libevent/releases https://github.com/jedisct1/libsodium/releases https://github.com/irssi/irssi/releases Thanks Stuart From bryan@stansell.org Sat Mar 24 01:21:43 2018 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTP id w2O1LhxQ012676; Sat, 24 Mar 2018 01:21:43 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=conserver.com; s=s0001; t=1521854503; bh=Ebol3kQUxNIvbeqcunUH3x5buZwtdVEu7PUjlGI109U=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=AyiZGYXWOjHF9sfzbvvmfyWETVMgiV6rEcJE/qOxak6fojiNkcfMz9FkcRvEsSeUn jC2SiaPT1a1p7soe+PoQA5ObX0eWe+FOg4086txHbktZ4KijOt9NCNpXNlIcN55dYk ATh0kOF2FmMnnc/VuVC5BMk1xyz/JXIh6inPVpS7OJCjLhnMNRlpdwi8e6sXxCAKN1 7BY30O/fuUrKF2gC4qjjaWcKfyAgEMC4s1BIQbyPPqfekX5mSNdw0jDp9EWJszHLPu 6eNgDCrsf5Wu1kmyFfj8WGLI12wsYHCqIp8mKwADfn3ksjHqkwoEkzlCc4mRgZWNVa e1l65X2d5Abdw== Received: (from bryan@localhost) by underdog.stansell.org (8.15.2/8.15.2/Submit) id w2O1LhYX012675; Sat, 24 Mar 2018 01:21:43 GMT Date: Sat, 24 Mar 2018 01:21:43 +0000 From: Bryan Stansell To: Stuart Henderson Cc: users@conserver.com Subject: Re: Embracing github.com Message-ID: <20180324012143.GA12462@underdog.stansell.org> References: <20180322152442.GA22432@underdog.stansell.org> <20180323085149.GA35391@naiad.spacehopper.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180323085149.GA35391@naiad.spacehopper.org> User-Agent: Mutt/1.4.2.3i X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 01:21:44 -0000 Excellent plan. Done! I've also created a PGP code signing key (not signed by anyone else, but, better than nothing), pushed it to the key servers, and signed the tarballs. It's nice to learn from the experience of others. Thanks! Bryan On Fri, Mar 23, 2018 at 08:51:49AM +0000, Stuart Henderson via users wrote: > > I have a request (I maintain the conserver port on OpenBSD). > > Would it be possible to add uploaded tarballs as "assets" to the github > releases please? > > The automatic "source code (tar.gz)" links on the releases page are to > files which are automatically generated by git-archive and then cached > for an unknown time. As confirmed by a github developer in private mail > they're subject to change if they update their software stack, so aren't > ideal for OS packagers who verify that downloaded files haven't changed. > > In the past github tried to keep these a bit more stable (including > locally backing out changes to software they use affecting the files) > but they seem to have stopped this now, we've been seeing checksum > failures quite often recently in files distributed this way (even with > files downloaded at the same time, but presumably from different github > clusters). > > The manual method is on https://help.github.com/articles/creating-releases/ > (note step 7), it can be automated too - various examples of this are at > https://gist.github.com/stefanbuck/ce788fee19ab6eb0b4447a85fc99f447 and > https://stackoverflow.com/questions/40733692/github-upload-release-assets-with-bash > > To show how it looks, here are a few other projects doing this: > > https://github.com/libevent/libevent/releases > https://github.com/jedisct1/libsodium/releases > https://github.com/irssi/irssi/releases > > Thanks > Stuart > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users From cross@distal.com Sat Mar 24 14:04:32 2018 Received: from hydra.pix.net (hydra.pix.net [71.178.232.4]) by underdog.stansell.org (8.15.2/8.15.2) with ESMTPS id w2OE4SFS005913 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 24 Mar 2018 14:04:31 GMT Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.15.2/8.15.2) with ESMTPSA id w2OE4K0K011400 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 24 Mar 2018 10:04:27 -0400 (EDT) (envelope-from cross@distal.com) Received: from westeros.distal.com (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail.distal.com (8.15.2/8.15.2) with ESMTPS id w2OE343G007228 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 24 Mar 2018 10:03:05 -0400 (EDT) (envelope-from cross@westeros.distal.com) Received: (from cross@localhost) by westeros.distal.com (8.15.2/8.15.2/Submit) id w2OE34sa007227 for users@conserver.com; Sat, 24 Mar 2018 10:03:04 -0400 (EDT) (envelope-from cross) Date: Sat, 24 Mar 2018 10:03:04 -0400 From: Chris Ross To: users@conserver.com Subject: Re: Embracing github.com Message-ID: <20180324140302.GC98610@westeros.distal.com> References: <20180322152442.GA22432@underdog.stansell.org> <20180323085149.GA35391@naiad.spacehopper.org> <20180324012143.GA12462@underdog.stansell.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180324012143.GA12462@underdog.stansell.org> User-Agent: Mutt/1.9.3 (2018-01-21) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mail.distal.com [IPv6:::1]); Sat, 24 Mar 2018 10:03:05 -0400 (EDT) X-Spam-Score: -0.001 () BAYES_40 X-Scanned-By: MIMEDefang 2.72 on 198.151.248.21 X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 14:04:33 -0000 On Sat, Mar 24, 2018 at 01:21:43AM +0000, Bryan Stansell via users wrote: > Excellent plan. Done! > > I've also created a PGP code signing key (not signed by anyone else, > but, better than nothing), pushed it to the key servers, and signed the > tarballs. > > It's nice to learn from the experience of others. Thanks! What geographic area do you live in, Bryan? I'm sure you could find friendly users of conserver to meet with you and after verifying you're you sign your PGP key. :-) If you were in the Washington DC metro area, I volunteer. - Chris