Re: [9front] AUTHENTICATE failed can't get challenge (imap4d)

[qwx@sciops.net]

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