From MAILER-DAEMON Tue Feb 01 18:56:56 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nF314-0000Jv-AN for mharc-tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 18:56:55 -0500 Received: from mail.fsf.org ([2001:470:142::13]:55146) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF312-0000J4-Bj for tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 18:56:52 -0500 Received: from havoc.proulx.com ([96.88.95.61]:55574) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF310-0001LP-GN for tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 18:56:51 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 172E1C80 for ; Tue, 1 Feb 2022 16:56:48 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1643759808; bh=8zJ5aKQWwr8HKaw+a1caFP/lI1NtM5Ocv0A4NPaQA/I=; h=Date:From:To:Subject:References:In-Reply-To:From; b=GPRiU+6fUFP4hldtD0tGH+fILTAL11lTmda/T7XKE6UYQcYpasKxsm8hiGCwqK6vR L0HYxQ8DLqpzvZpYSuPtjnZ+riD7ls23ZJWqvV/lNj2mf/RkHgpxo1LRebWJEmnLes UHChJHHzbmfKioaKvIc96zauIuay+q9GaA7/Wzvg4opiWF3Xrsr+s/DbfycqSA3mNB Jy/X5mGBcwP4k62q0VJxGPLAlYGbIDmx3199falgFIB2+rDC8gqGu78/smaTDOlCuZ vyrJ5apNZS+g9vStYH5TG2cFQmm5TPsclXFSXZBwe0xKZ4CREVurb1/kU3Ukzv8oNc hVFBMCeLn1dlg== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id E64C27A019 for ; Tue, 1 Feb 2022 16:56:47 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id E42612DCA5; Tue, 1 Feb 2022 16:56:47 -0700 (MST) Date: Tue, 1 Feb 2022 16:56:47 -0700 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Update 2022-02-01 Message-ID: <20220201164322345896550@bob.proulx.com> References: <20220126084604104725783@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220126084604104725783@bob.proulx.com> Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2022 23:56:52 -0000 > * Three of the six components of subversion are working. Have all of the Subversion components running now. PASS: svn-http PASS: svn-https PASS: svn-rsync PASS: svn-ssh PASS: svn-svn PASS: svn-web Could switch svn over to the new vcs2 at any time. However due to the ssh host keys maybe being upgraded to ed25519 keys it would make it undesireable to move it back. And right now it there have been no complaints from any of the svn, hg, bzr users about ssh. Also having a separate system means a doubling of the kernel resources for networking. Honestly things have never run smoother now that git is on it's own server and the others are on their own. Therefore I am inclined to keep working through the various issues for each of the systems and switch over later when everything is ready. I started working on hg next. Made good progress through the parts of it. Got snarled up with the anonymous hg service through xinetd. Eventually figured out my mistake. Got the http & https protocols running. And now things like like this. PASS: hg-hg PASS: hg-rsync FAIL: hg-ssh PASS: hg-web I am now stuck on the hs over ssh which seems like it should be the simplest and most robust. But I am getting this error. $ hg clone ssh://rwp@hg.savannah.gnu.org/test-project remote: abort: potentially unsafe serve --stdio invocation: ['--cwd', '/srv/hg', '-R', 'test-project', 'serve', '--stdio'] abort: no suitable response from remote hg! This works over hg:// and http:// and https:// so this is really strange that it is failing when used over ssh:// instead. My web search fu is failing me. Something about the newer version of hg on the new server almost certainly. And we have already run into a CVE that was against 2.8.2 which caused us to freeze there because later versions, at that time, were broken. This might be the above problem hit again as a deja vu and until I find the old email discussion about it I won't remember the details. The old version was 2.8.2 and the new version is 4.5.3 so they cranked through a bunch of changes in OS release timeframe! Any ideas? I am going to let that sit and switch to working on bzr. And/Or I will be working on the web UI frontend. Both of those are the next priorities. Behind them are the download and audio-video server and the SQL database server. Not to mention the debbugs BTS. Or the other sourcehut system. :-) Bob From MAILER-DAEMON Tue Feb 01 19:11:28 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nF3FA-000101-0b for mharc-tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 19:11:28 -0500 Received: from mail.fsf.org ([2001:470:142::13]:55706) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF3F7-0000zh-D5 for tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 19:11:25 -0500 Received: from havoc.proulx.com ([96.88.95.61]:55950) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF3F0-0002Ru-OP for tech-volunteer-meeting@fsf.org; Tue, 01 Feb 2022 19:11:22 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 377C8490 for ; Tue, 1 Feb 2022 17:11:12 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1643760672; bh=rcrlLHV1a/iee564R42rSAF5zNKDfCJy6/BhMg1XmWM=; h=Date:From:To:Subject:From; b=qCn/b5YO86WCO0E51eOhLUFhPullzvxFXFWnoONB9QrTEdV42WuvpZv6Sdol5kEMX KWL54XldE0KENqPhWMeKwIntONw1RfCPxfLsvswbvgX0eGABnsPDSHau/vzvBvlsnk 31NKyHRohdOn2oimwQVaZ8LsLIGGpV/m4RwJUxJY8Kn1ap+VshgA4xzTAfPCGSEHA/ qA1zEoVYIz3h74nqNiepch4pgmZv4XIuGa0FdbwY0hyehbHmaKNjfwmYNel833H8yu psCIlr88IcRJXoH2L4yOSZ8wKyj/8lIR2fdtWPny6wQvcLQ0M7NrN92NVOyYiF9C5m zT6+9FNMRgVDw== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 58D227A019 for ; Tue, 1 Feb 2022 17:11:11 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 542642DCA5; Tue, 1 Feb 2022 17:11:11 -0700 (MST) Date: Tue, 1 Feb 2022 17:11:11 -0700 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Reboots Applied After Network Outage Message-ID: <20220201165652598116702@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2022 00:11:25 -0000 The network outage this morning separated the VMs from their root file systems running on the Ceph partition. For something like a little over an hour. Some systems seemed to recover better than others. Thanks to Amin Bandali to reboot vcs2 which was really broken this morning. The details look like the kernel log snippet included at the bottom of this message. Those types of failures appeared repeating from the start until the end of the network event around 9:38am US/Eastern. If any VM shows this type of problem then it's not good. It's hard to predict the state of the running processes afterward. Also some of the systems didn't have anything logged because the log directory is on the same root file system and couldn't log it. We saw something almost exactly like this January 5th. Some of the active daemons at the time were killed by it. Which isn't surprising. Things weren't happy. And all of the systems were rebooted then for the same reason of resetting everything to a known state. I suggest that all VM owners reboot their VMs in order to ensure that they have no problems. I have rebooted all of the systems I can, that's 16 systems, and they are all rebooted to a good happy state. Bob Feb 1 08:16:57 vcs2 kernel: [3513312.220439] INFO: task xfsaild/dm-0:341 blocked for more than 120 seconds. Feb 1 08:16:57 vcs2 kernel: [3513312.220443] Not tainted 4.15.0-161-generic #169+9.0trisquel9 Feb 1 08:16:57 vcs2 kernel: [3513312.220444] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Feb 1 08:16:57 vcs2 kernel: [3513312.220446] xfsaild/dm-0 D 0 341 2 0x80000000 Feb 1 08:16:57 vcs2 kernel: [3513312.220450] Call Trace: Feb 1 08:16:57 vcs2 kernel: [3513312.220509] __schedule+0x24e/0x890 Feb 1 08:16:57 vcs2 kernel: [3513312.220536] ? lock_timer_base+0x6b/0x90 Feb 1 08:16:57 vcs2 kernel: [3513312.220538] schedule+0x2c/0x80 Feb 1 08:16:57 vcs2 kernel: [3513312.220754] _xfs_log_force+0x159/0x2a0 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.220772] ? wake_up_q+0x80/0x80 Feb 1 08:16:57 vcs2 kernel: [3513312.220807] ? xfsaild+0x1b6/0x7e0 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.220841] xfs_log_force+0x2c/0x80 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.220876] xfsaild+0x1b6/0x7e0 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.220884] kthread+0x121/0x140 Feb 1 08:16:57 vcs2 kernel: [3513312.220887] ? kthread+0x121/0x140 Feb 1 08:16:57 vcs2 kernel: [3513312.220921] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.220923] ? kthread_create_worker_on_cpu+0x70/0x70 Feb 1 08:16:57 vcs2 kernel: [3513312.220926] ret_from_fork+0x22/0x40 Feb 1 08:16:57 vcs2 kernel: [3513312.220938] INFO: task monit:664 blocked for more than 120 seconds. Feb 1 08:16:57 vcs2 kernel: [3513312.220939] Not tainted 4.15.0-161-generic #169+9.0trisquel9 Feb 1 08:16:57 vcs2 kernel: [3513312.220940] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Feb 1 08:16:57 vcs2 kernel: [3513312.220941] monit D 0 664 1 0x00000000 Feb 1 08:16:57 vcs2 kernel: [3513312.220943] Call Trace: Feb 1 08:16:57 vcs2 kernel: [3513312.220947] __schedule+0x24e/0x890 Feb 1 08:16:57 vcs2 kernel: [3513312.220961] ? __filemap_fdatawrite_range+0xcf/0x100 Feb 1 08:16:57 vcs2 kernel: [3513312.220964] schedule+0x2c/0x80 Feb 1 08:16:57 vcs2 kernel: [3513312.220998] _xfs_log_force_lsn+0x2cf/0x350 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.221000] ? wake_up_q+0x80/0x80 Feb 1 08:16:57 vcs2 kernel: [3513312.221033] xfs_file_fsync+0xfd/0x230 [xfs] Feb 1 08:16:57 vcs2 kernel: [3513312.221055] vfs_fsync_range+0x51/0xb0 Feb 1 08:16:57 vcs2 kernel: [3513312.221057] do_fsync+0x3d/0x70 Feb 1 08:16:57 vcs2 kernel: [3513312.221060] SyS_fsync+0x10/0x20 Feb 1 08:16:57 vcs2 kernel: [3513312.221075] do_syscall_64+0x73/0x130 Feb 1 08:16:57 vcs2 kernel: [3513312.221077] entry_SYSCALL_64_after_hwframe+0x41/0xa6 Feb 1 08:16:57 vcs2 kernel: [3513312.221080] RIP: 0033:0x7f662e5a9bf7 Feb 1 08:16:57 vcs2 kernel: [3513312.221081] RSP: 002b:00007ffc255d2e00 EFLAGS: 00000293 ORIG_RAX: 000000000000004a Feb 1 08:16:57 vcs2 kernel: [3513312.221082] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f662e5a9bf7 Feb 1 08:16:57 vcs2 kernel: [3513312.221084] RDX: 0000000000000000 RSI: 00007ffc255d2e30 RDI: 0000000000000004 Feb 1 08:16:57 vcs2 kernel: [3513312.221085] RBP: 00007ffc255d2e30 R08: 0000000000000000 R09: 0000000000000004 Feb 1 08:16:57 vcs2 kernel: [3513312.221086] R10: 00000000fffffffc R11: 0000000000000293 R12: 00005632626b7b68 Feb 1 08:16:57 vcs2 kernel: [3513312.221087] R13: 0000000000000000 R14: 00007ffc255d2f74 R15: 0000000000000000 Feb 1 08:18:00 vcs2 kernel: [3513375.708341] nfs: server nfs1 not responding, still trying Feb 1 08:18:09 vcs2 kernel: [3513384.156205] nfs: server nfs1 not responding, still trying From MAILER-DAEMON Wed Feb 02 17:01:39 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nFNh0-0007X2-0q for mharc-tech-volunteer-meeting@fsf.org; Wed, 02 Feb 2022 17:01:34 -0500 Received: from mail.fsf.org ([2001:470:142::13]:59544) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFNgu-0007Wq-1O for tech-volunteer-meeting@fsf.org; Wed, 02 Feb 2022 17:01:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fsf.org; s=mail-fsf-org; h=In-Reply-To:From:References:To:Subject:MIME-Version:Date; bh=UfPkOtwC5anEsT+l7RM9C0ovk4OQNjJwNhK8jpJggAw=; b=nCumTkssSdSBo6q8eFO9ZITWD 7tylNcUKmbvgYpiEeTJH3xg5zBdzdFb3vbbvBJiW3Z2oxWJlrZVg8MixFiTddZqafIi0j3tzcdFwx uoOSDS3EW2+AVgo6VKeUaMoo/xdxGnHL38sAT1bWZcU7iOhpEb3Z0FqOOAhIU/ijUHOOwHi6NNNrj eRJfBeSdOIueie4mRqq6B42CcDEX9gboJ9quphtU41veiC8bdJJibP9tqT7wtYw3QhWd8NomtbW8H wxENpY5Rr/TwFJo392LylktowTi0lsAXaFomAFV6M92nzWez8y3PH3TcC0BBQAe74CFfizg9JLTBQ OrmWGS//g==; Received: from jumpgate.fsf.org ([74.94.156.211]:46566 helo=[172.16.0.64]) by mail.fsf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nFNgq-0001CP-96 for tech-volunteer-meeting@fsf.org; Wed, 02 Feb 2022 17:01:25 -0500 Message-ID: Date: Wed, 2 Feb 2022 17:01:23 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Update 2022-02-01 Content-Language: en-US To: tech-volunteer-meeting@fsf.org References: <20220126084604104725783@bob.proulx.com> <20220201164322345896550@bob.proulx.com> From: Andrew Engelbrecht In-Reply-To: <20220201164322345896550@bob.proulx.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2022 22:01:32 -0000 On 2/1/22 18:56, Bob Proulx wrote: > $ hg clone ssh://rwp@hg.savannah.gnu.org/test-project > remote: abort: potentially unsafe serve --stdio invocation: ['--cwd', '/srv/hg', '-R', 'test-project', 'serve', '--stdio'] > abort: no suitable response from remote hg! > > This works over hg:// and http:// and https:// so this is really > strange that it is failing when used over ssh:// instead. I'm not sure what the solution is, but here's a description of the error message from the hg source code: if realcmd == b'serve' and b'--stdio' in cmdargs: # We want to constrain 'hg serve --stdio' instances pretty # closely, as many shared-ssh access tools want to grant # access to run *only* 'hg -R $repo serve --stdio'. We # restrict to exactly that set of arguments, and prohibit # any repo name that starts with '--' to prevent # shenanigans wherein a user does something like pass # --debugger or --config=ui.debugger=1 as a repo # name. This used to actually run the debugger. if ( len(req.args) != 4 or req.args[0] != b'-R' or req.args[1].startswith(b'--') or req.args[2] != b'serve' or req.args[3] != b'--stdio' ): raise error.Abort( _(b'potentially unsafe serve --stdio invocation: %s') % (stringutil.pprint(req.args),) ) -- US government employee? Use CFC charity code 63210 to support us through the Combined Federal Campaign. https://cfcgiving.opm.gov/ From MAILER-DAEMON Fri Feb 04 14:47:26 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nG4YI-0006T2-Li for mharc-tech-volunteer-meeting@fsf.org; Fri, 04 Feb 2022 14:47:26 -0500 Received: from mail.fsf.org ([2001:470:142::13]:42998) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nG4YG-0006Ss-CH for tech-volunteer-meeting@fsf.org; Fri, 04 Feb 2022 14:47:24 -0500 Received: from havoc.proulx.com ([96.88.95.61]:41906) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nG4YE-0003yM-9h for tech-volunteer-meeting@fsf.org; Fri, 04 Feb 2022 14:47:23 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id D6FEC200 for ; Fri, 4 Feb 2022 12:47:19 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1644004039; bh=HUIMzSippZdXZyUfBkGhKu3ureFPijYYyiJqF4T6Su0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=c79PK2gG4LD1d2ZEEJEsoa3VxNXFXxA0mALy05V19xHF0hjwIuNOuAIJwvpKkvNFz FOceEE+uHwFRU17bhpP9Ba0HDB3014V22VKsT9ddT7Bgywt3HyU+7AC589bbpiF9Ex im3juxGfYhJvJ56qxuBpNgJur3FGfPu9GsNICdQjg+ZrwVnzZGsCkQ1j3O2fqgIJyf L9/B1g1qAdfWhU8kTrVEnQYySyRnRRsxxlNb1Y1zPUD7raf6PaLOnLH/lCzHKgSwLF VI1ylYhCi0yYBoU+iaqUJCKT/1RFLo+q7VgrxZB676H4Jx/GmZDHWP2CZPPrwXALbe RZiDgiU0gXN5A== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id AE58E96881 for ; Fri, 4 Feb 2022 12:47:19 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id A9CCC2DCA5; Fri, 4 Feb 2022 12:47:19 -0700 (MST) Date: Fri, 4 Feb 2022 12:47:19 -0700 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Re: Update 2022-02-01 Message-ID: <20220204124328146275787@bob.proulx.com> References: <20220126084604104725783@bob.proulx.com> <20220201164322345896550@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2022 19:47:24 -0000 Andrew Engelbrecht wrote: > I'm not sure what the solution is, but here's a description of the error > message from the hg source code: Thanks for finding the source of this in the source. This is tickling some vague memories of a problem we ran into years ago. It's too bad Trisquel doesn't keep an archive of historical package releases but both Debian and Ubuntu do. I think I will line up these packages with those from the Ubuntu archive and see if this change is one that went in right after the last working version we are using. It might be. There is enough other work to keep us busy before needing to address this problem directly. Have to do so eventually. But I am going to let it sit for a while and try to catch up on the other work such as bzr and MariaDB first. Pick the lower hanging fruit first. And then circle back around to this. Thanks! Bob From MAILER-DAEMON Wed Feb 16 11:52:55 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nKNXz-0000Yn-Oz for mharc-tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 11:52:55 -0500 Received: from mail.fsf.org ([2001:470:142::13]:40514) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nKNXx-0000YK-MW for tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 11:52:53 -0500 Received: from havoc.proulx.com ([96.88.95.61]:48902) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nKNXu-0005ON-1u for tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 11:52:53 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 6F6844CD for ; Wed, 16 Feb 2022 09:52:47 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1645030367; bh=e98SSMwApYcfX4S6+p0LPDFbJyqjuwRqdCZlovDrwEo=; h=Date:From:To:Subject:From; b=g+Jbn/g/bMQMKgY4sKplar+5lFLaWzecX4UdbHTb0Ed/v3b4i8+t8bk81kCRXBvIR vDMY9QJf2Av2pivhFL5HHEQ0gdJWSgnPPkuh2bH5t53XTHhJjlReVClRVQ+k/I2LAl NfO4+fLd/89hZWxC6wBbysgE7Wqh4lOQ2Bp+Is846y1BRAnuqnVx12yTMZzt/qb3MZ QpjcG5bofrlhlydZeN0gsh+gabdas2FZOLXq6/7Lr6T5WZa8QPRIwTfazGtxS/uM/Z 2iCMgNAV4ImsRUAUr4Suhl3WVoOv96nXLFqwz25TGLNUwzDO6O8Ohm2cB5sdUeHMcm JDG+uRtadrf6A== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 4360D96881 for ; Wed, 16 Feb 2022 09:52:47 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 3E7902DCA5; Wed, 16 Feb 2022 09:52:47 -0700 (MST) Date: Wed, 16 Feb 2022 09:52:47 -0700 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Forgotten ViewVC discussion 2022-02-16 Message-ID: <20220216093942517758735@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2022 16:52:53 -0000 Oh! In my summary today afterwards I realized I forgot to say that there is one ViewVC issue with subversion that is still floating around somewhat. https://savannah.nongnu.org/support/index.php?110608 error when calculating annotation data with viewvc This is working on the new system but failing on the old system. Philippe reporting the problem was happy enough to use the new "svntmp" name I provided for testing this on the new server. But I haven't really resolved the issue yet. Since moving git to the new server there have been *zero* problems with overloaded system on either side causing problems. I don't know if that is actual or just because there haven't been the same bad abuse waves coming through. But it has me wanting to drag my feet about moving subversion over. But once moved I can't really move it back due to the ssh host keys and the SHA1 deprecation issue. All anonymous services such as svn:// http:// https:// all can be moved back and forth immediately with no problem. But ssh:// has host state of host keys associated and can really only move forward. Therefore I was holding off on switching it for the moment. Therefore I am going to try to fix the error on the old system. But I would guess this error has been there for two years already and this is the first problem report on it. It can't be a heavily used feature or we should have heard about it more previously. Bob From MAILER-DAEMON Wed Feb 16 12:22:24 2022 Received: from list by lists.fsf.org with archive (Exim 4.90_1) id 1nKO0W-0002jm-83 for mharc-tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 12:22:24 -0500 Received: from mail.fsf.org ([2001:470:142::13]:42686) by lists.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nKO0V-0002ja-28 for tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 12:22:23 -0500 Received: from havoc.proulx.com ([96.88.95.61]:49784) by mail.fsf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nKO0T-0000pi-8T for tech-volunteer-meeting@fsf.org; Wed, 16 Feb 2022 12:22:22 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 4F067D25 for ; Wed, 16 Feb 2022 10:22:12 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1645032132; bh=mR/UWlJe1jdUnhHUDC+1VEHlfk+lfqjoayjpfxW7K+k=; h=Date:From:To:Subject:References:In-Reply-To:From; b=NAqJawet9DrW7PqhgjHKXIVQnUeVV/jHZRdmSzbWHeIP94auQ8shR4IAt2BtPNaSc FY+5goEJAmGl0mX654AvHvUeSl/lYhp9TP3Bd4Z0a3C5wB8Fh6boMHAQp1Ib47zwqX Pn2mHcx+kNhIELw3s4HcXVuSlDLxyR/VyO8b3QO5HJOQs7W9Z7p8OxOZbCjEZGICdJ ASef2PzUL4q7HsnCXv4ClpwRyaBqNWb5UTnvQgGy0kvTV8ULQkrnDH/qYWhCsFMIuM Bvve16idchdUQn6gPkWUGTOY1nNWeO4xWtuSpux/joIaTE7kB/ql3qC/XFWbN/4IY8 GsaWsuMfXUVRw== Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 25F2C96881 for ; Wed, 16 Feb 2022 10:22:12 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 225432DCA5; Wed, 16 Feb 2022 10:22:12 -0700 (MST) Date: Wed, 16 Feb 2022 10:22:12 -0700 From: Bob Proulx To: tech-volunteer-meeting@fsf.org Subject: Re: Update 2022-02-01 Message-ID: <20220216101255757988568@bob.proulx.com> References: <20220126084604104725783@bob.proulx.com> <20220201164322345896550@bob.proulx.com> <20220204124328146275787@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220204124328146275787@bob.proulx.com> Received-SPF: pass client-ip=96.88.95.61; envelope-from=bob@proulx.com; helo=havoc.proulx.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: tech-volunteer-meeting@fsf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2022 17:22:23 -0000 Bob Proulx wrote: > Andrew Engelbrecht wrote: > > I'm not sure what the solution is, but here's a description of the error > > message from the hg source code: > > Thanks for finding the source of this in the source. This is tickling > some vague memories of a problem we ran into years ago. It's too bad > Trisquel doesn't keep an archive of historical package releases but > both Debian and Ubuntu do. I think I will line up these packages with > those from the Ubuntu archive and see if this change is one that went > in right after the last working version we are using. It might be. Update! 09:11 rwp: deb http://oldarchive.trisquel.info/trisquel/ toutatis main 09:59 thomzane, Yay! That works! I don't need to go all of the way back to toutatis but it works for belenos which is where I need to investigate versions. 10:09 Glad it works! That gets me access to the versions needing investigation on this problem. Yay! I gave it a quick look and it's definitely related. This gets me pretty much on top of the problem. But because this makes things a bigger task I am going to postpone this until finishing the other work on bzr, frontend, MariaDB, and so forth. Bob