YunoHost 3.8 testing / Call for feedback

[pascalv]

@Aleks same pb here, i can not stop service and restart anymore
the message is here

can you please help pascal

[Aleks]

Alrighty, sorry for the issue about service logs Should be fixed in 3.8.4.1

@gauthier67

Domain mondomain.nohost.me appears unreachable through HTTP from outside the local network.
Although have a VPN (ARN). I guess HTTPS is forced so it should not be a problem?

Hm yes it is, because HTTP is used for the ACME challenge for Let’s Encrypt … (And unfortunately many browser still attempt to connect using HTTP first) But are you sure it ain’t a false negative from the diagnosis ? Or do you confirm that it’s indeed not accessible on HTTP ?

@gauthier67

Service ynh-vpnclient-checker is dead :(
Probably this should not be considered a “problem” rather a “warning” or “info” as dead=good. Or this should be ignored by default?

Uh imho dead=bad in the general case But some service states are hard to diagnose because the info from systemd is not reliable … Typically some services are in state exited which can be good or bad depending on the service … This issue ain’t easy to solve but we’re going to see it showing up for many services installed by some apps … So far I don’t know what to do

@gauthier67

The system has only 500 MiB swap. You should consider having at least 512 MiB to avoid situations where the system runs out of memory.
Probably set the threshold to <=499 or <500 to avoid having an info message in many cases.

Damn I already had this on my server where it had exactly 512MB and the check was a “if swap is lower or equal than … then show warning”. I lowered it to 500 but still shows up for you so I lowered it to 450 ¯\_(ツ)_/¯

[pascalv]

@Aleks 3.8.4.1 installed - it fixed the services pages. Thanks all seems ok now

[Gofannon]

Made the switch to 3.8. Found a typo in a command given in the migration log

Attention : Trouvé 1 objet(s) pouvant être amélioré(s) pour Configurations système.
Attention : Pour voir les problèmes détectés, vous pouvez accéder à la section Diagnostic du webadmin ou exécuter « yunohost diagnostic show --issues » à partir de la ligne de commande.

Sould be

yunohost diagnosis show --issues instead of diagnostic

[Gofannon]

Feedback

In the diagnosis panel, I get two warnings that are interesting to share here

etckeeper

Configuration file /etc/etckeeper/etckeeper.conf appears to have been manually modified.

But the file does not exists anymore

root@yunohost:~# ls -al /etc/etckeeper/
ls: impossible d'accéder à '/etc/etckeeper/': Aucun fichier ou dossier de ce type
root@yunohost:~# 

DNS nohost.me

Some DNS records are missing or incorrect for domain XXX.nohost.me (category xmpp)

1. Do I need to do something about it?
2. Will the DNS be updated on the YunoHost side?
3. Will it “works” automagically?

Personal feedback

It’s really usefull, thanks to the team!!

Thanks to the diagnosis, I was able to:

1. fix DNS config about “xmpp-upload” entry
2. remove uwsgi service dating from an install of Searx in 2016 …

[gauthier67]

@Aleks

But are you sure it ain’t a false negative from the diagnosis ? Or do you confirm that it’s indeed not accessible on HTTP ?Typically some services are in state exited which can be good or bad depending on the service …

How can I test whether it is not accessible? In my browser if I give http://mydomain.tld I am redirected to https:// for both the admin and the user web pages.

@Aleks

Typically some services are in state exited which can be good or bad depending on the service

Is it possible to give specific “normal status” for specific Service, or is it just set by a general rule? ynh-vpnclient-checker is supposed to be running only if ynh-vpnclient is down, am I right? If yes, dead, or at least exited should be OK. If not, I guess I have some issue on my side because I never saw it running. I guess there could be an exception list giving “normal status” for specific services.

[Aleks]

@Gofannon

Configuration file /etc/etckeeper/etckeeper.conf appears to have been manually modified.

But the file does not exists anymore

Yup indeed … Had the same … I’ll add a fix

@Gofannon

• Do I need to do something about it?
• Will the DNS be updated on the YunoHost side?
• Will it “works” automagically?

Yes and no … for existing instances you gotta do a yunohost dyndns update --force … it should probably be advertised in the details of the diagnosis when running a nohost.me/noho.st/ynh.fr domain…

@gauthier67

In my browser if I give http://mydomain.tld I am redirected to https:// for both the admin and the user web pages.

Then my guess is that the HTTP does work because that’s in fact probably nginx which answers the very first requests with a redirection (as in “ask me again in HTTPS bruh!”). But it could also be a cache thing. Imho you can check this using the Network tab in Firefox debug (F12) and check the very first request sent. Or using a curl http://domain.tld in a terminal (should show something like 302 Found)

If you confirm that HTTP does work, then we should investigate why the diagnosis reports an issue if there’s no issue

@gauthier67

Is it possible to give specific “normal status” for specific Service, or is it just set by a general rule? ynh-vpnclient-checker is supposed to be running only if ynh-vpnclient is down, am I right? If yes, dead , or at least exited should be OK. If not, I guess I have some issue on my side because I never saw it running. I guess there could be an exception list giving “normal status” for specific services.

Hmmmyeah we can probably have some hardcoded list (it’s not pretty but it works). I don’t remember exactly what ynh-vpnclient-checker does exactly … We have the same kind of thing for yunohost-firewall which runs then exits.

The thing is, for that kind of service, reporting that “oh the service ain’t running, which is expected, so put it in green!” ain’t helpful or is even misleading. What you want to check is something like a) did it have the effect it’s suppose to have (e.g. configuring the firewall + that configuration is still there) or b) will it run when it needs to run ?

It looks like ynh-vpnclient-checker is in fact a timer and not a service (to be confirmed?) so gotta think about that to do

[gauthier67]

@Aleks

show something like 302 Found)

It actually shows:

<html>
<head><title>302 Found</title></head>
<body bgcolor="white">
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

@Aleks

What you want to check is something like a) did it have the effect it’s suppose to have (e.g. configuring the firewall + that configuration is still there) or b) will it run when it needs to run ?

My guess is ynh-vpnclient-checker is checking every 5 minutes if the VPN is mounted. If not it tries to restart it. If my guess is right, then we could get rid of of it, and use the diagnosis tool to give the admin some statistics about the VPN, like did it disconnect since last time vpnclient was started? For how long / how many times?
I think we could have two options here:

1. Strong privacy configuration (for advanced users): Connection to internet only through VPN. If VPN down, only the domain of the VPN server is reachable. Maybe we could re-use the configuration we use in Natta.
2. Flexible/monitored configuration: If VPN is down, connection to internet still possible. There the user could see in the diagnosis how often/long the VPN has been down since last vpnclient start. And set up notifications when the VPN unmounts.

[francoisa]

3.8.4.1 works fine.
A string not translate in french (all others are well done) :

 Le système dispose de 4.4 GiB de swap !
    Please be careful and aware that if the server is hosting swap on an SD card or SSD storage, it may drastically reduce the life expectancy of the device`.

[Aleks]

@francoisa

A string not translate in french (all others are well done) :

Yes the translations are not handled by the core development and therefore no guarantee that everything is 100% translated … They happen as people work on the on the translate.yunohost.org interface. Feel free to contribute there . (For french though it’s usually close to 100%, but this specific string was added very recently)

[Aleks]

For people on ARM64 boards : upgrade should now be possible now that metronome’s build is fixed

[ljf]

I found a small issue:
Multi_instance apps are not installable several times on Webadmin cause the Install button is disabled.
Expected behaviour: enable the install button if it’s multi_instance

[Kayou]

Should be fixed by: https://github.com/YunoHost/yunohost-admin/pull/300

[ljf]

I was just starting to stare at it. Thanks !

[lnoferin]

A little bug in yunohost testing version

yunohost:
repo: testing
version: 3.8.4.1
yunohost-admin:
repo: testing
version: 3.8.3.1
moulinette:
repo: testing
version: 3.8.1
ssowat:
repo: testing
version: 3.8.0

recreating the /etc/ssh/sshd_config file with the command

yunohost tools regen-conf ssh --dry-run --with-diff

the file has a little typo in the line

Match Address 192.168.0.0/16,10.0.0.0/8,172.16.0.0/12,169.254.0.0/16,fe80::/10,fd00::/8
    PermitRootLogin yes##-> my_webapp

without the carriage return after yes. I think it should be

Match Address 192.168.0.0/16,10.0.0.0/8,172.16.0.0/12,169.254.0.0/16,fe80::/10,fd00::/8
    PermitRootLogin yes
##-> my_webapp

[Kayou]

I think it’s more a bug in my_webapp: https://github.com/YunoHost-Apps/my_webapp_ynh/blob/testing/conf/ssh_regenconf_hook#L21

[FLBSLB]

Malheureusement depuis que je suis passé en version 3.8.4.1 PHP 7.3 ne démarre plus
J’ai redémarré le serveur, vérifié les logs mais rien de probant.
Une idée?

[Aleks]

@FLBSLB

Est-ce que tu peux partager le log du service qui devrait se trouver dans Services > Php7.3-fpm … (il devrait y’avoir un bouton vert “Partager avec Yunopaste”)

[FLBSLB]

https://paste.yunohost.org/uladerapop

Et pardon j’ai oublié d’être poli.

Bonjour et merci de votre aide

[FLBSLB]

En regardant le fichier de conf nextcloud.conf dans /etc/php/7.3/fpm/pool.d/ je vois en ligne 36:
listen = /var/run/php/php7.3-fpm-nextcloud.sock
Alors que dans ce répertoire je n’ai que des fichiers de conf pour PHP 7.0 et pour d’autres applications (rainloop, netdata…)