[03:17:00]
<satadaes> anyone know if it's possible to use say YH Install one (all ports open to public and with working properly) to point to another YH install that obviously doesnt have it's ports forwarded so that they both work?
[03:17:00]
<tituspijean> It looks like a bug. We have put exceptions in the URL conflicts detection that should ignore the .well-known addresses.
I cannot look into it right now (sleep required), but I will tomorrow morning.
Can you also include the nextcloud upgrade log?
[05:49:09]
<lohangX> Hello, how long will YuNoHost 11 be supported? I have a VPS that I'd rather keep on 11 until the VPS subscription ends in about 5 months. And do a clean install of 12 on the new server to which I'll be migrating afterward.
[06:54:43]
<satadaes> weird error when I try to change to IPV4 only in settings https://paste.yunohost.org/ijalixozeh, any ideas?
[07:37:00]
<tituspijean> > <lohangX> Hello, how long will YuNoHost 11 be supported? I have a VPS that I'd rather keep on 11 until the VPS subscription ends in about 5 months. And do a clean install of 12 on the new server to which I'll be migrating afterward.
If you look at the deprecation or end of support announcements on the forum, you should be covered for these 5 months. (e.g. https://forum.yunohost.org/t/end-of-life-for-buster-yunohost-4-x/28235)
[07:42:58]
<tituspijean> > <@satadaes:matrix.org> anyone know if it's possible to use say YH Install one (all ports open to public and with working properly) to point to another YH install that obviously doesnt have it's ports forwarded so that they both work?
It generally depends on the apps to be served by server 1, but look at the Redirect app in proxy mode.
Emails could be forwarded too I think. Look at the secondary MX and smtp relay settings.
[07:43:39]
<tituspijean> > <@satadaes:matrix.org> weird error when I try to change to IPV4 only in settings https://paste.yunohost.org/ijalixozeh, any ideas?
What's your YunoHost version?
[08:11:11]
<lohangX> > If you look at the deprecation or end of support announcements on the forum, you should be covered for these 5 months. (e.g. https://forum.yunohost.org/t/end-of-life-for-buster-yunohost-4-x/28235)
Thanks tituspijean ! This is good to know, so I can plan things early
[08:57:12]
<hercut> bonjour à tous,
Salamandar j'ai vu sur le forum ue tu avais eu le souci avec `[ERROR] Service supervisor is auto-restart :("`
J'ai tenté la commande donné
`apt install supervisor`
Mais je recois encore un mail de diagnosis me donnant l'erreur.
As tu une idée ?
[08:58:58]
<Salamandar> hmm ??
[08:58:58]
<Salamandar> euh
[08:59:09]
<Salamandar> tu as vu ça où ?
[08:59:24]
<Salamandar> mais surtout si tu as un message de diag, c'es tque c'est installé
[08:59:58]
<hercut> https://forum.yunohost.org/t/le-service-supervisor-est-dead/12242/2
[08:59:58]
<hercut> Ahah ca date un peu ^^
[08:59:58]
<hercut> > <@Salamandar:matrix.org> mais surtout si tu as un message de diag, c'es tque c'est installé
Alors oui surement, mais je ne sais pas d'ou sa sort ...
[09:00:14]
<Salamandar> tu as eu aussi l'erreur "supervisorctl commande non trouvée" ?
[09:04:14]
<hercut> ```
[ERROR] Service supervisor is auto-restart :(
- 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 supervisor' and 'yunohost service log supervisor').
```
[10:26:49]
<chankalan> Si jamais c'est utile : pendant une upgrade de yunohost11 vers 12, php7.3-fpm n'était pas totalement désinstallé et ça bloquait l'upgrade. "sudo apt remove php7.3-fpm" m'a sauvé, l'upgrade a pu terminer
[10:37:01]
<chankalan> J'ai retrouvé rspamd depuis les apps, la nouvelle interface utilisateur est bien chouette, tout semble bien fonctionner :o) \o/
[11:00:39]
<isAAAc> > <@hercut:matrix.org> ```
> [ERROR] Service supervisor is auto-restart :(
> - 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 supervisor' and 'yunohost service log supervisor').
> ```
supervisor status
[11:00:40]
<isAAAc> ?
[11:01:41]
<isAAAc> s'il y en a un en failed,
supervisor restart <nom_du_job_en_question>
[11:01:52]
<isAAAc> puis à nouveau supervisor status
[11:02:20]
<isAAAc> s'il est encore failed, faut aller checker les logs pour piger pourquoi, dans /var/log/supervisor probablement
[11:02:29]
<isAAAc> hercut: ^
[11:03:22]
<isAAAc> ou les commandes passant par yunohost qu idoivent faire pareil avec possiblement des hooks autour
[11:03:59]
<isAAAc> yunohost service status supervisor
[12:13:32]
<satadaes> latest bookworm
[13:57:41]
<hercut> > yunohost service status supervisor
configuration: unknown
description: Supervisor daemon for pixelfed
last_state_change: 2024-11-22 13:56:42
start_on_boot: enabled
status: auto-restart
[13:57:52]
<hercut> systemctl status supervisor
```
● supervisor.service - Supervisor process control system for UNIX
Loaded: loaded (/lib/systemd/system/supervisor.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-11-22 13:56:42 UTC; 13s ago
Docs: http://supervisord.org
Process: 404687 ExecStart=/usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf (code=exited, status=2)
Main PID: 404687 (code=exited, status=2)
CPU: 231ms
```
[13:59:57]
<hercut> > s'il y en a un en failed,
> supervisor restart <nom_du_job_en_question>
DOnc si je comprend bien ca serait pixelfed qui demande ca ?
Bizarre que j'ai encore le souci aujourd'hui sachant que je l'ai desinstallé hier, car j'avais vu 2 ou 3 posts parlant de cette application dans le forum
[14:01:51]
<isAAAc> hercut: pardon , je me suis mal exprimé
que dit `supervisorctl status` pour interroger supervisor directement
[14:02:16]
<isAAAc> c'est là que tu dois voir si un job est en failed
[14:02:34]
<hercut> > hercut: pardon , je me suis mal exprimé
> que dit `supervisorctl status` pour interroger supervisor directement
unix:///var/run/supervisor.sock no such file
[14:03:44]
<isAAAc> `supervisorctl start` ?
[14:03:51]
<hercut> je met sudo devant ?
[14:04:08]
<hercut> > `supervisorctl start` ?
unix:///var/run/supervisor.sock no such file
[14:05:01]
<isAAAc> ouep, systemctl restart supervisor.service
[14:05:30]
<isAAAc> puis systemctl status supervisor.service
[14:05:39]
<Aleks (he/him/il/lui)> Is pixelfed even installed on your machine ? Supervisor shouldnt be there in the first place... It's an old mechanism which we dont recommend to use, its redundant with systemctl
[14:05:39]
<isAAAc> puis supervisorctl status
[14:06:00]
<hercut> > ouep, systemctl restart supervisor.service
```
Failed to execute /usr/bin/pkttyagent: No such file or directory
Failed to restart supervisor.service: Access denied
See system logs and 'systemctl status supervisor.service' for details.
```
[14:06:00]
<isAAAc> oui avec sudo
[14:06:41]
<Aleks (he/him/il/lui)> (Hmpf apparently the app is still using supervisor)
[14:07:05]
<isAAAc> root@krashboyz:~# supervisorctl status
pixelfed-horizon FATAL Exited too quickly (process log may have details)
j'ai la meme chose en fait ^^
[14:07:05]
<isAAAc> Aleks (he/him/il/lui): ^
[14:07:20]
<hercut> > ouep, systemctl restart supervisor.service
il me semble que c'est la commande que j'avais fait, trouvé sur le forum sur un post de Salamandar
[14:07:31]
<hercut> > puis systemctl status supervisor.service
```
● supervisor.service - Supervisor process control system for UNIX
Loaded: loaded (/lib/systemd/system/supervisor.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2024-11-22 14:06:26 UTC; 16s ago
Docs: http://supervisord.org
Process: 406720 ExecStart=/usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf (code=exited, status=2)
Main PID: 406720 (code=exited, status=2)
CPU: 235ms
```
[14:07:53]
<hercut> > oui avec sudo
```
sudo supervisorctl status
unix:///var/run/supervisor.sock no such file
```
[14:08:10]
<isAAAc> ````
root@krashboyz:~# supervisorctl status
pixelfed-horizon FATAL Exited too quickly (process log may have details)
root@krashboyz:~# supervisorctl restart pixelfed-horizon
pixelfed-horizon: ERROR (not running)
pixelfed-horizon: started
root@krashboyz:~# supervisorctl status
pixelfed-horizon RUNNING pid 3720818, uptime 0:00:07
```
[14:08:37]
<isAAAc> hercut: faut comprendre pourquoi ton supervisor ne veut pas se lancer
[14:09:04]
<hercut> > hercut: faut comprendre pourquoi ton supervisor ne veut pas se lancer
y en a t'il besoin ? sachant que j'ai supprimer pixelfed ?
[14:10:00]
<isAAAc> supervisor peut etre utilisé pour d'autres chose que pixelfed, si tu es certain qu'il n'y a plus de job qui devrait tourner avec oui, je l'aurai purgé
[14:10:16]
<hercut> > supervisor peut etre utilisé pour d'autres chose que pixelfed, si tu es certain qu'il n'y a plus de job qui devrait tourner avec oui, je l'aurai purgé
Aucune idée :/
[14:12:03]
<isAAAc> tu as quoi dans `/etc/supervisor/conf.d` si tu `ls` dessus ça dit quoi ?
[14:12:47]
<isAAAc> si c'est vide: `apt purge supervisor`
si c'est pas vide, c'est que autre chose utilise encore supervisor
[14:14:46]
<hercut> > tu as quoi dans `/etc/supervisor/conf.d` si tu `ls` dessus ça dit quoi ?
pixelfed-horizon.conf
[14:15:20]
<hercut> pixelfed aurais laisser des choses alors que je l'ai supprimer ?
[14:16:01]
<isAAAc> > <@hercut:matrix.org> pixelfed aurais laisser des choses alors que je l'ai supprimer ?
ouep ça arrive que la desinstalle d'une appli laisse des crottes derrière :)
[14:17:10]
<hercut> > ouep ça arrive que la desinstalle d'une appli laisse des crottes derrière :)
enfin la c'est plus une crotte, ca gene un peu, bien que semblerai que ca soit pas ultra grave non plus, si j'ai bien compris :)
[14:17:19]
<isAAAc> tu as bien désintallé pixelfed de ton ynh ?
[14:17:25]
<hercut> > tu as bien désintallé pixelfed de ton ynh ?
oui
[14:17:45]
<hercut> mais j'ai eu pas mal de souci avec la migration et que le serveur est vieux alors peut etre que ca à laissé des trace
[14:17:52]
<isAAAc> ok, oui donc pas d'effet de bord que supervisor plante, rien d'autre ne semble l'utiliser
[14:18:09]
<isAAAc> apt purge supervisor et hop ça devrait rentrer dans l'ordre
[14:19:05]
<hercut> > apt purge supervisor et hop ça devrait rentrer dans l'ordre
ok :) Comment on peut demander a diagnosis pouvoir si j'ai encore l'erreur ?
[14:19:21]
<isAAAc> > <@hercut:matrix.org> mais j'ai eu pas mal de souci avec la migration et que le serveur est vieux alors peut etre que ca à laissé des trace
oui en général c'est ça , mon serveur est un vieux ynh et j'ai des relicats de temps en temps de vieilles pratiques/intégrations qui n'avaient probablement pas été prises en compte car on peut pas penser à tout tout le temps ;)
[14:19:23]
<hercut> ah
```
dpkg: warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed
dpkg: warning: while removing supervisor, directory '/etc/supervisor/conf.d' not empty so not removed
```
[14:20:26]
<hercut> > oui en général c'est ça , mon serveur est un vieux ynh et j'ai des relicats de temps en temps de vieilles pratiques/intégrations qui n'avaient probablement pas été prises en compte car on peut pas penser à tout tout le temps ;)
:) j'ai pas de souci avec ca, je comprend totallement ! Et la chance qu'on a c'est qu'il y a des gens actif et reactif c'est vraiment top ! Et encore merci à tous les gens qui m'aident a chaque fois
[14:20:40]
<isAAAc> `rm -Rf /var/log/supervisor /etc/supervisor/conf.d`
[14:21:10]
<isAAAc> avec sudo les deux si tu n'es pas en root
[14:21:34]
<isAAAc> puis relance un diag : `yunohost diagnosis run`
[14:22:50]
<hercut> je pense que c'est l'erreur que j'ai tout le temps
`[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.`
recuperé sur un des dernier mail
[14:24:11]
<hercut> ```
Warning: Found 1 item(s) that could be improved for Base system.
Success! Everything looks OK for Internet connectivity!
Success! Everything looks OK for DNS records! (+ 1 ignored issue(s))
Success! Everything looks OK for Ports exposure!
Success! Everything looks OK for Web!
Success! Everything looks OK for Email! (+ 2 ignored issue(s))
Error: Failed to get status information via dbus for service supervisor, systemctl didn't recognize this service ('NoSuchUnit').
Warning: Found 1 item(s) that could be improved for Services status check.
Success! Everything looks OK for System resources!
Success! Everything looks OK for System configurations!
Success! Everything looks OK for Applications!
Warning: To see the issues found, you can go to the Diagnosis section of the webadmin, or run 'yunohost diagnosis show --issues --human-readable' from the command-line.
```
[14:25:37]
<hercut> j'ai fait yunohost diagnosis show --issues --human-readable
[14:25:46]
<hercut> et j'ai encore supervisor
[14:25:57]
<hercut> ```
=================================
Base system (basesystem)
=================================
[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.
=================================
Services status check (services)
=================================
[WARNING] Service supervisor 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 supervisor' and 'yunohost service log supervisor').
```
[14:37:26]
<isAAAc> tu peux tenter `sudo apt install supervisor && sudo apt purge supervisor && yunohost diagnosis show --issues --human-readable` voir si ça change
[14:37:44]
<isAAAc> aucun risque puisque rien n'utilise supervisor ;)
[14:37:57]
<hercut> ok :)
[14:38:27]
<hercut> Je pose la question vite fait hors sujet , pour les
```
"[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.
"
```
Y a rien a faire ?
[14:38:53]
<isAAAc> systemctl reset-failed
[14:39:17]
<isAAAc> puis refais un diag
[14:39:38]
<hercut> ```
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
supervisor-doc
The following NEW packages will be installed:
supervisor
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 311 kB of archives.
After this operation, 1,748 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main amd64 supervisor all 4.2.5-1 \[311 kB\]
Fetched 311 kB in 0s (3,118 kB/s)
Selecting previously unselected package supervisor.
(Reading database ... 59746 files and directories currently installed.)
Preparing to unpack .../supervisor\_4.2.5-1\_all.deb ...
Unpacking supervisor (4.2.5-1) ...
Setting up supervisor (4.2.5-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/supervisor.service → /lib/systemd/system/supervisor.service.
Processing triggers for man-db (2.11.2-2) ...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
supervisor\*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1,748 kB disk space will be freed.
Do you want to continue? \[Y/n\] y
(Reading database ... 59895 files and directories currently installed.)
Removing supervisor (4.2.5-1) ...
Processing triggers for man-db (2.11.2-2) ...
(Reading database ... 59750 files and directories currently installed.)
Purging configuration files for supervisor (4.2.5-1) ...
dpkg: warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed
Error: yunohost command must be run as root or with sudo.
```
[14:40:02]
<isAAAc> si c'est encore là, systemctl mask supervisor puis un diag, et là il ne devrait plus apparaitre en diag
[14:40:52]
<isAAAc> > <@hercut:matrix.org> ```
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Suggested packages:
> supervisor-doc
> The following NEW packages will be installed:
> supervisor
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 311 kB of archives.
> After this operation, 1,748 kB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian bookworm/main amd64 supervisor all 4.2.5-1 \[311 kB\]
> Fetched 311 kB in 0s (3,118 kB/s)
>
> Selecting previously unselected package supervisor.
> (Reading database ... 59746 files and directories currently installed.)
> Preparing to unpack .../supervisor\_4.2.5-1\_all.deb ...
> Unpacking supervisor (4.2.5-1) ...
> Setting up supervisor (4.2.5-1) ...
> Created symlink /etc/systemd/system/multi-user.target.wants/supervisor.service → /lib/systemd/system/supervisor.service.
> Processing triggers for man-db (2.11.2-2) ...
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be REMOVED:
> supervisor\*
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> After this operation, 1,748 kB disk space will be freed.
> Do you want to continue? \[Y/n\] y
> (Reading database ... 59895 files and directories currently installed.)
> Removing supervisor (4.2.5-1) ...
> Processing triggers for man-db (2.11.2-2) ...
> (Reading database ... 59750 files and directories currently installed.)
> Purging configuration files for supervisor (4.2.5-1) ...
> dpkg: warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed
> Error: yunohost command must be run as root or with sudo.
> ```
oui j'ai oublié sudo devant le diag
[14:41:23]
<isAAAc> sudo yunohost diagnosis show --issues --human-readable
[14:43:10]
<hercut> > sudo yunohost diagnosis show --issues --human-readable
```
=================================
Base system (basesystem)
=================================
[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.
=================================
Services status check (services)
=================================
[WARNING] Service supervisor 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 supervisor' and 'yunohost service log supervisor').
```
[14:45:36]
<rodinux> Il y a eu une coquille plus haut
```
dpkg: warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed
Error: yunohost command must be run as root or with sudo.
```
[15:13:34]
<thibault> Hello est-ce que certains depuis la migration vers yunohost 12 ont des difficultés à maintenir une redirection de port ? Merci d'avance
[15:36:03]
<hercut> > <@rodinux:matrix.org> Il y a eu une coquille plus haut
> ```
> dpkg: warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed
> Error: yunohost command must be run as root or with sudo.
> ```
Il fallait faire autrement ?
[16:16:39]
<rodinux> Ben là tu as toujours un soucis de `service unknow` et dans la commande `warning: while removing supervisor, directory '/var/log/supervisor' not empty so not removed`
[16:19:05]
<rodinux> Est-ce qu'il existe encore une conf ? `ls /etc/systemd/system/`
[16:20:20]
<rodinux> Est-ce que ce serait pas une autre application qui a besoin de ce service ??
[18:29:49]
<Klorydryk> Bonjour, pouvez-vous me dire au bout de combien de temps la config est-elle mise à jour par la commande
`yunohost app setting redirect protect_against_basic_auth_spoofing -v false` ?
[18:32:05]
<Aleks (he/him/il/lui)> environ 50 millisecondes ?
[18:32:25]
<Aleks (he/him/il/lui)> ah non pardon si tu parles de la conf ssowat il faut lancer `yunohost app ssowatconf`
[19:11:29]
<shortdom> Sorry, the log I posted is the only log I know of. It's the log Yunohost provides when I try to upgrade Nextcloud, and it's the one it recommend including with any bug report. If there's a different log you need, please tell me where to look for it.
I can say that it's an old problem that has existed since at least Yunohost 11. Because of that, I know it's very reproducible, as I've run into it several times over the years on different installs.
[19:20:47]
<Klorydryk> > <@Alekswag:matrix.org> ah non pardon si tu parles de la conf ssowat il faut lancer `yunohost app ssowatconf`
merci !
[19:33:50]
<shortdom> > <@csolisr:azkware.net> Synapse is generally expected to run as the root *domain.tld*, from what I remember
I did read that's the most secure way of running Synapse, but I really want to run Nextcloud on my root. That way my email is user@domain.tld, my Nextcloud user is user@domain.tld, my Matrix user is @user:domain.tld, and even my CalDAV/CardDAV (on Nextcloud) account reads as user@domain.tld. It's a little thing, but I get joy out of it every day.
[22:42:12]
<orhtej2> > <@shortdom:matrix.org> I did read that's the most secure way of running Synapse, but I really want to run Nextcloud on my root. That way my email is user@domain.tld, my Nextcloud user is user@domain.tld, my Matrix user is @user:domain.tld, and even my CalDAV/CardDAV (on Nextcloud) account reads as user@domain.tld. It's a little thing, but I get joy out of it every day.
You can do that by changing server name to domain.tld while running the server on sub.domain.tld, this leaks only when configuring the client