[00:52:39]
<rodinux> Hello, I am migrating my server on another machine, I used the backup restore before post-install, all good exept a backup of uptime-kuma
[00:52:39]
<rodinux> I have logs here https://paste.yunohost.org/raw/qavepezapo
[00:53:30]
<rodinux> ```
Info : DEBUG - installing : node-v18.20.5
Info : WARNING - curl: (22) The requested URL returned error: 404
Info : DEBUG -
Info : WARNING - Error: download preflight failed for '18.20.5' (https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz)
```
[00:54:47]
<Aleks (he/him/il/lui)> sounds like it could be a temporary issue (it does work to fetch the url manually), does the same error reappear when retrying ?
[00:55:10]
<rodinux> yes
[00:55:58]
<Aleks (he/him/il/lui)> @_@
[00:56:19]
<rodinux> but you right, if I click on the link it propose a download ???
[00:56:43]
<Aleks (he/him/il/lui)> if you manually run `wget https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz` on the server, does it work ?
[00:57:32]
<rodinux> yes it works...
[00:59:02]
<rodinux> So why the restore breaks here ???
[00:59:02]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[00:59:03]
<rodinux> can I install manually first this dependencie ?
[00:59:46]
<rodinux> Is more `Error: download preflight failed for '18.20.5'`, I imagine is a npm module ??
[01:00:07]
<Aleks (he/him/il/lui)> it's node itself
[01:00:34]
<Aleks (he/him/il/lui)> what about `curl -L --head https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz | head -n 1`
[01:01:12]
<Aleks (he/him/il/lui)> (does it show HTTP/2 200 ?)
[01:01:28]
<rodinux> yes
[01:01:44]
<rodinux> ```
curl -L --head https://nodejs.org/dist/v18.20.5/node-v18.20.5-linux-x64.tar.xz | head -n 1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 22.8M 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
HTTP/2 200
```
[01:02:34]
<Aleks (he/him/il/lui)> 😐️
[01:03:33]
<rodinux> I can try the restore with `--force` ?
[01:03:47]
<Aleks (he/him/il/lui)> don't think that's going to change anything
[01:04:01]
<Aleks (he/him/il/lui)> can you try running `bash -x /opt/node_n/bin/n 18`
[01:04:21]
<Aleks (he/him/il/lui)> hopefully that should tell us what command exactly it tries to run
[01:05:16]
<rodinux> bash -x /opt/node_n/bin/n 18
bash: /opt/node_n/bin/n: No such file or directory
[01:05:57]
<Aleks (he/him/il/lui)> zrgmblg
[01:06:30]
<rodinux> It means is the only app which need node ??
[01:07:26]
<Aleks (he/him/il/lui)> and then re-run ` bash -x /opt/node_n/bin/n 18`
[01:07:26]
<Aleks (he/him/il/lui)> let's `cp /usr/share/yunohost/helpers.v2.d/vendor/n/n /opt/node_n/bin/n`
[01:08:32]
<rodinux> I have to crreate the directory /opt/node_n first
[01:09:33]
<rodinux> well all the directorys ??
[01:09:46]
<rodinux> directories
[01:10:45]
<Aleks (he/him/il/lui)> yeah `mkdir -p /opt/node_n/bin`
[01:12:08]
<rodinux> yes !
```
++ npm --version
- npm\_version\_str=' (with npm 10.8.2)'
++ /usr/local/bin/node --version
- log installed 'v18.20.5 (with npm 10.8.2)'
- printf ' \\033\[36m%10s\\033\[0m : \\033\[2m%s\\033\[0m\\n' installed 'v18.20.5 (with npm 10.8.2)'
installed : v18.20.5 (with npm 10.8.2)
- \[\[ -e /usr/local/bin/node \]\]
- \[\[ -e '' \]\]
- exit
[01:12:09]
<Aleks (he/him/il/lui)> so it worked ..?
[01:12:09]
<Aleks (he/him/il/lui)> @_@
[01:12:48]
<rodinux> 🤞
[01:13:03]
<Aleks (he/him/il/lui)> so we don't know why it didnt work 😭
[01:13:07]
<Aleks (he/him/il/lui)> (╯°□°）╯︵ ┻━┻
[01:13:14]
<rodinux> Yes !!
[01:13:20]
<Aleks (he/him/il/lui)> quantum bugs
[01:13:41]
<Aleks (he/him/il/lui)> so many people trying to come up with quantum computers yet we already have them
[01:13:44]
<rodinux> it works, thanks
[01:15:00]
<Aleks (he/him/il/lui)> i wouldn't call this a win, i can hear the chaos monkeys swearing about their revenge in the background
[01:16:17]
<Aleks (he/him/il/lui)> anyway, regular day in system administration i guess
[01:19:12]
<rodinux> well, if the chaos of monkeys arrive, we will join the rebellion
[01:22:23]
<rodinux> Yunohost is amazing, I have migrate so easly from a server to another, without this sytem it would be have a mount of time, brain and pain, I am sure of that...
[01:36:52]
<Craig van Beek> Hey, Since upgrading to Yunohost 12, Calibre ebook application seems to have died 🤷♂️ any chance of an update, or something I've missed? Logs : https://paste.yunohost.org/qiwopokiki
[05:11:40]
<@err404:matrix.numericore.com> Craig van Beek: did you tried to reboot your yunohost instance?
[05:13:57]
<Craig van Beek> > Craig van Beek: did you tried to reboot your yunohost instance?
several times
[05:17:07]
<@err404:matrix.numericore.com> Ok, I cannot read your logs in my smartphone, I will read later in my computer.
[05:17:36]
<Craig van Beek> it's just rebooting again now so will double check...
[05:20:28]
<@err404:matrix.numericore.com> Can you make a backup?
Then you can delete your calibre and reinstall a new and empty calibre? (To check if the app can work on your side)
[05:21:05]
<Craig van Beek> it was working previously... yeah, I can back it up, delete and try a fresh install, most likely be tomorrow though before I get a chance got a few other things on the go tonight
[05:22:12]
<@err404:matrix.numericore.com> Ok, so I will have time to read your logs 😃
[05:23:04]
<@err404:matrix.numericore.com> It is the early morning on my side 😃
[05:28:30]
<Craig van Beek> 6:30pm over here :)
[05:38:59]
<@err404:matrix.numericore.com> 6:37 in the morning here, we are on the oposites sides 😎
[05:51:53]
<Craig van Beek> Some good news...is going to be a beautiful day :) Was for us anyways 🤣
[06:55:40]
<nicofrand> Same issue here but only from a shortcut (on my launchscreen). If I type the app's url in the browser directly, no issue...
The issue appeared with ynh 12
[08:23:14]
<krcr> > <@krcr:matrix.org> Does someone know if delete and restore the app from backup worth a try?
Thanks for the reply! So I am out of ideas. I posted an issue on the synapse_ynh repo maybe Josue_T or someone one else will have some, my only lead is that I restored the app a year ago from 32 to 64 bits, I don't know if that can be linked: https://github.com/YunoHost-Apps/synapse_ynh/issues/495#issuecomment-2471669295
[08:26:37]
<krcr> > unlikely
Thanks for the reply! So I am out of ideas. I posted an issue on the synapse_ynh repo maybe Josue_T or someone one else will have some, my only lead is that I restored the app a year ago from 32 to 64 bits, I don't know if that can be linked: https://github.com/YunoHost-Apps/synapse_ynh/issues/495#issuecomment-2471669295
[09:26:07]
<hercut> Hello les gens, suite à mes echanges hier et la commande :
`apt full-upgrade -o APT::Force-LoopBreak=1 -o Dpkg::Options::='--force-confold'`
J'ai recu le mail suivant, je n'ai pas trouvé le log ...
```
=================================
Base system (basesystem)
=================================
[ERROR] You are running inconsistent versions of the YunoHost packages… most probably because of a failed or partial upgrade.
- yunohost version: 12.0.6 (stable)
- yunohost-admin version: 11.3.0 (stable)
- yunohost-portal version: ? (stable)
- moulinette version: 12.0.3 (stable)
- ssowat version: 12.0.3 (stable)
[WARNING] There's been a suspiciously high number of authentication failures recently. You may want to make sure that fail2ban is running and is correctly configured, or use a custom port for SSH as explained in https://yunohost.org/security.
=================================
Internet connectivity (ip)
=================================
[WARNING] DNS resolution seems to be working, but it looks like you're using a custom /etc/resolv.conf.
- The file /etc/resolv.conf should be a symlink to /etc/resolvconf/run/resolv.conf itself pointing to 127.0.0.1 (dnsmasq). If you want to manually configure DNS resolvers, please edit /etc/resolv.dnsmasq.conf.
=================================
Web (web)
=================================
[ERROR] Domain cryptpad.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain invidious.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain piped.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain searx.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain collabora.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain petrolette.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
[ERROR] Domain vaultwarden.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
- It looks like another machine (maybe your internet router) answered instead of your server.
1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
=================================
Services status check (services)
=================================
[ERROR] Service dnsmasq is failed :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart dnsmasq' and 'yunohost service log dnsmasq').
[WARNING] Configuration is broken for service fail2ban!
- ERROR: cannot import name 'MutableMapping' from 'collections' (/usr/lib/python3.11/collections/__init__.py)
[WARNING] Service yunohost-portal-api is unknown :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart yunohost-portal-api' and 'yunohost service log yunohost-portal-api').
[ERROR] Service yunomdns is failed :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart yunomdns' and 'yunohost service log yunomdns').
=================================
System configurations (regenconf)
=================================
[WARNING] Configuration file /etc/apt/sources.list.d/extra_php_version.list appears to have been manually modified.
- This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically… But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf apt --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf apt --force'
```
[09:28:33]
<John Livingston> Hello hello. J'ai quelqu'un qui a un soucis avec le plugin de tchat Peertube. Y'a des requêtes dont la réponse a une en-tête "x-sso-wat: You've just been SSOed", qui m'a l'air complètement étrangère à Peertube. C'est un truc yunohost ? Qu'est ce qui peut expliquer qu'on ai ça sur un appel d'API sur une URL censée être gérée par Peertube ?
[09:34:16]
<John Livingston> Ok, j'ai trouvé un ticket qui semble lié à ça: https://github.com/YunoHost/issues/issues/1420
[09:37:23]
<John Livingston> Mais par contre, je ne comprend pas comment ça se corrige.
[09:40:46]
<isAAAc> c'est mon peertube ^
[09:41:44]
<isAAAc> (je pause café car au taf depuis trois heures sans pause, mais je re dans pas longtemps ;) )
[09:43:58]
<isAAAc> tout le peertube marche sinon (hormis des abonnements qu se sync plus de manière aléatoires, il faut juste que je réabonne de force de temps en temps à une chaine ou une autre), mais le chat passe pas si je suis auth, pas de soucis sur chromium, que sur ffox
[09:44:25]
<isAAAc> je peux poster les confs nginx si besoin et/ou ouvrir un ticket
[09:47:22]
<isAAAc> (re)
[13:21:07]
<Andreas> Hi! I have tried to restore my Immich backup after having moved my `/home/yunohost.app/` dir to an external ssd (followed instructions from here: https://yunohost.org/oc/external\_storage). The backup fails to restore saying "Original path for "/home/yunohost.app/immich" not found". Full log: https://paste.yunohost.org/raw/obulucukub. As far as I can tell, the mount --bind of /home/yunohost.app/ works for all other apps. Good ideas? Thank you :)
[13:21:54]
<Salamandar> might be a permissions issue ?
[13:23:41]
<Andreas> Before restoring I had installed Backrest, which corrupted permissions to postgresql, so could very well be.
[13:25:20]
<Andreas> how to check?
[13:25:48]
<Andreas> or resolve? I get sweaty palms of permission errors 😅
[13:28:39]
<Andreas> in the pop-up dialog when trying to restore, I also get the error: "psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5433" failed: No such file or directory" and "Is the server running locally and accepting connections on that socket?"
[13:29:13]
<guillaume@maguicha.fr> The strange thing is that it worked fine until Iupgraded to Nextcloud 29.0.8…
[13:29:18]
<Andreas> this is when to app is removed after failed restore
[13:30:13]
<Aleks (he/him/il/lui)> feels like this could be a bug with helpers 2.1
[13:32:00]
<Aleks (he/him/il/lui)> is_data should become true here but it doesnt hmmmwhy
[13:32:47]
<Aleks (he/him/il/lui)> `[[ "$target" == "$data_dir*" ]]` eeeh that's not right
[13:33:13]
<Aleks (he/him/il/lui)> ah!
[13:33:25]
<Aleks (he/him/il/lui)> https://github.com/YunoHost/yunohost/commit/b516c142d83dde2b2de9e71bc4b6dca046760249 it fixed ynh_backup but not ynh_restore
[13:33:51]
<Aleks (he/him/il/lui)> Andreas: i'll patch it and make a new release
[13:34:06]
<Andreas> you're a hero!
[13:44:02]
<Maranda> !servers
[13:44:08]
<Echo Archon> Member list loaded, found 1089 members on 179 servers. Now running federation tests
[13:45:09]
<Echo Archon> ### Versions
* 1 server with 358 members on Synapse 1.119.0rc1
* 23 servers with 43 members on Synapse 1.118.0
* 58 servers with 65 members on Synapse 1.117.0
* 5 servers with 5 members on Synapse 1.115.0
* 1 server with 1 member on Synapse 1.114.0
* 9 servers with 10 members on Synapse 1.113.0
* 1 server with 4 members on Synapse 1.112.0
* 1 server with 4 members on Synapse 1.111.0
* 1 server with 1 member on Synapse 1.110.0
* 2 servers with 2 members on Synapse 1.109.0
* 1 server with 1 member on Synapse 1.107.0
* 1 server with 1 member on Synapse 1.105.1
* 1 server with 1 member on Synapse 1.105.0
* 3 servers with 3 members on Synapse 1.98.0
* 1 server with 1 member on Synapse 1.96.1
* 1 server with 2 members on Synapse 1.95.1
* 1 server with 1 member on Synapse 1.85.1
* 1 server with 1 member on Conduit 0.9.0-alpha
* 12 servers with 12 members on Conduit 0.9.0
* 1 server with 1 member on Conduit 0.7.0
* 1 server with 1 member on Conduit 0.10.0-alpha
* 1 server with 1 member on Dendrite 0.13.8
* 1 server with 516 members on Archon 1.118.0
### Errors
* elune.cloud (1 member): federation not OK
* sysop.me (1 member): federation not OK
* sc.bblaze.xyz (1 member): federation not OK
* schicksal.im (1 member): federation not OK
* liberium.fr (1 member): federation not OK
* rosahaj.xyz (1 member): federation not OK
* 494b8.strangled.net (1 member): federation not OK
* chat.bblaze.xyz (1 member): federation not OK
* govinda.krshna.at (1 member): federation not OK
* kenyseb.de (2 members): federation not OK
* karayan.xyz (1 member): federation not OK
* synapse.the-cryptolution.com (1 member): federation not OK
* im.anmol.net.in (1 member): federation not OK
* matrix.doeszen.org (1 member): federation not OK
* matrix.fosshost.com (1 member): federation not OK
* matrix.hetre-et-penser.fr (1 member): federation not OK
* intlsyn.org (1 member): federation not OK
* losk.me (1 member): federation not OK
* tchat.colibris-outilslibres.org (1 member): federation not OK
* chat.homehub.ovh (1 member): federation not OK
* gwenlg.fr (1 member): federation not OK
* librehost.io (1 member): federation not OK
* estradiol.rocks (1 member): federation not OK
* fanglap.com (1 member): federation not OK
* cyber-ghost.pp.ua (1 member): federation not OK
* lebeaunuage.net (1 member): federation not OK
* matrix.kodein.be (1 member): federation not OK
* matrix.flauschbereich.de (1 member): federation not OK
* social.pericles.hu (1 member): federation not OK
* mymatrix.yorili.com (1 member): federation not OK
* matrix.newan.net (1 member): federation not OK
* link-goe.de (1 member): federation not OK
* sabatino.cloud (1 member): federation not OK
* conduit.pijean.ovh (1 member): federation not OK
* blabla.blablub.de (1 member): federation not OK
* matrix.lebeaunuage.net (1 member): federation not OK
* rechtsmatrix.de (1 member): federation not OK
* toyshelf.club (1 member): federation not OK
* yorili.com (1 member): federation not OK
* l-linsner.com (1 member): federation not OK
* daemon.fail (1 member): federation not OK
* matrix.harrynjames.xyz (1 member): federation not OK
* on.toyshelf.club (1 member): federation not OK
* irelativism.org (1 member): federation not OK
* loliimoutolove.com (1 member): test timed out
* die-basis-rv.de (1 member): test timed out
* chat.stijnvp.xyz (1 member): test timed out
* emacsgirl.org (3 members): test timed out
* cat.casa (1 member): test timed out
* chat.divisionismanmade.net (1 member): test timed out
* ukronia.fr (1 member): test timed out
[13:45:19]
<Maranda> :/
[13:45:36]
*Maranda picks up for the spring cleans
[14:10:29]
<thatoo> J'ai un soucis avec une migration vers ynh 12 : https://paste.yunohost.org/raw/vagulafufi
[14:11:34]
<Aleks (he/him/il/lui)> classic grub-pc shit ...
[14:11:47]
<Aleks (he/him/il/lui)> tu peux faire ce qui est recommandé, à savoir `DEBIAN_FRONTEND=dialog dpkg --configure grub-pc`
[14:12:01]
<Aleks (he/him/il/lui)> sachant qu'il va te demander où tu veux installer le grub et faut faire gaffe à ce que tu réponds
[14:12:23]
<Aleks (he/him/il/lui)> (classiquement ça peut être parce que ton disque à changé depuis l'install initiale, ou bien parce qu'il s'apelle plus pareil pour des raisons™)
[14:14:15]
<thatoo> euh, du coup j'ai un autre pbm, mon utilisateur n'est plus dans le fichier sudoers (comme la migration est "en cours", je n'ose pas faire grand chose)
[14:17:54]
<Aleks (he/him/il/lui)> si tu es encore root, tu peux lancer `yunohost tools regen-conf nsswitch --force`
[14:18:12]
<thatoo> ```
admin@domain:~ $ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev 3,9G 0 3,9G 0% /dev
tmpfs 795M 980K 794M 1% /run
/dev/sda6 489G 38G 427G 8% /
tmpfs 3,9G 80K 3,9G 1% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
/dev/sdb1 295G 170G 110G 61% /media/stockage
/dev/sda1 2,1G 140M 1,9G 8% /boot
tmpfs 795M 0 795M 0% /run/user/46026
```
et quand viendra le moment de choisir, le grub, je l'installe sur /dev/sda1 (/boot), c'est bien ça ?
[14:18:50]
<Aleks (he/him/il/lui)> oui j'imagine, soit sda1, ou sda tout court, pour moi c'est pas clair ... logiquement ce serait sda1, mais avec un pote qui avait le soucis l'autre fois on a fait sda ... si ça se trouve ça ne change rien, je sais pas, c'est flou pour moi
[14:20:32]
<thatoo> > <@Alekswag:matrix.org> si tu es encore root, tu peux lancer `yunohost tools regen-conf nsswitch --force`
non, je ne suis pas root
[14:25:58]
<Aleks (he/him/il/lui)> dans ce cas tu devrais pouvoir devenir root avec "su" et taper le mdp root
[14:26:31]
<Aleks (he/him/il/lui)> > <@andreas:gdamsbo.dk> Hi! I have tried to restore my Immich backup after having moved my `/home/yunohost.app/` dir to an external ssd (followed instructions from here: https://yunohost.org/oc/external\_storage). The backup fails to restore saying "Original path for "/home/yunohost.app/immich" not found". Full log: https://paste.yunohost.org/raw/obulucukub. As far as I can tell, the mount --bind of /home/yunohost.app/ works for all other apps. Good ideas? Thank you :)
so this should be fixed if you upgrade to 12.0.7
[14:30:34]
<thatoo> > <@Alekswag:matrix.org> dans ce cas tu devrais pouvoir devenir root avec "su" et taper le mdp root
je n'ai pas le mdp root, seulement le mdp de l'utilisateur qui a pris la place de l'ancien "admin"
[14:32:20]
<Aleks (he/him/il/lui)> le mdp root c'est potentiellement le premier mot de passe que t'as défini long time ago
[14:33:30]
<Andreas> > <@Alekswag:matrix.org> so this should be fixed if you upgrade to 12.0.7
I was just writing! :) Thanks for your quick response! Have just installed 12.0.7. It looks like it worked, but now there is a new problem when trying to restore. Log: https://paste.yunohost.org/raw/emivalixup. Looks like the problem with postgresql, which might be the same problem that caused Immich to stall and be to try to restore. ANy idea?
[14:41:11]
<Aleks (he/him/il/lui)> ah god is immich that famous app that depends on a specific version of postgresql T_T
[14:41:43]
<Aleks (he/him/il/lui)> zblerugruahra
[14:42:24]
<Aleks (he/him/il/lui)> i would check was does `pg_lsclusters` return, maybe the old version of postgres (13?) is still using port 5433 or something idk
[14:42:53]
<Aleks (he/him/il/lui)> i gotta move tho
[14:50:16]
<Andreas> > <@Alekswag:matrix.org> i would check was does `pg_lsclusters` return, maybe the old version of postgres (13?) is still using port 5433 or something idk
Ah. I will try to have a look at this. I suppose I can fall back to restoring files manually.
[14:53:29]
<hercut> > <@hercut:matrix.org> Hello les gens, suite à mes echanges hier et la commande :
> `apt full-upgrade -o APT::Force-LoopBreak=1 -o Dpkg::Options::='--force-confold'`
> J'ai recu le mail suivant, je n'ai pas trouvé le log ...
> ```
> =================================
> Base system (basesystem)
> =================================
>
> [ERROR] You are running inconsistent versions of the YunoHost packages… most probably because of a failed or partial upgrade.
> - yunohost version: 12.0.6 (stable)
> - yunohost-admin version: 11.3.0 (stable)
> - yunohost-portal version: ? (stable)
> - moulinette version: 12.0.3 (stable)
> - ssowat version: 12.0.3 (stable)
>
> [WARNING] There's been a suspiciously high number of authentication failures recently. You may want to make sure that fail2ban is running and is correctly configured, or use a custom port for SSH as explained in https://yunohost.org/security.
>
>
>
> =================================
> Internet connectivity (ip)
> =================================
>
> [WARNING] DNS resolution seems to be working, but it looks like you're using a custom /etc/resolv.conf.
> - The file /etc/resolv.conf should be a symlink to /etc/resolvconf/run/resolv.conf itself pointing to 127.0.0.1 (dnsmasq). If you want to manually configure DNS resolvers, please edit /etc/resolv.dnsmasq.conf.
>
>
>
> =================================
> Web (web)
> =================================
>
> [ERROR] Domain cryptpad.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain invidious.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain piped.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain searx.celien.link appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain collabora.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain petrolette.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
> [ERROR] Domain vaultwarden.jbv.cloud appears unreachable through HTTP from outside the local network in IPv4, though it works in IPv6.
> - It looks like another machine (maybe your internet router) answered instead of your server.
> 1. The most common cause for this issue is that port 80 (and 443) are not correctly forwarded to your server.
> 2. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
>
>
>
> =================================
> Services status check (services)
> =================================
>
> [ERROR] Service dnsmasq is failed :(
> - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart dnsmasq' and 'yunohost service log dnsmasq').
>
> [WARNING] Configuration is broken for service fail2ban!
> - ERROR: cannot import name 'MutableMapping' from 'collections' (/usr/lib/python3.11/collections/__init__.py)
>
> [WARNING] Service yunohost-portal-api is unknown :(
> - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart yunohost-portal-api' and 'yunohost service log yunohost-portal-api').
>
> [ERROR] Service yunomdns is failed :(
> - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart yunomdns' and 'yunohost service log yunomdns').
>
>
>
> =================================
> System configurations (regenconf)
> =================================
>
> [WARNING] Configuration file /etc/apt/sources.list.d/extra_php_version.list appears to have been manually modified.
> - This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically… But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf apt --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf apt --force'
> ```
Je me permet un petit up si possible ?
[15:01:41]
<hercut> Dans la continuité, j'ai essayé d'allé sur le diag de la webadmin et ca me dit ca :
```
Erreur: "500"
Action: "PUT" /yunohost/api/diagnosis/run?except_if_never_ran_yet
Message d'erreur :
Failed to load diagnoser ip : cannot import name 'parse_filter_key' from 'yunohost.utils.configpanel' (/usr/lib/python3/dist-packages/yunohost/utils/configpanel.py)
Pendant le traitement de l'action, le serveur a dit :
unable to retrieve string to translate with key 'tos_postinstall_acknowledgement' for default locale 'locales/en.json' file (don't panic this is just a warning)
```
[15:02:19]
<hercut> Je n'arrive as à allé sur les journaux, enfin ca n'affiche rien :/
[15:24:37]
<thatoo> > <@Alekswag:matrix.org> le mdp root c'est potentiellement le premier mot de passe que t'as défini long time ago
J'ai essayé tout ce que je connaissais, impossible de devenir root. Ce n'est pas grave, je vais restaurer une sauvegarde. Par contre, j'ai ensuite testé tous mes ynh et aucun de mes mdp des utilisateurs admin ne m'ont permis de devenir root. Je n'arrive à devenir root que via `` sudo su root `` pas directement `` su root ``.
Du coup, j'ai fait `` sudo su root `` puis `` passwd `` pour mettre un mdp à root. Je me demande combien pense à le faire.
[15:48:18]
<Andreas> > <@Alekswag:matrix.org> i would check was does `pg_lsclusters` return, maybe the old version of postgres (13?) is still using port 5433 or something idk
So, looks like for some reason I have version 15, 16 and 17 on the system with 15 running:
```Ver Cluster Port Status Owner Data directory Log file
15 main 5432 online postgres /var/lib/postgresql/15/main /var/log/po
stgresql/postgresql-15-main.log
16 main 5433 down postgres /var/lib/postgresql/16/main /var/log/po
stgresql/postgresql-16-main.log
17 main 5434 down postgres /var/lib/postgresql/17/main /var/log/po
stgresql/postgresql-17-main.log```
[16:39:55]
<isAAAc> > je peux poster les confs nginx si besoin et/ou ouvrir un ticket
ok , i'll see to manage this in an issue, but not tonight i'm out of order after this hell's day @ work ;) thx for your help anyway John Livingston
[17:07:02]
<yvanq> Hello, looking to migrate to yunohost 12 my production server, any trick or risk of failure of any app?
[17:34:55]
<orhtej2> > <@yvanq:matrix.org> Hello, looking to migrate to yunohost 12 my production server, any trick or risk of failure of any app?
Node and python apps typically need an update afterwards
[18:17:09]
<Paprika> > <@yvanq:matrix.org> Hello, looking to migrate to yunohost 12 my production server, any trick or risk of failure of any app?
Migrated two of my servers, one important, one production but disposable, both went well. On the second server the migration made webUI inaccessible, which I went and fixed, but I then broke something later, did a rollback and migrated again, without issues.
I’d say it is safe, but of course, make sure all of your apps work correctly, are accessible, don’t throw errors upon usage, verify if your configs haven’t been updated if you manually edited any of them.
[18:19:39]
<482535397> good
[18:19:43]
<Paprika> The only app I had issues with was Jellyfin, but it was due to Jellyfin’s update rather than migration. Update to Jellyfin causes it to try and bind to 127.0.0.1 (it populates the field with this), which makes clients unable to access the server on anything except a browser. Couldn’t find anything on the net about this, fixed it by comparing configs.
[21:00:03]
<thatoo> > <@Alekswag:matrix.org> tu peux faire ce qui est recommandé, à savoir `DEBIAN_FRONTEND=dialog dpkg --configure grub-pc`
J'ai restauré ma sauvegarde mais la commande est en erreur :
```
$ DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg: erreur de traitement du paquet grub-pc (--configure) :
le paquet grub-pc est déjà installé et configuré
Des erreurs ont été rencontrées pendant l'exécution :
grub-pc
```
[21:00:27]
<geoma> Hi. I am migrating my server to my new house, and I need to access it locally (through keyboard and monitor) as apparently it is not connected to the internet. Thing is I dont know what is the debian system local login. Should credentials I usr for SSH access work?
[21:01:52]
<Aleks (he/him/il/lui)> > <@thatoo:defis.info> J'ai restauré ma sauvegarde mais la commande est en erreur :
> ```
> $ DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
> dpkg: erreur de traitement du paquet grub-pc (--configure) :
> le paquet grub-pc est déjà installé et configuré
> Des erreurs ont été rencontrées pendant l'exécution :
> grub-pc
> ```
it's telling it's already configured so it's not needed anymore supposedly...
[21:03:04]
<thatoo> Pour l'instant je n'ai fait que restaurer à l'instant avant la migration donc logiquement pendant la migration je devrais avoir la même erreur.
Peut-être n''est-ce pas possible de l'anticiper.
[21:03:43]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[21:04:14]
<Aleks (he/him/il/lui)> ah tu veux dire tu as restauré ta sauvegarde genre, tu as rollback à une ancienne image du système ...
[21:06:28]
<thatoo> oui, tout à fait, depuis proxmox backup
[21:10:01]
<thatoo> la seule différence c'est que maintenant, j'ai un mdp pour root :-)
[22:15:33]
<geoma> Ok no problem... I managed to access through local private IP
[22:21:18]
<thatoo> Comme attendu, j'ai de nouveau la même erreur.
Je me connecte en tant que root et /
[22:22:00]
<thatoo> ```
# DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg: avertissement: « ldconfig » introuvable dans la variable PATH ou non exécutable
dpkg: avertissement: « start-stop-daemon » introuvable dans la variable PATH ou non exécutable
dpkg: erreur: 2 programmes attendus non trouvés dans la variable PATH ou non exécutables
Note : la variable PATH du superutilisateur doit normalement contenir /usr/local/sbin, /usr/sbin et /sbin
```
[22:24:39]
<thatoo> Par contre, j'ai pu faire
`` yunohost tools regen-conf nsswitch --force ``
et en tant qu'utilisateur admin mais pas root, j'ai pu lancer la commande
[22:32:22]
<thatoo> et maintenant, je n'ai plus que l'erreur avec php7.3-fpm : https://paste.yunohost.org/raw/isadoyazuj
[22:52:39]
<thatoo> en désinstallant php7.3-fpm, la migration a pu se terminer.
[23:00:31]
<pti-jean> thatoo, 👍️ bravo! La persévérance fini par payer!
[23:00:55]
<pti-jean> J'ai Bitwarden qui ne fonctionne plus sur mon téléphone Android... une idée ?
[23:01:17]
<pti-jean> Message:
"Nous n'avons pas pu traiter votre requête. Veuillez réessayer ou nous contacter."
[23:01:44]
<pti-jean> J'ai été obligé de rétrograder Bitwarden à la version 2024.6.0 pour qu'il fonctionne! Bizarre! Une idée ??
[23:12:58]
<geoma> Ok the priblem is the ISP of my new home is apparently a CGNAT and does not allow port forwarding at all. How can I solve this???😭