[08:07:31]
<rodinux> Hello, j'ai des soucis de resolv.conf...
[08:08:10]
<rodinux> je n'ai pas de `/etc/run`
[08:09:00]
<rodinux> le lien symbolique ressemblait à `l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Feb 11 2024 /etc/resolv.conf -> ../run/resolvconf/resolv.conf`
[08:13:06]
<rodinux> du coup j'ai essayé de supprimer et réinstaller `apt install resolvconf --reinstall` de supprimer `/etc/resolv.conf` et d'ajouter un un lien symbolique `ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf` mais il n'y a pas de dossier `/etc/resolvconf/run` !!
[08:14:27]
<rodinux> Comment résoudre cela ....
[08:15:03]
<rodinux> j'ai essayer ensuite un `regen-conf dnsmasq` mais pas mieux...
[08:16:57]
<rodinux> ```
# cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or director
```
[08:17:01]
<rodinux> y
[08:18:12]
<Salamandar> tu peux tenter un systemctl restart dnsmasq ?
[08:18:26]
<Salamandar> je crois que c'est lui qui crée le dossier /run/resolvconf
[08:20:46]
<rodinux> toujours pas...
[08:23:18]
<rodinux> en fait il y a bien un fichier `/run/resolvconf/resolv.conf`
[08:23:24]
<rodinux> mais pas de `/etc/resolvconf/run/resolv.conf`
[08:24:09]
<Salamandar> > <@rodinux:matrix.org> mais pas de `/etc/resolvconf/run/resolv.conf`
ça n'existe pas ça
[08:24:58]
<rodinux> et du coup qu'est-ce que veut dire `ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf`
[08:26:50]
<Salamandar> Pas sûr de pourquoi tu veux faire un tel lien
[08:26:59]
<Salamandar> ```
root@ci-apps-bookworm:/var/www/yunorunner/package_check# ls /etc/resolv* -lah
lrwxrwxrwx 1 root root 29 Sep 23 23:41 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
```
[08:27:37]
<rodinux> Ah Ok, c'est ce que j'avais auparavant !
[08:28:05]
<rodinux> Du coup comment je peut recréer ce lien ?
[08:28:32]
<Salamandar> supprime-le puis restart dnsmasq
[08:28:35]
<Salamandar> il devrait le recréer
[08:29:50]
<rodinux> je supprime `/etc/resolv.conf` ? ou le lien créer ?
[08:30:41]
<rodinux> ceci dit en fait il n'existe tout simplement pas du coup...
[08:33:26]
<rodinux> mais j'ai toujours
[08:33:28]
<rodinux> ls -lah /etc/resolv*
-rw-r--r-- 1 root root 551 Oct 22 10:15 /etc/resolv.dnsmasq.conf
/etc/resolvconf:
total 24K
drwxr-xr-x 5 root root 4.0K Oct 22 09:57 .
drwxr-xr-x 96 root root 4.0K Oct 22 10:31 ..
-rw-r--r-- 1 root root 878 Jan 6 2021 interface-order
lrwxrwxrwx 1 root root 31 Oct 22 09:54 resolv.conf -> /etc/resolvconf/run/resolv.conf
[08:33:51]
<Salamandar> mais ce lien c'est toi qui l'as créé ?
[08:33:59]
<rodinux> oui
[08:34:06]
<Salamandar> supprime-le puis redémarre dnsmasq
[08:34:49]
<Salamandar> ```
root@ci-apps-bookworm:/home/yunohost# ls -lah /etc/resolv*
lrwxrwxrwx 1 root root 29 Sep 23 23:41 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
-rw-r--r-- 1 root root 551 Oct 17 06:22 /etc/resolv.dnsmasq.conf
/etc/resolvconf:
total 24K
drwxr-xr-x 5 root root 4.0K Sep 23 23:41 .
drwxr-xr-x 111 root root 4.0K Oct 22 10:33 ..
-rw-r--r-- 1 root root 878 Jan 6 2021 interface-order
drwxr-xr-x 2 root root 4.0K Sep 23 23:41 resolv.conf.d
drwxr-xr-x 2 root root 4.0K Sep 23 23:41 update.d
drwxr-xr-x 2 root root 4.0K Sep 23 23:41 update-libc.d
```
[08:35:25]
<rodinux> mais aucun des 2 n'esixte !
[08:36:02]
<rodinux> rm /etc/resolv.conf
rm: cannot remove '/etc/resolv.conf': No such file or directory
[08:36:36]
<rodinux> rm -i /etc/resolvconf/run/resolv.conf
rm: cannot remove '/etc/resolvconf/run/resolv.conf': No such file or directory
[08:36:59]
<Salamandar> mais pas la cible
[08:37:02]
<Salamandar> le lien lui-même
[08:37:15]
<Salamandar> etc/resolvconf/resolv.conf
[08:40:22]
<rodinux> Ok, en redémarrant je n'ai plus de `/etc/resolv.conf`
[08:42:53]
<rodinux> aaargh...
[08:46:13]
<rodinux> zut !!
[08:46:13]
<rodinux> ls -lah /etc/resolv*
-rw-r--r-- 1 root root 551 Oct 22 10:45 /etc/resolv.dnsmasq.conf
/etc/resolvconf:
total 24K
drwxr-xr-x 5 root root 4.0K Oct 22 10:37 .
drwxr-xr-x 96 root root 4.0K Oct 22 10:31 ..
-rw-r--r-- 1 root root 878 Jan 6 2021 interface-order
drwxr-xr-x 2 root root 4.0K Oct 22 09:57 resolv.conf.d
drwxr-xr-x 2 root root 4.0K Oct 22 09:57 update.d
drwxr-xr-x 2 root root 4.0K Jun 30 06:09 update-libc.d
[08:47:05]
<Salamandar> Étrange
[08:47:13]
<Salamandar> bin du coup recrée le lien symbolique à la main peut-être
[08:47:33]
<Salamandar> mais vers /run/resolvconf/resolv.conf
[08:48:38]
<rodinux> Est-ce qu'il faudrait faire un `ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf` ?
[08:49:04]
<rodinux> ou `ln -s /run/resolvconf/resolv.conf /etc/resolv.conf`
[08:52:45]
<miro5001> Ce ne serait pas un vps ovh ? J'ai eu le même soucis. Je me rappelle l'avoir corrigé à la main. Créer ce qui n'existe pas, supprimer et créer le lien. Ça fait un peu plus d'un an
[08:54:21]
<rodinux> Ce n'est pas un vps de ovh, mais presque, car à partir d'une image cloud-init
[08:55:40]
<rodinux> du coup je fait cela ? `ln -s /run/resolvconf/resolv.conf /etc/resolv.conf` ou cela `ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf` ? j'ai un doute ?
[08:56:47]
<rodinux> Le premier me renvoi cela après
[08:56:49]
<rodinux> root@yuno:~# ls -lah /etc/resolv*
lrwxrwxrwx 1 root root 27 Oct 22 10:55 /etc/resolv.conf -> /run/resolvconf/resolv.conf
-rw-r--r-- 1 root root 551 Oct 22 10:45 /etc/resolv.dnsmasq.conf
[08:57:07]
<rodinux> pas pareil tout de même...
[09:00:32]
<rodinux> pas pareil que `ls -lah /etc/resolv*
lrwxrwxrwx 1 root root 29 Sep 23 23:41 /etc/resolv.conf -> ../run/resolvconf/resolv.conf`
[09:03:49]
<rodinux> Du coup j'ai opter pour l'autre `ln -s ../run/resolvconf/resolv.conf /etc/resolv.conf`
[09:03:49]
<miro5001> https://forum.yunohost.org/t/diagnostic-warning-etc-resolv-conf-conflit-network-manager/30582/3?u=jarod5001
[09:06:41]
<rodinux> > <@miro5001:matrix.org> https://forum.yunohost.org/t/diagnostic-warning-etc-resolv-conf-conflit-network-manager/30582/3?u=jarod5001
Ah oui, c'est moi en plus qui propose cela !! mais dans ce cas ça ne va pas, je n'ai pas de dossier `/etc/resolvconf/run/`...
[09:09:16]
<miro5001> En fait, j'aurai fait comme ça
rm /etc/resolv.conf
rm /etc/resolvconf/run/resolv.conf
touch /etc/resolv.conf
echo "nameserver 127.0.0.1" > /etc/resolvconf/run/resolv.conf
ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf
[09:09:37]
<rodinux> ceci n'existe pas sur cette instance `/etc/resolvconf/run/resolv.conf`
[09:09:37]
<miro5001> Ah c'est une v12 !
[09:09:51]
<Salamandar> ça n'existe pas
[09:09:51]
<Salamandar> mais encore une fois je comprends pas pourquoi tu parles de /etc/resolvconf/run…
[09:10:15]
<rodinux> le dossier de resolvconf se trouve dans /run/resolvconf/resolv.conf et non ce n'est pas une v12
[09:10:35]
<rodinux> > <@Salamandar:matrix.org> mais encore une fois je comprends pas pourquoi tu parles de /etc/resolvconf/run…
Ben sur certaines instance j'ai bien cela
[09:11:21]
<rodinux> ls -lah /etc/resolvconf/
total 32K
drwxr-xr-x 5 root root 4.0K Oct 19 2022 .
drwxr-xr-x 120 root root 12K Oct 22 11:00 ..
-rw-r--r-- 1 root root 878 Jan 6 2021 interface-order
drwxr-xr-x 2 root root 4.0K Oct 19 2022 resolv.conf.d
lrwxrwxrwx 1 root root 15 Mar 19 2021 run -> /run/resolvconf
drwxr-xr-x 2 root root 4.0K Oct 19 2022 update.d
drwxr-xr-x 2 root root 4.0K Jul 2 22:43 update-libc.d
[09:12:54]
<Salamandar> Chelou. Bon en tout cas là c'est un symlink vers /run
[09:12:56]
<rodinux> Du coup c'est ça l'astuce, de créer un lien vers /run
[09:12:58]
<rodinux> d'où le message du diagnostic `Le fichier /etc/resolv.conf doit être un lien symbolique vers /etc/resolvconf/run/resolv.conf lui-même pointant vers 127.0.0.1 `
[09:13:03]
<rodinux> C'est ce qui devrait être logique...
[09:16:41]
<rodinux> Du coup à la main il faudrait d'abord créer ce lien symbolique `ln -s /run/resolvconf /etc/resolvconf/run` ?
[09:17:49]
<rodinux> puis ensuite `ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf` ??
[09:22:25]
<rodinux> Après dans un `cloud-init` j'ai trouvé cette astuce pour garder que
```
```
[09:22:49]
<rodinux> Après dans un `cloud-init` j'ai trouvé cette astuce pour garder que
nameserver 127.0.0.1
search local
[09:23:41]
<rodinux> commenter dans le fichier `/run/resolvconf/interface/lo.inet` les `nameserver`
[16:37:51]
<Aleks (he/him/il/lui)> and did you double check that the file size make somewhat sense between the original file and the copied file ?
[16:38:02]
<Aleks (he/him/il/lui)> not sure why it can't obtain the info json then
[16:38:02]
<Aleks (he/him/il/lui)> hmmokay so the size seems to match ?
[16:38:02]
<Aleks (he/him/il/lui)> but you could also copy that file
[16:38:18]
<Aleks (he/him/il/lui)> i suppose nope, it's in fact meant to be different, since that's the size of the raw content
[16:50:21]
<onner1964> I'm trying to restore a backup but I'm encountering a problem. To save disk space I upload the backups to a remote server using Rclone. I've downloaded the two necessary files (.tar and .info.json) but I'm getting an error message.
[16:50:21]
<onner1964> Error: "500"
Action: "PUT" /yunohost/api/backups/wallabag2-pre-upgrade1/restore
Error message:
Could not load info for archive '/home/yunohost.backup/archives/wallabag2-pre-upgrade1.tar'… The info.json file cannot be retrieved (or is not a valid json).
[16:50:21]
<onner1964> Hey guys!
[16:50:22]
<onner1964> wait...
[16:50:22]
<onner1964> rclone ls remote:
2350888960 wallabag2-pre-upgrade1.tar
/home/yunohost.backup/archives$ ls -l
-rw-rw-rw- 1 root root 319 Oct 22 02:32 wallabag2-pre-upgrade1.info.json
-rw-rw-rw- 1 root root 2350888960 Oct 20 21:08 wallabag2-pre-upgrade1.tar
[16:50:22]
<onner1964> .info.json file does not have equal sizes:
rclone ls
314 wallabag2-pre-upgrade1.info.json
[16:50:22]
<onner1964> I didn't think to check. I'll do it now...
[16:50:23]
<onner1964> now the file is the same size.
-rw-rw-rw- 1 user user 314 Oct 20 21:06 wallabag2-pre-upgrade1.info.json
-rw-rw-rw- 1 root root 2350888960 Oct 20 21:08 wallabag2-pre-upgrade1.tar
[16:50:23]
<onner1964> I will download it again.
[16:50:23]
<onner1964> cat wallabag2-pre-upgrade1.info.json
{"description": "test", "created_at": 1729468203, "size": 2326668137, "size_details": {"system": {}, "apps": {"wallabag2": 2326667333}}, "apps": {"wallabag2": {"version": "2.5.4~ynh4", "name": "Wallabag", "description": "Save and classify articles. Read them later"}}, "system": {}, "from_yunohost_version": "11.2.31"}
[16:50:24]
<onner1964> I will give up because the file is corrupted. Somewhere in the upload or download process the file is being corrupted.
[16:50:24]
<onner1964> tar x0f wallabag2-pre-upgrade1.tar &> /dev/null; echo $?
64
tar -tf wallabag2-pre-upgrade1.tar &> /dev/null; echo $?
2
[16:50:24]
<onner1964> Does the size specified in the .info.json file need to be the same as that specified in the ls -l command?
[16:50:25]
<onner1964> What a shame! My backup strategy failed. 😅
[22:22:51]
<cefaleia> it's possible to send email from another vps using my yunohost smtp server? do i need to set up a relay on yunohost or add my other vps ip to yunohost postfix?
[22:34:19]
<Salamandar> maybe the easiest would be to add the other vps' domain on your yunohost
[22:34:49]
<cefaleia> it's configured on cloudflare
[22:35:38]
<Salamandar> i mean just run add the domain in the yunohost config
[22:35:49]
<Salamandar> That way, yunohost will add all the email config required
[22:36:01]
<Salamandar> and the other vps will just have to login via smtp to your yunohost server
[22:36:42]
<cefaleia> and i dont need to change nameservers?
[22:37:17]
<Salamandar> you'll just have to configure the mail config on your registrar (DKIM, Dmarc, mailkey)
[22:37:30]
<Salamandar> but the rest can keep pointing on your other vps
[22:37:55]
<Salamandar> if you want to receive email that might be another story, either you want the email to arrive on your VPS, or on your yunohost
[22:40:42]
<cefaleia> i have set email routing in cloudflare for the domain of the other vps just to receive and forward a general email. its best to remove this configuration and set up mx entries to my yunohost server?
[22:42:38]
<Salamandar> well hmmm that depends on your use case i guess
[22:42:51]
<Salamandar> sorry, gotta sleep, but i'll be back tomorrow
[22:43:43]
<cefaleia> ok thanks