[01:20:48]
<Eda> > why not Matrix tho
Because of all the metadata pb that the servers have and pass to each other
[10:19:37]
<ynhuser> bonjour, je ne peux plus entrer dans l'administration de yunohost
[10:19:55]
<ynhuser> je tape mes identifiants mais le bouton validé reste inactif
[10:37:54]
<Aleks (he/him/il/lui)> ça ressemble à l'API YunoHost qui serait down ... est-ce que tu peux te connecter en SSH sur le serveur ?
[12:41:40]
<Christopher> > <@big_diggity:matrix.org> I am trying to create a couple of backups. For some reason, my Yunohost web portal has become very slow. I was able to get a back up of Pixelfed, Peertube, and Collabora. I downloaded those backups and then deleted their archives. I performed a back up of Hubzilla and it took several hours to complete. I downloaded it and deleted the archive. Now I am trying to backup Misskey. The Yunohost web portal is running very slow. SSH into the server seems to be fast. I have over 100gb is storage and it says the archive will be around 23gb. When I try to back up Misskey using the web portal, it gives a 504 Timeout. When I try to back up using the command line, it also fails. I have tried restarting the server. I have tried to restart the Misskey service. I have tried restarting the mysql and the postresql services. Misskey seems to be working as it should when I visit the site. Below is the log it generates when failing. What else can I try? I won't be available again until later today, but I would like the minds thinking to get whoever can help. Much appreciated. https://paste.yunohost.org/raw/erejetafax
Anybody have a suggestion on this? Also, when using the web portal to check the backup folder it takes hours to populate anything and when it does, it's a 504 timeout error.
[13:08:34]
<Chatpitaine Caverne> Not sure, but when a backup failed and there is only a .tar file and not the .json file, it takes a long time to open the backup list folder.
Maybe check that via SSH ?
[13:09:25]
<Chatpitaine Caverne> Christopher: Not sure, but when a backup failed and there is only a .tar file and not the .json file, it takes a long time to open the backup list folder.
Maybe check that via SSH ?
[13:14:22]
<Christopher> > <@chatpitaine:cirkau.art> Christopher: Not sure, but when a backup failed and there is only a .tar file and not the .json file, it takes a long time to open the backup list folder.
> Maybe check that via SSH ?
OK. I'll look at that again. I noticed yesterday when using ssh, that there are multiple 20+gb archives, so I assume they are the app I've been trying to backup. There were a couple of .json files in there, but I don't know if they were new or not.
[13:19:54]
<Chatpitaine Caverne> Christopher: The .tar (and/or .tar.gz) and the .json go by couple (or triple) with the same beginning of name. If a .tar (and/or .tar.gz) doesn't have it's own .json file then, this symptom appears (for me at least).
[13:20:59]
<Christopher> OK. So, what do I do if the .json file isn't being generated?
[13:22:19]
<Chatpitaine Caverne> Cause it's broken backup, I delete the .tar and/or .tar.gz (or if you prefer, you can move them somewhere else).
[13:23:30]
<Chatpitaine Caverne> And since the possibility of compressed backup is opened in Yunohost, for long and big backups, I get a 504 also, but the backup continue and can finish normally usually.
[13:25:21]
<Christopher> OK. I'm not doing the extra compressed backup. I'll check this info out and report back when I can. Thanks so much!
[15:12:41]
<Westbam> salut, des utilisateurs de seafile par ici ?? je teste rapidement ce service. j'ai configuré un ndd dédié, cela marche bien à partir d'un navigateur, par contre pas possible de connecter un client dessus, que ce soit android ou windows .... est-il necessaire d'ouvrir un port en particulier pour que cela marche ?
[15:27:34]
<Chatpitaine Caverne> I don't use Seafile, but it seem's yes it uses ports :
```
#ynh_script_progression --message="Finding available ports..."
seahub_port=$(ynh_find_port --port 8000)
fileserver_port=$(ynh_find_port --port 8082)
webdav_port=$(ynh_find_port --port 8080)
```
From the github of the ynh-app (https://github.com/YunoHost-Apps/seafile_ynh/blob/master/scripts/install)
````
[15:30:31]
<pavezzi> I was wondering what could be the reason when after upgrading at some point I no longer receive mail to the aliases "root" and "abuse"? How can one fix this?
[15:34:16]
<Aleks (he/him/il/lui)> did you read the 11.1 release note ..?
[15:35:40]
<Chatpitaine Caverne> Westbam: Excuse, j'ai répondu en anglais sans m'en rendre compte. Désolé, je ne sais plus où j'en suis avec les langues, on dirait.
[15:58:46]
<pavezzi> Aleks (he/him/il/lui), having read the releasenote I am not sure if the included information is sufficient to alleviate my problem
[15:59:17]
<Aleks (he/him/il/lui)> soooo can you confirm that the admin group migration ran properly ?
[15:59:36]
<Aleks (he/him/il/lui)> and that your user is in the admins group ?
[16:04:16]
<pavezzi> Aleks (he/him/il/lui), the actual problem is that adding aliases for my secondary domain fails for anything starting with "abuse", which is kind of essential for me
[16:06:17]
<Westbam> > <@chatpitaine:cirkau.art> Westbam: Excuse, j'ai répondu en anglais sans m'en rendre compte. Désolé, je ne sais plus où j'en suis avec les langues, on dirait.
t'inquietes pas de souci, j'avais compris 🙂
[16:06:55]
<Aleks (he/him/il/lui)> then I would recommend adding the abuse@ alias to the admins group using `yunohost user group --add-mailalias abuse@domain.tld`
[16:10:01]
<pavezzi> that has got to have a syntax error there
[16:11:43]
<pavezzi> but thank you Aleks (he/him/il/lui), got it fixed with: yunohost user group add-mailalias admins abuse@domain.tld
[16:14:45]
<pavezzi> tested and working, merci beaucoup, kiitos, thanks & danke schön
[16:16:51]
<ynhuser4> J'ai un message d'erreur "Le service uwsgi-app@searx est failed :-("
[16:17:03]
<ynhuser4> https://paste.yunohost.org/xuzuzojezo
[16:18:39]
<ynhuser4> je ne trouve pas la réponse et toute mes tentatives de relance ou redémarrage sont vaines
[16:19:36]
<ynhuser4> merci de votre aide
[16:21:43]
<Aleks (he/him/il/lui)> ```
chdir() to /opt/yunohost/searx/searx/
chdir(): No such file or directory [core/uwsgi.c line 2625]
```
apriori `/opt/yunohost/searx` a disparu mais difficile d'en savoir plus sans l'histoire récente de ton app ...
[16:25:45]
<ynhuser4> Ca a commencé a bugger après une mise à jour yunohost et appli
[16:32:42]
<ynhuser91> je reprend avec ce pseudo, ma session a planté
[16:33:27]
<ynhuser91> "/opt/yunohost/searx/" existe mais pas "/opt/yunohost/searx/searx/"
[16:33:51]
<ynhuser91> et je ne sais pas pourquoi
[16:44:21]
<Aleks (he/him/il/lui)> et /opt/yunohost/searx/ contiens des trucs ?
[16:45:23]
<ynhuser91> bin include lib lib64 pyvenv.cfg share
[16:47:52]
<Aleks (he/him/il/lui)> de ce que je vois dans les scripts de l'app, le dossier searx devrait bel et bien exister ... est-ce que tu peux partager le log d'upgrade de l'app
[17:02:43]
<ynhuser91> Pas certain ou le trouver
[17:07:18]
<ynhuser91> je n'ai que ça https://paste.yunohost.org/siminawoti
[17:16:40]
<Aleks (he/him/il/lui)> dans la webadmin > Outils > Journaux > tu devrais trouver la mention de ta mise à jour de l'app
[17:16:54]
<Aleks (he/him/il/lui)> puis gros bouton vers "Partager les logs avec Yunopaste"
[17:17:31]
<ynhuser91> https://paste.yunohost.org/raw/isiwihamer
[17:17:38]
<ynhuser91> merci
[17:25:54]
<Aleks (he/him/il/lui)> mouarf ben je capte pas, y'a rien l'air d'anormal ...
[17:26:37]
<ynhuser91> ok merci d'avoir regardé
[19:42:09]
<olivier[m]> hello à tous ; j'ai un cryptpad un peu cassé depuis une mise à jour récente, ça dit ça : ``` - Mar 28 10:29:00 systemd[1]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:00 systemd[1]: Started CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:01 npm[23354]: npm does not support Node.js v8.17.0
- Mar 28 10:29:01 npm[23354]: You should probably upgrade to a newer version of node as we
- Mar 28 10:29:01 npm[23354]: can't make any promises that npm will work with this version.
- Mar 28 10:29:01 npm[23354]: You can find the latest version at https://nodejs.org/
- Mar 28 10:29:01 npm[23354]: /opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/npm.js:32
- Mar 28 10:29:01 npm[23354]: #unloaded = false
- Mar 28 10:29:01 npm[23354]: ^
- Mar 28 10:29:01 npm[23354]: SyntaxError: Invalid or unexpected token
- Mar 28 10:29:01 npm[23354]: at createScript (vm.js:80:10)
- Mar 28 10:29:01 npm[23354]: at Object.runInThisContext (vm.js:139:10)
- Mar 28 10:29:01 npm[23354]: at Module._compile (module.js:617:28)
- Mar 28 10:29:01 npm[23354]: at Object.Module._extensions..js (module.js:664:10)
- Mar 28 10:29:01 npm[23354]: at Module.load (module.js:566:32)
- Mar 28 10:29:01 npm[23354]: at tryModuleLoad (module.js:506:12)
- Mar 28 10:29:01 npm[23354]: at Function.Module._load (module.js:498:3)
- Mar 28 10:29:01 npm[23354]: at Module.require (module.js:597:17)
- Mar 28 10:29:01 npm[23354]: at require (internal/module.js:11:18)
- Mar 28 10:29:01 npm[23354]: at module.exports (/opt/node_n/n/versions/node/16.14.2/lib/node_modules/npm/lib/cli.js:22:15)
- Mar 28 10:29:01 systemd[1]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
- Mar 28 10:29:01 systemd[1]: cryptpad.service: Failed with result 'exit-code'.
```
[19:42:28]
<olivier[m]> * hello à tous ; j'ai un cryptpad un peu cassé depuis une mise à jour récente, ça dit ça : \`\`\` - Mar 28 10:29:00 systemd\[1\]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:00 systemd\[1\]: Started CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:01 npm\[23354\]: npm does not support Node.js v8.17.0
- Mar 28 10:29:01 npm\[23354\]: You should probably upgrade to a newer version of node as we
- Mar 28 10:29:01 npm\[23354\]: can't make any promises that npm will work with this version.
- Mar 28 10:29:01 npm\[23354\]: You can find the latest version at https://nodejs.org/
- Mar 28 10:29:01 npm\[23354\]: /opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/npm.js:32
- Mar 28 10:29:01 npm\[23354\]: #unloaded = false
- Mar 28 10:29:01 npm\[23354\]: ^
- Mar 28 10:29:01 npm\[23354\]: SyntaxError: Invalid or unexpected token
- Mar 28 10:29:01 npm\[23354\]: at createScript (vm.js:80:10)
- Mar 28 10:29:01 npm\[23354\]: at Object.runInThisContext (vm.js:139:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.\_compile (module.js:617:28)
- Mar 28 10:29:01 npm\[23354\]: at Object.Module.\_extensions..js (module.js:664:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.load (module.js:566:32)
- Mar 28 10:29:01 npm\[23354\]: at tryModuleLoad (module.js:506:12)
- Mar 28 10:29:01 npm\[23354\]: at Function.Module.\_load (module.js:498:3)
- Mar 28 10:29:01 npm\[23354\]: at Module.require (module.js:597:17)
- Mar 28 10:29:01 npm\[23354\]: at require (internal/module.js:11:18)
- Mar 28 10:29:01 npm\[23354\]: at module.exports (/opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/cli.js:22:15)
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Failed with result 'exit-code'.
```
[19:42:42]
<olivier[m]> * hello à tous ; j'ai un cryptpad un peu cassé depuis une mise à jour récente, ça dit ça :
``` - Mar 28 10:29:00 systemd\[1\]: Stopped CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:00 systemd\[1\]: Started CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:01 npm\[23354\]: npm does not support Node.js v8.17.0
- Mar 28 10:29:01 npm\[23354\]: You should probably upgrade to a newer version of node as we
- Mar 28 10:29:01 npm\[23354\]: can't make any promises that npm will work with this version.
- Mar 28 10:29:01 npm\[23354\]: You can find the latest version at https://nodejs.org/
- Mar 28 10:29:01 npm\[23354\]: /opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/npm.js:32
- Mar 28 10:29:01 npm\[23354\]: #unloaded = false
- Mar 28 10:29:01 npm\[23354\]: ^
- Mar 28 10:29:01 npm\[23354\]: SyntaxError: Invalid or unexpected token
- Mar 28 10:29:01 npm\[23354\]: at createScript (vm.js:80:10)
- Mar 28 10:29:01 npm\[23354\]: at Object.runInThisContext (vm.js:139:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.\_compile (module.js:617:28)
- Mar 28 10:29:01 npm\[23354\]: at Object.Module.\_extensions..js (module.js:664:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.load (module.js:566:32)
- Mar 28 10:29:01 npm\[23354\]: at tryModuleLoad (module.js:506:12)
- Mar 28 10:29:01 npm\[23354\]: at Function.Module.\_load (module.js:498:3)
- Mar 28 10:29:01 npm\[23354\]: at Module.require (module.js:597:17)
- Mar 28 10:29:01 npm\[23354\]: at require (internal/module.js:11:18)
- Mar 28 10:29:01 npm\[23354\]: at module.exports (/opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/cli.js:22:15)
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Failed with result 'exit-code'.
```
```
[19:43:00]
<olivier[m]> * hello à tous ; j'ai un cryptpad un peu cassé depuis une mise à jour récente, ça dit ça :
```- Mar 28 10:29:00 systemd\[1\]: Started CryptPad: Zero Knowledge realtime collaborative editor..
- Mar 28 10:29:01 npm\[23354\]: npm does not support Node.js v8.17.0
- Mar 28 10:29:01 npm\[23354\]: You should probably upgrade to a newer version of node as we
- Mar 28 10:29:01 npm\[23354\]: can't make any promises that npm will work with this version.
- Mar 28 10:29:01 npm\[23354\]: You can find the latest version at https://nodejs.org/
- Mar 28 10:29:01 npm\[23354\]: /opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/npm.js:32
- Mar 28 10:29:01 npm\[23354\]: #unloaded = false
- Mar 28 10:29:01 npm\[23354\]: ^
- Mar 28 10:29:01 npm\[23354\]: SyntaxError: Invalid or unexpected token
- Mar 28 10:29:01 npm\[23354\]: at createScript (vm.js:80:10)
- Mar 28 10:29:01 npm\[23354\]: at Object.runInThisContext (vm.js:139:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.\_compile (module.js:617:28)
- Mar 28 10:29:01 npm\[23354\]: at Object.Module.\_extensions..js (module.js:664:10)
- Mar 28 10:29:01 npm\[23354\]: at Module.load (module.js:566:32)
- Mar 28 10:29:01 npm\[23354\]: at tryModuleLoad (module.js:506:12)
- Mar 28 10:29:01 npm\[23354\]: at Function.Module.\_load (module.js:498:3)
- Mar 28 10:29:01 npm\[23354\]: at Module.require (module.js:597:17)
- Mar 28 10:29:01 npm\[23354\]: at require (internal/module.js:11:18)
- Mar 28 10:29:01 npm\[23354\]: at module.exports (/opt/node\_n/n/versions/node/16.14.2/lib/node\_modules/npm/lib/cli.js:22:15)
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Main process exited, code=exited, status=1/FAILURE
- Mar 28 10:29:01 systemd\[1\]: cryptpad.service: Failed with result 'exit-code'.```
[19:43:21]
<olivier[m]> y'a une mise à jour de node que j'aurais raté?
[20:05:54]
<Guillaume Bouzige> bizarre tu es passer de quel version vers quel version ?
[20:06:29]
<Guillaume Bouzige> tu peut soit faire une issue sur github ou un post sur le forum pour que je puisse suivre ton probleme car la tout de suite je ne peut pas regarder
[20:07:13]
<Guillaume Bouzige> (je maintien l'app cryptpad et ai effectué les recentes maj)
[21:32:43]
<ynhuser> any quick hint why user import from csv fails with an unexpected server-error? csv is same format as export
[21:33:13]
<ynhuser> tried with password and without. (trying to create new users)
[21:57:11]
<Aleks (he/him/il/lui)> no logs, no help ...
[23:26:28]
<carrabelloy[m]> # sudo fail2ban-client test
2023-03-29 22:51:53,690 fail2ban.configreader [132201]: ERROR No section: 'Definition'
2023-03-29 22:51:53,690 fail2ban.configreader [132201]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader [132201]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader [132201]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban.configreader [132201]: ERROR No section: 'Definition'
2023-03-29 22:51:53,691 fail2ban [132201]: ERROR Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?
root@............................ /.............. # sudo nano /etc/fail2ban/jail.conf
root@................................... /home/.......................... #
The problem is that it is a day later. They are probably sytag errors but I still do not know where. Although I set the log level to Dubag to learn more. In addition, I am every area through geagngen again. in these areas have # sudo grep -rl "\[definition\]" /etc/fail2ban/filter.d/ /etc/fail2ban/filter.d/yunohost.conf /etc/fail2ban/filter.d/postfix-sasl.conf /etc/fail2ban/filter.d/postfix-sasl.local root@darknight-coffee /home/..........# /etc/fail2ban/filter.d/yunohost.conf /etc/fail2ban/filter.d/postfix-sasl.conf /etc/fail2ban/filter.d/postfix-sasl.local root@............... /home/........ # don't know where the error is or points me out like to use a color Unkt or so. Can anyone give me a tip. or help. Or are there ready-made jails? Thanks if answer comes.