YunoHost 3.8 testing / Call for feedback

Announcements
, ,
61

For your ssh server config, you can check what has been modified by executing this command (via SSH) :

sudo yunohost tools regen-conf --dry-run --with-diff ssh
62 
> 
> -##-> my_webapp
> -    # Hardening user connection
> -    Match User webapp1
> -    ChrootDirectory %h
> -    ForceCommand internal-sftp
> -    AllowTcpForwarding no
> -    PermitTunnel no
> -    X11Forwarding no
> -    PasswordAuthentication yes
> -##<- my_webapp
> +        PermitRootLogin yes
>       status: modified

Seems to be my_webapp


63

Indeed. my_webapp adds a post-hook that appends this config to the SSH server config.

This is normal then.

1 Like
64

Thanks for the update ! Everything went smoothly, as usual :slight_smile:.
I still have two warnings about DNS: it is pihole which change /etc/resolv.conf and /etc/dnsmasq.conf.

65

What we need to know if you think you have a false-positive on mail blacklist check

For people (@ericg) who meet this issue, we need returns of these commands AFTER you add made the upgrade and force-rerun the diagnosis. Feel free to send us the result on a private message if you prefer

yunohost --version
cat /etc/resolv.conf
curl ip.yunohost.org
curl ip6.yunohost.org
yunohost diagnosis show mail --issues
yunohost app list

If your public IPv4 is AAA.BBB.CCC.DDD, do these commands (note the ip is “reversed”) for each blacklist which failed, example with zen.spamhaus.org. You can find the dnsbl to use by refering to our dnsbl list https://github.com/YunoHost/yunohost/blob/stretch-unstable/data/other/dnsbl_list.yml

dig +short A DDD.CCC.BBB.AAA.zen.spamhaus.org
dig +short A DDD.CCC.BBB.AAA.zen.spamhaus.org @127.0.0.1
dig +short A DDD.CCC.BBB.AAA.zen.spamhaus.org @8.8.8.8

If you are not blacklisted these commands should return nothing.

Next try directly by calling:

yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org', 'A'));"
yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org', 'A', 'force_external'));"
yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org', 'A', ['8.8.8.8']));"

yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org.', 'A'));"
yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org.', 'A', 'force_external'));"
yunohost tools shell -c "from yunohost.utils.network import dig ; print(dig('DDD.CCC.BBB.AAA.zen.spamhaus.org.', 'A', ['8.8.8.8']));"

About the WHOIS expiration date feature

If the system says it is not able to find the expiration date of your domain, please send us you domain, like that we could improve our system. Especially if you have domain with a particular TLD.

You can also verify your domain expiration displayed by your registrar with the one we display. The 2 date should be distant from 2 days maximum, if it’s more, say us.

2 Likes
66

I’m blacklisted because of Orange ISP. Thanks to the diagnostic system for for bringing this to me.

About the WHOIS expiration date feature

If the system says it is not able to find the expiration date of your domain, please send us you domain, like that we could improve our system. Especially if you have domain with a particular TLD.

You can also verify your domain expiration displayed by your registrar with the one we display. The 2 date should be distant from 2 days maximum, if it’s more, say us.

2 days for me, so I guess it’s ok :slight_smile:

Thank you so much for your work

1 Like
67

3.8.2.1 was released with a couple of additional small fixes, in particular for the false-negatives about blacklists, as reported by @ericg and @pascalv (thanks for the tests !)

That was a sneaky subtle issue but should (really) be fixed now

  • [fix] Make sure DNS queries are done using absolute names to avoid stupid issues
  • [fix] More reliable way to fetch PTR record / reverse DNS
  • [fix] Propagate IPv6 default route check to ip diagnoser code as well
2 Likes
68

Yes it works! :+1:, that was quick.

1 Like
69

J’ai encore une question.
Concernant le reverse DNS, le diagnostic me renvoie deux alertes:

- Le DNS inverse n'est pas correctement configurĂ© en IPv4. Certains e-mails seront peut-ĂȘtre refusĂ©s ou considĂ©rĂ©s comme des spam. 
- Aucun DNS inverse n’est dĂ©fini pour IPv6. Certains e-mails seront peut-ĂȘtre refusĂ©s ou considĂ©rĂ©s comme des spam.

Je ne retrouve pas ces erreurs aprùs un essai avec mail-tester qui me donne un joli 10/10


Ces erreurs viennent d’apparaütre avec la version 3.8.2.1.

70

mail-tester ne teste que l’IPv4 
 du coup le truc sur l’IPv6 est probablement juste, par contre c’est Ă©trange effectivement pour l’ipv4 
 Que raconte les dĂ©tails ? (Ă©ventuellement remplace les donnĂ©es privĂ©es par ‘domain.tld’ par exemple)

71

I try the upgrade a few minutes ago and encoutered an error during metronome upgrade. Failed to restart because of a syntax error.

Unpacking ldap-utils (2.4.44+dfsg-5+deb9u4) over (2.4.44+dfsg-5+deb9u3) ...
Setting up ldap-utils (2.4.44+dfsg-5+deb9u4) ...
(Reading database ... 48048 files and directories currently installed.)
Preparing to unpack .../metronome_3.13.6+yunohost-1_armhf.deb ...
Unpacking metronome (3.13.6+yunohost-1) over (3.12.0+yunohost-1) ...
Setting up metronome (3.13.6+yunohost-1) ...
Job for metronome.service failed because the control process exited with error code.
See "systemctl status metronome.service" and "journalctl -xe" for details.
invoke-rc.d: initscript metronome, action "start" failed.
● metronome.service - LSB: Metronome XMPP Server
   Loaded: loaded (/etc/init.d/metronome; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-05-01 13:07:12 UTC; 72ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19477 ExecStart=/etc/init.d/metronome start (code=exited, status=1/FAILURE)

May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: in function '_real_require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:154: in function 'require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:108: in function 'init_net_server'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:376: in main chunk
May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: ?
May 01 13:07:12 yunolime2test.local metronome[19477]:  failed!
May 01 13:07:12 yunolime2test.local systemd[1]: metronome.service: Control process exited, code=exited status=1
May 01 13:07:12 yunolime2test.local systemd[1]: Failed to start LSB: Metronome XMPP Server.
May 01 13:07:12 yunolime2test.local systemd[1]: metronome.service: Unit entered failed state.
May 01 13:07:12 yunolime2test.local systemd[1]: metronome.service: Failed with result 'exit-code'.
dpkg: error processing package metronome (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 metronome
E: Sub-process /usr/bin/dpkg returned an error code (1)

The crash logs

-- Unit metronome.service has begun starting up.
May 01 13:07:12 yunolime2test.local metronome[19477]: Starting Metronome XMPP Server: metronomelua5.1: error loading module 'net.server_event' from file '/usr/lib/metronome/n
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/lib/metronome/net/server_event.lua:139: unexpected symbol near ';'
May 01 13:07:12 yunolime2test.local metronome[19477]: stack traceback:
May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: ?
May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: in function '_real_require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:154: in function 'require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/lib/metronome/net/server.lua:12: in main chunk
May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: in function '_real_require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:154: in function 'require'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:108: in function 'init_net_server'
May 01 13:07:12 yunolime2test.local metronome[19477]:         /usr/bin/metronome:376: in main chunk
May 01 13:07:12 yunolime2test.local metronome[19477]:         [C]: ?
May 01 13:07:12 yunolime2test.local metronome[19477]:  failed!
May 01 13:07:12 yunolime2test.local systemd[1]: metronome.service: Control process exited, code=exited status=1
May 01 13:07:12 yunolime2test.local systemd[1]: Failed to start LSB: Metronome XMPP Server.

I check the code of metronome v3.13.6 and the code is not the same so do we use master branch instead of a tagged release to build the package ?

72

@HugoPoi : indeed, Maranda the maintainer just warned me about this, fix on the way 
 :s

(The builds are from https://github.com/YunoHost/metronome on branch Debian, it’s sync with the upstream when we do releases )

73

We sync on master on every commit ?

74

Uuuuh not sure “on every commit”, it’s synced manually with a “git merge upstream/master” basically (or “git merge <tag>”)

75

Ok not great, we should used the tagged release, and I see that we packaged for Debian, a PR in the upstream could be doable ?

76

We do use the tagged release, Maranda warns us when there’s a new tag and we do merge the new tag at that time

I guess yup, but there’s also the question of how to actually build the package (and until recently I didn’t know about platforms that allow to request build like salsa.debian or idk which one arthurlutz mentionned 
)

77

I have also my metronome not starting - what to do here?
waiting an update?

78

Weird about the tag stuff because YunoHost/metronome pull upstream until 18d162c commit but the v3.13.6 point to 1e43613. Maranda has probably moved the tags after fixing the issue ? which is very bad if it’s the case

79

I think he did :stuck_out_tongue_winking_eye:

80

Qu’on lui coupe la tĂȘte

I think we can used Github Worflows for building 
 and would be really cool to make the package available in Debian repository too but probably lot of work