[10:10:51]
<bipseb> quelqu'un as t-il une idée ?
[10:10:51]
<bipseb> j'ai toujours "invlid user name" affiché
[10:10:51]
<bipseb> j'ai un soucis avec automad, je n'arrive pas à me loger sur le dashboard
[10:10:52]
<bipseb> j'ai toujours "invlid user name" affiché
[10:10:52]
<bipseb> j'ai un soucis avec automad, je n'arrive pas à me loger sur le dashboard
[10:10:53]
<bipseb> quelqu'un as t-il une idée ?
[10:12:01]
<bipseb> merci d'avance
[10:20:45]
<bipseb> je precise que j'ai installé depuis l'outil d'administration de yunohost
[10:32:28]
<bipseb> quelqu'un à une idée pour faire marcher automad
[10:32:28]
<bipseb> desolé je me suis deconnecté
[10:37:20]
<tituspijean> bipsebtu as dû recevoir un email sur ton adresse root@tondomaine.tld avec les identifiants de l'admin
[10:37:48]
<tituspijean> si tu ne sais pas comment voir ces emails, installe l'app Snappymail sur ton serveur
[14:05:56]
<ynhuser> Je besoin d'aide pour installer Odoo
[14:06:49]
<ynhuser> à chaque fois que j'essaye de l'installer. J'ai un erreur au final et installation echoué
[14:36:23]
<bionick> Hi, I'm trying to register to the forum, but the activation email never arrives, checked the spam folder, changed email address ... nothing works. I need to reset a domain. Any advice?
[14:38:04]
<tituspijean> Hello, it might be an issue with our server configuration. I will try to investigate within the next 6 hours and ping here. Sorry for the inconvenience.
[14:38:18]
<tituspijean> *ping you here
[14:38:26]
<bionick> Thank you
[15:04:50]
<wzt> Hi
[20:22:43]
<tituspijean> bionick fixed, sorry for the inconvenience again 🙂
[20:23:23]
<tituspijean> > within the next 6 hours
Well that was unexpectedly accurate.
[20:38:33]
<Nick_> Thank you! (this is another nick-name)
[21:01:08]
<bormay[m]> does anyone know spectre meltdown checker? Does yunohost run this script?
[21:07:35]
<tituspijean> it does not
[21:08:12]
<bormay[m]> my vps crashes sometimes and the last thing which is run is this script
[21:08:22]
<bormay[m]> and I get this error - msr: Write to unrecognized MSR 0x49 by perl
[21:09:15]
<tituspijean> mmmh actually we might be running it? sorry... https://forum.yunohost.org/t/new-and-updated-install-still-shows-i-have-a-meltdown-vulnerability/13960/2?u=tituspijean
[21:10:35]
<tituspijean> yeah we do actually: https://github.com/YunoHost/yunohost/blob/9a585f03c67923b31802aaee762888349f3b3f3d/src/diagnosers/00-basesystem.py#L251 (damn it was two years ago o_O)
[21:11:04]
<tituspijean> do you know which line of the script bugs out?
[21:11:41]
<tane> https://packages.debian.org/bullseye/spectre-meltdown-checker
[21:11:46]
<bormay[m]> I have no idea. I am trying to diagnose it
[21:12:07]
<bormay[m]> it freezes the damn vps for some reason
[21:16:08]
<tane> There is a bug for that.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986423
[21:17:11]
<bormay[m]> I have seen this. But the person didn't specify it it froze his system. I have a feeling that it didn't
[21:17:59]
<bormay[m]> The link is interesting .---
[21:18:01]
<bormay[m]> "This warning message does not affect the system in any way - it is only
there to gather info which userspace tools are poking at model-specific
registers (MSRs) with the intent to fix them because userspace should
not access MSRs - that's the kernel's job."
[21:18:10]
<tituspijean> tane thanks tane for the investigation! It looks like we need to upgrade the script (we manually include it in yunohost's core, we don't rely on the deb package)
[21:18:56]
<tituspijean> cf. https://github.com/speed47/spectre-meltdown-checker/issues/385 that seemingly fixed the issue according to debian's bugtracker
[21:20:45]
<bormay[m]> "According to the author of the patch above, writing to MSR is not recommended. And indeed, spectre-meltdown-checker.sh does exactly that. A few lines after a kernel lock down feature is mentioned, but this patch doesn't seem to be used with current kernels anymore."
[21:21:07]
<bormay[m]> Am I experiencing a kernel lockdown?
[21:21:17]
<bormay[m]> Is this why my vps freezes?
[21:22:42]
<tituspijean> You'd have to ask them. We are definitely no experts on that here.
[21:27:35]
<tituspijean> What I might suggest you to do, is manually updating the script:
```
sudo su
cd /usr/lib/python3/dist-packages/yunohost/vendor/spectre-meltdown-checker/
mv spectre-meltdown-checker.{sh,bak}
wget https://raw.githubusercontent.com/speed47/spectre-meltdown-checker/a6c943d38f315f339697ec26e7374a09b88f2183/spectre-meltdown-checker.sh
chmod +x spectre-meltdown-checker.sh
```
[21:33:23]
<bormay[m]> alright thank you. I have done that
[21:33:46]
<bormay[m]> now I will wait and see if my system will randomly freeze or crash :/ . . I never know when this happens
[21:33:51]
<bormay[m]> it is kind of random
[21:34:24]
<bormay[m]> but it always seems to happen when I am connecting to my vps or when I am doing something
[21:38:35]
<bormay[m]> this is incredible. I have never seen linux freeze. When this happens I am not able to connect through ssh. I can't even get a ping to the server.
[21:38:56]
<bormay[m]> If I connect with a KVM the only thing which is displayed is the aforementioned error
[22:10:52]
<bormay[m]> I have a suspicion that maybe contabo does something crazy like try to limit the banwidth on individual VPS instances through some sort of kernel injection
[22:11:28]
<bormay[m]> the vps itself is quite good. It has 16gb of ram and runs on a relatively modern amd cpu
[22:11:48]
<bormay[m]> also plenty of free ssd space
[22:12:03]
<bormay[m]> so the system is not running at its limit
[22:12:27]
<bormay[m]> and I doubt debian 11 has a major issue like this