From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id A086723510 for ; Mon, 6 May 2024 15:01:22 +0200 (CEST) Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Mon May 6 08:59:53 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1715000358; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=gUmvAZdDl/uc0EFy0Q6PP3U/uO7sFgtrKnCqsYSx89c=; b=M2JrgDFtwsVdnqQrGKfSCyMjKYJfHS3Bc0/uvu0v2B1cJlTdFK2etNK86nKybrlOKq5mm2 v1RCTQSe76QVmFnBeU79tXGQX5QZCnR5M3TTTiAKulLghJ+1WnzMuear6mfCWmsjZ3FhGw YEIAMo/RGMTnA48kJT/7py2oGqVbFdA= Received: by wopr.sciops.net (OpenSMTPD) with ESMTPSA id 8c48fc10 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for <9front@9front.org>; Mon, 6 May 2024 05:59:17 -0700 (PDT) Message-ID: Date: Mon, 06 May 2024 14:59:41 +0200 From: qwx@sciops.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: agile distributed standard-based API Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d) Reply-To: 9front@9front.org Precedence: bulk On Mon May 6 13:12:51 +0200 2024, sirjofri+ml-9front@sirjofri.de wrote: > Hello all, > > a simple reboot fixed it for me for some reason. In the end it was so borked that I couldn't even connect in any way, so I used the VPS panel to reboot it. > > According to the panel, that machine was up for about 860 days, though I have no idea about the accuracy of those numbers, and I couldn't confirm using uptime. > > Btw, the VPS panel reports a disk usage of 19GB/20GB, which wouldn't be good. I really hope that's just due to formatting. What's the best way to ask cwfs for accurate numbers? (I run a cwfs without worm). > > sirjofri It's a bad idea to run cwfs without a worm, especially in a vm. The system being "borked" isn't encouraging. Who knows what state it's in, but you can try the check commands on the cwfs console. I don't think you can get numbers on how full cache or other partitions are without a worm, but you could probably modify cwfs to find out. What VPS panel is this that would give uptime of the system or cwfs's disk usage? I imagine that the 20gb are the raw disk and that the plan9 partition is using the entire disk? As for uptime, is this the current number after you rebooted? If so it's probably how long the vm has been active. 860 days would make the system (or kernel anyway) out of date since at least late december 2021; if you updated userland in the mean time perhaps the kernel is out of sync. Have you updated, installed a new kernel and rebooted the machine before during the past several years? A lot of unknowns here. Perhaps rule out a borked cwfs first, then update. Make sure you rebuild your compilers first before anything else, or pull the binaries from the latest iso. Hope this helps, qwx