[01:58:35]
<Aleks (he/him/il/lui)> not much to do, your server probably ran out of RAM ... I see in our automatic tests that the install takes at least one good GB of RAM ... how much RAM do you have availabe ?
[01:58:35]
<Granite T. Rock> I would like to install NetData. However NetData froze and the whole server was unresponsive while installing. CPU and Disk usage maxed out. After about 25 minutes the server recovered on it's own. The NetData install shows in Yunohost control panel but just redirects me to the yunohost main login when I visit the URL. I'm not sure how to troubleshoot the next step. (ie. Should I click uninstall to remove what's there? Try to install again?) Thanks in advance!
Logs: https://paste.yunohost.org/raw/kekipowuci
[02:02:21]
<Granite T. Rock> > <@Alekswag:matrix.org> not much to do, your server probably ran out of RAM ... I see in our automatic tests that the install takes at least one good GB of RAM ... how much RAM do you have availabe ?
2 GB
[02:02:22]
<Aleks (he/him/il/lui)> is it the total RAM on your server, or the *actually free/available* RAM ?
[02:06:44]
<Granite T. Rock> Ironically that was one of the reasons I was installing netdata. VPS host doesn't show how much RAM I'm using.
[02:08:58]
<Aleks (he/him/il/lui)> Yunohost's diagnosis will tell you how much ram is free/available at the bottom in "system resources"
[02:08:59]
<Granite T. Rock> I think I can temporarily upgrade the RAM as a troubleshooting step and retry the install.
[02:11:38]
<Granite T. Rock> > The system still has 759 MiB (40%) RAM available out of 1.9 GiB.
> The system has no swap at all. You should consider adding at least 512 MiB of swap to avoid situations where the system runs out of memory.
[02:12:09]
<Granite T. Rock> Thanks for your help! Looks like your thoughts about running out of RAM are right.
[06:31:55]
<lapineige> Some swap should be enough for the install of netdata :)
[06:32:08]
<lapineige> You may have a look at zram too :)
[06:56:53]
<Michele Agostinelli> Hello, I installed YunoHost on a VPS with ipv6 only, i receive the following errors:
yunohost diagnosis run
Info: (Cache still valid for Base system diagnosis. Won't re-diagnose it yet!)
Info: (Cache still valid for Internet connectivity diagnosis. Won't re-diagnose it yet!)
Error: Can't run diagnosis for DNS records while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Ports exposure while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Web while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Email while there are important issues related to Internet connectivity.
Info: (Cache still valid for Services status check diagnosis. Won't re-diagnose it yet!)
Info: (Cache still valid for System resources diagnosis. Won't re-diagnose it yet!)
Info: (Cache still valid for System configurations diagnosis. Won't re-diagnose it yet!)
Info: (Cache still valid for Applications diagnosis. Won't re-diagnose it yet!)
Any ideas?
[06:59:35]
<tituspijean> Ciao Michele Agostinelli, I see
> Can't run diagnosis ... while there are important issues related to Internet connectivity.
What does it say about Internet connectivity?
[07:02:59]
<Michele Agostinelli> yunohost diagnosis run --force
Success! Everything looks OK for Base system!
Error: Found 1 significant issue(s) related to Internet connectivity!
Error: Can't run diagnosis for DNS records while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Ports exposure while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Web while there are important issues related to Internet connectivity.
Error: Can't run diagnosis for Email while there are important issues related to Internet connectivity.
Success! Everything looks OK for Services status check!
Success! Everything looks OK for System resources!
Error: Found 1 significant issue(s) (and 1 warning(s)) related to 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.
[07:42:42]
<pti-jean> J'ai le port 587 d'ouvert ??
À quoi ça correspond le port:
587/tcp open submission
à quel service ?
[07:48:54]
<Jim> > <pti-jean> J'ai le port 587 d'ouvert ??
> À quoi ça correspond le port:
> 587/tcp open submission
> à quel service ?
C'est le mail (SMTP).
[07:51:20]
<tituspijean> Michele Agostinelli I am not sure you are reading the output, did you follow the suggestion of looking into the webadmin or running `yunohost diagnosis show --issues --human-readable` ? The webadmin is way more convenient for the Diagnosis.
[07:54:44]
<Michele Agostinelli> # I think that ipv4 is mandatory:
# Internet connectivity (ip)
\[ERROR\] The server does not have working IPv4.
I found this command:
yunohost diagnosis unignore --filter ip test=ipv4
But it doesn't work the next step (DNS records)
[08:13:22]
<tituspijean> Michele Agostinelli I need more context on your server now. Does it actually have an IPv4?
[08:25:29]
<pti-jean> Jim, 👍️
[08:37:39]
<craigvb[m]> any easy fix for owncloud coming up with a 403 forbidden nginx message? happened since trying to update the other day
[08:43:48]
<craigvb[m]> I seem to recall there was some way to rebuild all the config files...but blowed if I can remember it just atm
[09:05:14]
<tituspijean> https://aria.im/_matrix/media/v1/download/pijean.ovh/c8b2ca774ec39165d47bc7e936d9ca404d993d336c1bce985f2cc7f232c287c2
[09:11:12]
<Michele Agostinelli> > <@titus:pijean.ovh> Michele Agostinelli I need more context on your server now. Does it actually have an IPv4?
no, only ipv6 address.
[09:20:42]
<tituspijean> Michele Agostinelli Then you can safely ignore anything related to IPv4. You actually have a global setting for that:
[09:20:42]
<tituspijean> https://aria.im/_matrix/media/v1/download/pijean.ovh/90abfe20ae75a55fe4cf4d70c355f1a7e1f7b3c7efcef00edcecebf03139fd28
[09:33:23]
<craigvb[m]> NVM...will uninstall and reinstall, should be as good as rebooting windows 🤣
[09:34:15]
<craigvb[m]> sigh.... *nextcloud I need sleep
[09:41:18]
<craigvb[m]> well.... darn it, that didn't work apparently uninstalling doesn't remove everything? https://paste.yunohost.org/raw/ihovifutak
[09:42:36]
<craigvb[m]> username is invalid because files already exists for this user
[09:49:19]
<craigvb[m]> is there anyway to actually completely uninstall the app from yunohost?
[09:49:19]
<tituspijean> and btw, having the log of NGINX for the 403 error would be nice
[09:49:19]
<tituspijean> try restoring a backup instead of reinstalling
[09:49:19]
<Daniel Rodríguez Rivero> Hello. I started to get some errors in logrotate. Not sure if those can be related to me moving the home directory to a new disk
[09:49:20]
<Daniel Rodríguez Rivero> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
Jul 25 09:44:22 yuno.danielo.es systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
[09:49:23]
<craigvb[m]> restore worked..will leave it alone until after some sleep to try and get the upgrade working <3
[09:49:23]
<Daniel Rodríguez Rivero> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
Jul 25 09:44:22 yuno.danielo.es systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURElogrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
Jul 25 09:44:22 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
[09:49:23]
<Daniel Rodríguez Rivero> ```
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
Jul 25 09:44:22 yuno.danielo.es systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURElogrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
Jul 25 09:44:22 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
```
[11:37:35]
<orhtej2> > <@danielo515:matrix.org> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
> Jul 25 09:44:22 logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
> Jul 25 09:44:22 Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb/calibreweb.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in conf>
> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/calibreweb//var/log/calibreweb/calibreweb-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root")>
> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/freshrss/freshrss.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/miniflux/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to >
> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/api-access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config f>
> Jul 25 09:44:22 yuno.danielo.es logrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
> Jul 25 09:44:22 yuno.danielo.es systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURElogrotate[398718]: error: skipping "/var/log/rportd/rportd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file >
> Jul 25 09:44:22 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
>
curious, what's the output of `ls -la /var/log` ?
[11:41:03]
<Aleks (he/him/il/lui)> or even `ls -ld /var/log`
[11:42:20]
<orhtej2> > <@danielo515:matrix.org> Hello. I started to get some errors in logrotate. Not sure if those can be related to me moving the home directory to a new disk
I mean the borked permissions seem on `/var` rather than `/home` but IDK about the exact steps you took so who knows
[11:43:11]
<Daniel Rodríguez Rivero> > curious, what's the output of `ls -la /var/log` ?
```
total 107648
drwxr-xr-x 23 root root 4096 Jul 23 00:00 .
drwxr-xr-x 14 root root 4096 Jul 22 15:30 ..
-rw-r--r-- 1 root root 1646 Jul 21 20:22 alternatives.log
-rw-r--r-- 1 root root 15555 Jul 12 12:00 alternatives.log.1
-rw-r--r-- 1 root root 2569 Jan 16 2023 alternatives.log.2.gz
drwxr-xr-x 2 root root 4096 Jul 24 09:44 apt
-rw-r----- 1 root adm 3059694 Jul 25 11:42 auth.log
-rw-r----- 1 root adm 8259963 Jul 23 00:00 auth.log.1
-rw-r----- 1 root adm 791902 Jul 16 00:00 auth.log.2.gz
-rw-r----- 1 root adm 951046 Jul 9 00:00 auth.log.3.gz
-rw-r----- 1 root adm 941733 Jul 2 00:00 auth.log.4.gz
-rw-rw---- 1 root utmp 15665664 Jul 25 11:41 btmp
-rw-rw---- 1 root utmp 16465920 Jun 30 23:59 btmp.1
drwxrwxrwx 3 calibreweb calibreweb 4096 Jul 19 04:10 calibreweb
-rw-r--r-- 1 root adm 457811 Jul 21 20:22 cloud-init.log
-rw-r----- 1 root adm 19673 Jul 21 20:22 cloud-init-output.log
drwxr-x--- 2 couchdb couchdb 4096 Jul 23 00:00 couchdb
-rw-r----- 1 root adm 4710965 Jul 25 11:41 daemon.log
-rw-r----- 1 root adm 13608218 Jul 23 00:00 daemon.log.1
-rw-r----- 1 root adm 584846 Jul 16 00:00 daemon.log.2.gz
-rw-r----- 1 root adm 53759 Jul 9 00:00 daemon.log.3.gz
-rw-r----- 1 root adm 58677 Jul 2 00:00 daemon.log.4.gz
-rw-r----- 1 root adm 143913 Jul 25 11:40 debug
-rw-r----- 1 root adm 249103 Jul 22 23:00 debug.1
-rw-r----- 1 root adm 8688 Jul 15 23:52 debug.2.gz
-rw-r----- 1 root adm 5817 Jul 8 23:40 debug.3.gz
-rw-r----- 1 root adm 5977 Jul 2 00:00 debug.4.gz
-rw-r--r-- 1 root root 30706 Jul 24 09:44 dpkg.log
-rw-r--r-- 1 root root 190664 Jul 12 12:00 dpkg.log.1
-rw-r--r-- 1 root root 30012 Jan 16 2023 dpkg.log.2.gz
-rw-r----- 1 root adm 415923 Jul 25 11:41 fail2ban.log
-rw-r----- 1 root adm 1339952 Jul 23 00:00 fail2ban.log.1
-rw-r----- 1 root adm 137239 Jul 15 23:59 fail2ban.log.2.gz
-rw-r----- 1 root adm 153930 Jul 8 23:51 fail2ban.log.3.gz
-rw-r----- 1 root adm 146790 Jul 1 23:59 fail2ban.log.4.gz
-rw-r--r-- 1 root root 31968 Jul 21 16:48 faillog
-rw-r--r-- 1 root root 2382 Jan 13 2023 fontconfig.log
drwxrwxrwx 2 freshrss www-data 4096 Jan 13 2023 freshrss
drwxr-sr-x+ 4 root systemd-journal 4096 Jan 13 2023 journal
-rw-r----- 1 root adm 0 Jul 23 00:00 kern.log
-rw-r----- 1 root adm 79168 Jul 22 15:33 kern.log.1
-rw-r----- 1 root adm 4725 Jul 13 12:25 kern.log.2.gz
-rw-r----- 1 root adm 159 Jul 12 07:49 kern.log.3.gz
-rw-r----- 1 root adm 144 Jun 20 14:07 kern.log.4.gz
-rw-rw-r-- 1 root utmp 6104552 Jul 25 08:48 lastlog
-rw-r----- 1 root adm 0 Jan 15 2023 mail.err
-rw-r----- 1 root adm 408 Jan 13 2023 mail.err.1
-rw-r----- 1 root adm 1643891 Jul 25 11:39 mail.info
-rw-r----- 1 root adm 3242027 Jul 22 23:59 mail.info.1
-rw-r----- 1 root adm 141923 Jul 15 23:58 mail.info.2.gz
-rw-r----- 1 root adm 151835 Jul 8 23:59 mail.info.3.gz
-rw-r----- 1 root adm 102884 Jul 1 23:59 mail.info.4.gz
-rw-r----- 1 root adm 1643891 Jul 25 11:39 mail.log
-rw-r----- 1 root adm 3242027 Jul 22 23:59 mail.log.1
-rw-r----- 1 root adm 141923 Jul 15 23:58 mail.log.2.gz
-rw-r----- 1 root adm 151835 Jul 8 23:59 mail.log.3.gz
-rw-r----- 1 root adm 102884 Jul 1 23:59 mail.log.4.gz
-rw-r----- 1 root adm 26845 Jul 25 11:11 mail.warn
-rw-r----- 1 root adm 14015 Jul 22 23:59 mail.warn.1
-rw-r----- 1 root adm 2181 Jul 15 23:45 mail.warn.2.gz
-rw-r----- 1 root adm 7746 Jul 8 22:32 mail.warn.3.gz
-rw-r----- 1 root adm 2883 Jul 1 23:35 mail.warn.4.gz
-rw-r----- 1 root adm 146107 Jul 25 11:40 messages
-rw-r----- 1 root adm 576441 Jul 23 00:00 messages.1
-rw-r----- 1 root adm 733393 Jul 16 00:00 messages.2.gz
-rw-r----- 1 root adm 26368 Jul 9 00:00 messages.3.gz
-rw-r----- 1 root adm 26402 Jul 2 00:00 messages.4.gz
drwxr-x--- 2 metronome adm 4096 Jul 25 00:00 metronome
drwxrw-r-- 2 root root 4096 Jan 13 2023 miniflux
drwxr-s--- 2 mysql adm 4096 Jan 13 2023 mysql
drwxr-xr-x+ 2 root adm 12288 Jul 25 00:00 nginx
drwxr-xr-x 2 ntp ntp 4096 Sep 23 2020 ntpstats
drwxrwxr-x 8 pcp pcp 4096 Jan 15 2023 pcp
-rw------- 1 root root 856 Jul 25 09:29 php7.4-fpm.log
-rw------- 1 root root 2537 Jul 22 19:16 php7.4-fpm.log.1
-rw------- 1 root root 241 May 20 19:12 php7.4-fpm.log.10.gz
-rw------- 1 root root 249 May 13 19:11 php7.4-fpm.log.11.gz
-rw------- 1 root root 245 May 6 19:11 php7.4-fpm.log.12.gz
-rw------- 1 root root 596 Jul 15 19:02 php7.4-fpm.log.2.gz
-rw------- 1 root root 243 Jul 8 19:08 php7.4-fpm.log.3.gz
-rw------- 1 root root 246 Jul 1 19:06 php7.4-fpm.log.4.gz
-rw------- 1 root root 243 Jun 24 19:19 php7.4-fpm.log.5.gz
-rw------- 1 root root 243 Jun 17 19:19 php7.4-fpm.log.6.gz
-rw------- 1 root root 239 Jun 10 19:03 php7.4-fpm.log.7.gz
-rw------- 1 root root 250 Jun 3 19:04 php7.4-fpm.log.8.gz
-rw------- 1 root root 239 May 27 19:14 php7.4-fpm.log.9.gz
-rw------- 1 root root 856 Jul 25 09:29 php8.0-fpm.log
-rw------- 1 root root 2537 Jul 22 19:16 php8.0-fpm.log.1
-rw------- 1 root root 447 Jul 15 19:02 php8.0-fpm.log.2.gz
-rw------- 1 root root 856 Jul 25 09:29 php8.1-fpm.log
-rw------- 1 root root 4306 Jul 22 19:16 php8.1-fpm.log.1
-rw------- 1 root root 856 Jul 25 09:29 php8.2-fpm.log
-rw------- 1 root root 2537 Jul 22 19:16 php8.2-fpm.log.1
-rw------- 1 root root 585 Jul 15 19:02 php8.2-fpm.log.2.gz
drwxrwxr-t 2 root postgres 4096 Jul 22 00:00 postgresql
drwx------ 2 root root 4096 Jan 13 2023 private
drwxr-s--- 2 redis adm 4096 Jul 23 00:00 redis
drwxrwxrwx 2 rportd rportd 4096 Jan 14 2023 rportd
drwxr-x--- 2 _rspamd _rspamd 4096 Jul 25 00:00 rspamd
drwxr-xr-x 3 root root 4096 Jan 13 2023 runit
drwxr-x--- 2 root adm 4096 Aug 9 2022 samba
drwxr-xr-x 2 root root 4096 Jan 13 2023 supervisor
-rw-r----- 1 root adm 6897212 Jul 25 11:41 syslog
-rw-r----- 1 root adm 18165113 Jul 23 00:00 syslog.1
-rw-r----- 1 root adm 1580618 Jul 16 00:00 syslog.2.gz
-rw-r----- 1 root adm 295621 Jul 9 00:00 syslog.3.gz
-rw-r----- 1 root adm 250216 Jul 2 00:00 syslog.4.gz
drwxr-x--- 2 root adm 4096 Jul 22 00:00 unattended-upgrades
-rw-r----- 1 root adm 159364 Jul 25 11:40 user.log
-rw-r----- 1 root adm 532004 Jul 23 00:00 user.log.1
-rw-r----- 1 root adm 729937 Jul 16 00:00 user.log.2.gz
-rw-r----- 1 root adm 27837 Jul 9 00:00 user.log.3.gz
-rw-r----- 1 root adm 28007 Jul 2 00:00 user.log.4.gz
-rw-rw-r-- 1 root utmp 71808 Jul 25 08:48 wtmp
drwxr-x--- 3 root root 4096 Jul 23 00:00 yunohost
-rw-r--r-- 1 root root 272890 Jan 13 2023 yunohost-installation_20230113_123419.log
[11:43:39]
<Daniel Rodríguez Rivero> ```
drwxr-xr-x 23 root root 4096 Jul 23 00:00 /var/log
```
[11:44:16]
<Daniel Rodríguez Rivero> > I mean the borked permissions seem on `/var` rather than `/home` but IDK about the exact steps you took so who knows
The only steps I followed where the ones in the yunohost tutorial
[11:44:37]
<Daniel Rodríguez Rivero> Didn't modified anything in the /var/log or /etc/logrotate
[11:45:17]
<orhtej2> > <@danielo515:matrix.org> ```
> total 107648
> drwxr-xr-x 23 root root 4096 Jul 23 00:00 .
> drwxr-xr-x 14 root root 4096 Jul 22 15:30 ..
> -rw-r--r-- 1 root root 1646 Jul 21 20:22 alternatives.log
> -rw-r--r-- 1 root root 15555 Jul 12 12:00 alternatives.log.1
> -rw-r--r-- 1 root root 2569 Jan 16 2023 alternatives.log.2.gz
> drwxr-xr-x 2 root root 4096 Jul 24 09:44 apt
> -rw-r----- 1 root adm 3059694 Jul 25 11:42 auth.log
> -rw-r----- 1 root adm 8259963 Jul 23 00:00 auth.log.1
> -rw-r----- 1 root adm 791902 Jul 16 00:00 auth.log.2.gz
> -rw-r----- 1 root adm 951046 Jul 9 00:00 auth.log.3.gz
> -rw-r----- 1 root adm 941733 Jul 2 00:00 auth.log.4.gz
> -rw-rw---- 1 root utmp 15665664 Jul 25 11:41 btmp
> -rw-rw---- 1 root utmp 16465920 Jun 30 23:59 btmp.1
> drwxrwxrwx 3 calibreweb calibreweb 4096 Jul 19 04:10 calibreweb
> -rw-r--r-- 1 root adm 457811 Jul 21 20:22 cloud-init.log
> -rw-r----- 1 root adm 19673 Jul 21 20:22 cloud-init-output.log
> drwxr-x--- 2 couchdb couchdb 4096 Jul 23 00:00 couchdb
> -rw-r----- 1 root adm 4710965 Jul 25 11:41 daemon.log
> -rw-r----- 1 root adm 13608218 Jul 23 00:00 daemon.log.1
> -rw-r----- 1 root adm 584846 Jul 16 00:00 daemon.log.2.gz
> -rw-r----- 1 root adm 53759 Jul 9 00:00 daemon.log.3.gz
> -rw-r----- 1 root adm 58677 Jul 2 00:00 daemon.log.4.gz
> -rw-r----- 1 root adm 143913 Jul 25 11:40 debug
> -rw-r----- 1 root adm 249103 Jul 22 23:00 debug.1
> -rw-r----- 1 root adm 8688 Jul 15 23:52 debug.2.gz
> -rw-r----- 1 root adm 5817 Jul 8 23:40 debug.3.gz
> -rw-r----- 1 root adm 5977 Jul 2 00:00 debug.4.gz
> -rw-r--r-- 1 root root 30706 Jul 24 09:44 dpkg.log
> -rw-r--r-- 1 root root 190664 Jul 12 12:00 dpkg.log.1
> -rw-r--r-- 1 root root 30012 Jan 16 2023 dpkg.log.2.gz
> -rw-r----- 1 root adm 415923 Jul 25 11:41 fail2ban.log
> -rw-r----- 1 root adm 1339952 Jul 23 00:00 fail2ban.log.1
> -rw-r----- 1 root adm 137239 Jul 15 23:59 fail2ban.log.2.gz
> -rw-r----- 1 root adm 153930 Jul 8 23:51 fail2ban.log.3.gz
> -rw-r----- 1 root adm 146790 Jul 1 23:59 fail2ban.log.4.gz
> -rw-r--r-- 1 root root 31968 Jul 21 16:48 faillog
> -rw-r--r-- 1 root root 2382 Jan 13 2023 fontconfig.log
> drwxrwxrwx 2 freshrss www-data 4096 Jan 13 2023 freshrss
> drwxr-sr-x+ 4 root systemd-journal 4096 Jan 13 2023 journal
> -rw-r----- 1 root adm 0 Jul 23 00:00 kern.log
> -rw-r----- 1 root adm 79168 Jul 22 15:33 kern.log.1
> -rw-r----- 1 root adm 4725 Jul 13 12:25 kern.log.2.gz
> -rw-r----- 1 root adm 159 Jul 12 07:49 kern.log.3.gz
> -rw-r----- 1 root adm 144 Jun 20 14:07 kern.log.4.gz
> -rw-rw-r-- 1 root utmp 6104552 Jul 25 08:48 lastlog
> -rw-r----- 1 root adm 0 Jan 15 2023 mail.err
> -rw-r----- 1 root adm 408 Jan 13 2023 mail.err.1
> -rw-r----- 1 root adm 1643891 Jul 25 11:39 mail.info
> -rw-r----- 1 root adm 3242027 Jul 22 23:59 mail.info.1
> -rw-r----- 1 root adm 141923 Jul 15 23:58 mail.info.2.gz
> -rw-r----- 1 root adm 151835 Jul 8 23:59 mail.info.3.gz
> -rw-r----- 1 root adm 102884 Jul 1 23:59 mail.info.4.gz
> -rw-r----- 1 root adm 1643891 Jul 25 11:39 mail.log
> -rw-r----- 1 root adm 3242027 Jul 22 23:59 mail.log.1
> -rw-r----- 1 root adm 141923 Jul 15 23:58 mail.log.2.gz
> -rw-r----- 1 root adm 151835 Jul 8 23:59 mail.log.3.gz
> -rw-r----- 1 root adm 102884 Jul 1 23:59 mail.log.4.gz
> -rw-r----- 1 root adm 26845 Jul 25 11:11 mail.warn
> -rw-r----- 1 root adm 14015 Jul 22 23:59 mail.warn.1
> -rw-r----- 1 root adm 2181 Jul 15 23:45 mail.warn.2.gz
> -rw-r----- 1 root adm 7746 Jul 8 22:32 mail.warn.3.gz
> -rw-r----- 1 root adm 2883 Jul 1 23:35 mail.warn.4.gz
> -rw-r----- 1 root adm 146107 Jul 25 11:40 messages
> -rw-r----- 1 root adm 576441 Jul 23 00:00 messages.1
> -rw-r----- 1 root adm 733393 Jul 16 00:00 messages.2.gz
> -rw-r----- 1 root adm 26368 Jul 9 00:00 messages.3.gz
> -rw-r----- 1 root adm 26402 Jul 2 00:00 messages.4.gz
> drwxr-x--- 2 metronome adm 4096 Jul 25 00:00 metronome
> drwxrw-r-- 2 root root 4096 Jan 13 2023 miniflux
> drwxr-s--- 2 mysql adm 4096 Jan 13 2023 mysql
> drwxr-xr-x+ 2 root adm 12288 Jul 25 00:00 nginx
> drwxr-xr-x 2 ntp ntp 4096 Sep 23 2020 ntpstats
> drwxrwxr-x 8 pcp pcp 4096 Jan 15 2023 pcp
> -rw------- 1 root root 856 Jul 25 09:29 php7.4-fpm.log
> -rw------- 1 root root 2537 Jul 22 19:16 php7.4-fpm.log.1
> -rw------- 1 root root 241 May 20 19:12 php7.4-fpm.log.10.gz
> -rw------- 1 root root 249 May 13 19:11 php7.4-fpm.log.11.gz
> -rw------- 1 root root 245 May 6 19:11 php7.4-fpm.log.12.gz
> -rw------- 1 root root 596 Jul 15 19:02 php7.4-fpm.log.2.gz
> -rw------- 1 root root 243 Jul 8 19:08 php7.4-fpm.log.3.gz
> -rw------- 1 root root 246 Jul 1 19:06 php7.4-fpm.log.4.gz
> -rw------- 1 root root 243 Jun 24 19:19 php7.4-fpm.log.5.gz
> -rw------- 1 root root 243 Jun 17 19:19 php7.4-fpm.log.6.gz
> -rw------- 1 root root 239 Jun 10 19:03 php7.4-fpm.log.7.gz
> -rw------- 1 root root 250 Jun 3 19:04 php7.4-fpm.log.8.gz
> -rw------- 1 root root 239 May 27 19:14 php7.4-fpm.log.9.gz
> -rw------- 1 root root 856 Jul 25 09:29 php8.0-fpm.log
> -rw------- 1 root root 2537 Jul 22 19:16 php8.0-fpm.log.1
> -rw------- 1 root root 447 Jul 15 19:02 php8.0-fpm.log.2.gz
> -rw------- 1 root root 856 Jul 25 09:29 php8.1-fpm.log
> -rw------- 1 root root 4306 Jul 22 19:16 php8.1-fpm.log.1
> -rw------- 1 root root 856 Jul 25 09:29 php8.2-fpm.log
> -rw------- 1 root root 2537 Jul 22 19:16 php8.2-fpm.log.1
> -rw------- 1 root root 585 Jul 15 19:02 php8.2-fpm.log.2.gz
> drwxrwxr-t 2 root postgres 4096 Jul 22 00:00 postgresql
> drwx------ 2 root root 4096 Jan 13 2023 private
> drwxr-s--- 2 redis adm 4096 Jul 23 00:00 redis
> drwxrwxrwx 2 rportd rportd 4096 Jan 14 2023 rportd
> drwxr-x--- 2 _rspamd _rspamd 4096 Jul 25 00:00 rspamd
> drwxr-xr-x 3 root root 4096 Jan 13 2023 runit
> drwxr-x--- 2 root adm 4096 Aug 9 2022 samba
> drwxr-xr-x 2 root root 4096 Jan 13 2023 supervisor
> -rw-r----- 1 root adm 6897212 Jul 25 11:41 syslog
> -rw-r----- 1 root adm 18165113 Jul 23 00:00 syslog.1
> -rw-r----- 1 root adm 1580618 Jul 16 00:00 syslog.2.gz
> -rw-r----- 1 root adm 295621 Jul 9 00:00 syslog.3.gz
> -rw-r----- 1 root adm 250216 Jul 2 00:00 syslog.4.gz
> drwxr-x--- 2 root adm 4096 Jul 22 00:00 unattended-upgrades
> -rw-r----- 1 root adm 159364 Jul 25 11:40 user.log
> -rw-r----- 1 root adm 532004 Jul 23 00:00 user.log.1
> -rw-r----- 1 root adm 729937 Jul 16 00:00 user.log.2.gz
> -rw-r----- 1 root adm 27837 Jul 9 00:00 user.log.3.gz
> -rw-r----- 1 root adm 28007 Jul 2 00:00 user.log.4.gz
> -rw-rw-r-- 1 root utmp 71808 Jul 25 08:48 wtmp
> drwxr-x--- 3 root root 4096 Jul 23 00:00 yunohost
> -rw-r--r-- 1 root root 272890 Jan 13 2023 yunohost-installation_20230113_123419.log
welp as indicated by the log these ale all over the place, perhaps someone with more experience knows if it's just a matter of a couple of `chown`/`chgrp`/`chmod` ?
[11:47:11]
<Aleks (he/him/il/lui)> > <@danielo515:matrix.org> The only steps I followed where the ones in the yunohost tutorial
there are many instructions in yunohost tutorial, could you be more specific x_x
[11:47:19]
<orhtej2> although I find `miniflux` entry especially puzzling as `./.log` does not seem like a proper log name :/
[11:51:37]
<orhtej2> > <@danielo515:matrix.org> The only steps I followed where the ones in the yunohost tutorial
this one? https://yunohost.org/it/external_storage
[11:52:24]
<Daniel Rodríguez Rivero> Talking about this one https://yunohost.org/it/external_storage
[11:52:29]
<Daniel Rodríguez Rivero> > this one? https://yunohost.org/it/external_storage
Yes, that one
[11:54:20]
<Daniel Rodríguez Rivero> The thing is that, I don't know if this is a bug in yunohost or if there is something else going on
[11:54:57]
<Aleks (he/him/il/lui)> i'm not seeing anything related to tweaking /var/log ...
[12:07:01]
<Daniel Rodríguez Rivero> > <@Alekswag:matrix.org> i'm not seeing anything related to tweaking /var/log ...
I know, that's why I think it's unrelated, and I just found this problem while checking my server
[12:18:08]
<Lars> Hello, i would upgrade today the Whatsapp Bridge. Das Failed. Now i cant get the Bridge working after restoring the Update.
[12:18:10]
<Lars> https://paste.yunohost.org/voyikigime
[12:19:00]
<Lars> that was the Error at the Upgrade 2023-07-25 13:09:57,877: DEBUG - + /opt/yunohost/mautrix_whatsapp/mautrix-whatsapp -g -c /opt/yunohost/mautrix_whatsapp/config.yaml -r /etc/matrix-synapse/app-service/mautrix_whatsapp.yaml
2023-07-25 13:09:57,885: WARNING - Error updating config: failed to unmarshal config: yaml: line 91: did not find expected key
2023-07-25 13:09:57,887: WARNING - Failed to parse config: yaml: line 91: did not find expected key
[12:27:24]
<tituspijean> Lars hallo. Can you share the full upgrade log?
[12:27:59]
<tituspijean> I am no expert on mautrix bridges, but the error from the service looks from a different issue
[12:28:01]
<Lars> yes here: tituspijean https://paste.yunohost.org/raw/qarofenivu
[12:28:36]
<Lars> and the log for failing to start after restore the Backup https://paste.yunohost.org/voyikigime
[12:48:32]
<Lars> issue found. At restore the permission is set to root and not mautrix_whatsapp
[14:58:26]
<tituspijean> Lars thanks for the debugging! If you have a github account, feel free to open an issue in its repository 😉
[14:59:58]
<muma> It's asking me to enter the username and password right after the installation. May you please help me an tell me the default login credentials to the desktop.
[15:02:10]
<tituspijean> > <@titus:pijean.ovh> Lars thanks for the debugging! If you have a github account, feel free to open an issue in its repository 😉
ah I didn't see you already reported that elsewhere.
[15:02:44]
<tituspijean> muma `root` and `yunohost` as password
[15:03:16]
<muma> didn't work for me
[15:04:01]
<muma> I already tried those credentials..
[15:04:21]
<tituspijean> then, can you describe better what's on screen?
[15:04:42]
<tituspijean> hum wait, "credentials to the desktop"? what do you mean?
[15:05:04]
<muma> username I give the root in
[15:06:38]
<muma> I also tried typing z instead of y, still getting the error code
[15:08:07]
<tituspijean> how have you installed YunoHost? on which hardware?
whz would zou tzpe z instead of z? 🤔
have you performed the post-installation?
[15:09:31]
<muma> I can't go passt the login screen
[15:09:55]
<muma> I meant y with z because it midght have been the German layout for the keyboard
[15:13:12]
<tituspijean> Try "from the web interface" method: https://yunohost.org/de/install/hardware:regular#proceed-with-the-initial-
[15:13:58]
<tituspijean> (I still need to now your hardware and how you installed YunoHost: from ISO, or with the `curl | bash` command?)
[15:14:33]
<muma> core i5 series 9
[15:15:54]
<muma> gtx1660ti
[15:16:15]
<tituspijean> "regular computer" it is, then 🙂
[15:16:31]
<muma> Yeah
[15:18:39]
<muma> Strange.. I haven't found any cases like mine on the internet 🤔
[15:23:18]
<tituspijean> > <@titus:pijean.ovh> Try "from the web interface" method: https://yunohost.org/de/install/hardware:regular#proceed-with-the-initial-
...
[16:51:08]
<Daniel Rodríguez Rivero> can't find this feature in my installed tynytynyrss https://tt-rss.org/wiki/ShareAnything
[18:34:24]
<ynhuser> Hi?
[18:37:56]
<nalla22> Bonjour, j'ai créé un dossier à la racine du système de fichier avec l'utilisateur root, et je voudrais donner les droits nécéssaires à l'utilisateur admin de yunohost pour que les applications comme Jellyfin et autre puissent avoir les droits d'écriture sur ce fameux dossier...
Mais l'utilisateur admin yunohost est introuvable dans la liste `/cat/group`, comment donner les droits à cet utilisateur invisible sur ce dossier ?
[18:40:14]
<Chatpitaine Caverne> nalla22: il n'y a plus d'utilisateur admin. Par contre, il existe un groupe admins.
[18:41:12]
<nalla22> Je faisais référence au status admin de l'utilisateur suprême de yunohost !
[18:44:49]
<ynhuser> What?
[18:48:24]
<nalla22> En faite je sais très bien que l'utilisateur admin n'est plus présent par defaut sur yunohost, mais à defaut de me répéter, je faisais référence à un utilisateur quelconque enregistré sur la panel yunohost avec les droits "admin".
Ceci n'a rien avoir avec ma question, et ne résout pas mon problème de base !
[18:49:47]
<Tag> Tu peux utiliser la commande `chown` pour modifier l'utilisateur et le groupe lié à ton dossier.
[18:54:46]
<Tag> nalla22: Je ne comprends pas pourquoi tu as besoin d'aller chercher ton utilisateur admin dans `/etc/group`. Tu peux simplement l'appeler par son nom.
Pour info, il n'est pas visible dans ce fichier car il est géré par LDAP
[18:56:12]
<nalla22> D'accord,est-ce que je peux mettre ce dossier dans le groupe yunohost, pour que tous les utilisateurs yunohost puissent y accéder en lecture et écriture ?
[18:57:43]
<nalla22> (je ne sais pas comment se nomme le groupe yunohost s'il y'en a un!)
[18:58:21]
<Tag> Je n'ai pas testé, mais ça fonctionne peut être ? Le groupe en question s'appelle `all_users`
[18:59:33]
<nalla22> Et le groupe qui concerne seulement les admins yunohost s'appelle comment ?
[19:00:09]
<Tag> Tu peux voir la liste des groupes gérés par yunohost avec `sudo yunohost user group list`
[19:00:53]
<Tag> Et un peu de lecture https://yunohost.org/fr/groups_and_permissions#groupes-par-defaut
[19:01:55]
<nalla22> Merci pour les informations, je ferais des tests dès que mon serveur sera en route :)
[19:15:48]
<YunoHostGuest> Bonjour, je rencontre un problème sur votre repo matomo : https://forum.yunohost.org/t/maj-matomo-networkerror-when-attempting-to-fetch-resource/25585/2
[21:08:47]
<nalla22> > <@tag:lostpod.me> Et un peu de lecture https://yunohost.org/fr/groups_and_permissions#groupes-par-defaut
J'ai lu le didacticiel jusqu'au bout, mais il n'explique pas comment donner à un dossier les permissions d'un groupe Yunohost, car bien évidemment les groupes spéciaux visitors, all_users et admins ne sont pas présents dans /etc/group !
[21:14:20]
<Tag> Oui, pareil que tout à l'heure : ces groupes sont gérés par LDAP, pas besoin de les avoir dans /etc/group
[21:16:36]
<Tag> nalla22: je ne comprends toujours pas pourquoi tu les cherches dans /etc/group :(
Avec `chown user:group /dossier` ça fonctionne
[21:17:09]
<nalla22> > <@tag:lostpod.me> nalla22: je ne comprends toujours pas pourquoi tu les cherches dans /etc/group :(
> Avec `chown user:group /dossier` ça fonctionne
Peut être parce que /etc/group est censé répértorier tous les groupes Linux comme son nom l'indique !
[21:17:53]
<Tag> Et pourtant tu arrives à te connecter en SSH avec ton utilisateur admin
[21:18:32]
<nalla22> Et si j'essayais de créer un deuxième groupe nommé "visitors" est ce que j'aurai l'autorisation du système pour le faire vu qu'il n'est pas présent dans /etc/groups ?
[21:19:04]
<Tag> ?
[21:19:28]
<Tag> Tu rencontres un message d'erreur quelque part ?
[21:20:14]
<nalla22> Quels sont les fichiers équivalents à /etc/groups et /etc/passwd côté LDAP ?
[21:20:32]
<nalla22> > <@tag:lostpod.me> Tu rencontres un message d'erreur quelque part ?
J'essaye juste de comprendre !
[21:21:15]
<Tag> > <@nalla22:matrix.org> Quels sont les fichiers équivalents à /etc/groups et /etc/passwd côté LDAP ?
Tu peux t'amuser avec l'app phpLDAPadmin, mais sinon l'interface Utilisateurs de YunoHost fonctionne bien pour ça
[21:21:28]
<Gilou> getent passwd est ton ami
[21:21:29]
<Gilou> et getent group pour l'autre ;)
[21:21:58]
<Tag> et tu as de la conf dans /etc/slapd/
[21:22:14]
<Gilou> si ton système (et notamment nsswitch) tape sur ldap, getent te les sortira
[21:22:44]
<Gilou> et c'est ce que fait yunohost ;)
[21:24:12]
<nalla22> > <@Gilou:libera.chat> getent passwd est ton ami
Je viens de tester, ces commandes affichent les utilisateurs et groupes standard ainsi que les utilisateurs et groupes yunohost, toute la famille est réunis :)
[21:24:52]
<Gilou> si tu veux aller lire dans l'annuaire, si tu veux vraiment voir ses entrailles, avec un joujou comme ldapvi… mais pas sûr que tu en aies très envie
[21:25:17]
<nalla22> > <@tag:lostpod.me> et tu as de la conf dans /etc/slapd/
Je ne possède pas ce dossier sur mon installation yunohost
[21:25:37]
<Gilou> parce qu'il est dans /etc/ldap
[21:26:03]
<Gilou> mais openldap est désormais configuré... par ldap.. donc c'est un peu ardu de se lancer dedans
[21:26:16]
<Gilou> mais tu as une représentation de la conf dans /etc/ldap/slapd.d
[21:27:02]
<Gilou> there be dragons, et notamment yunohost va pas spécialement apprécier si tu y mets les pattes ;)
[21:30:17]
<nalla22> Je vais me contenter de `getent passwd` et `getent group` pour voir l'ensemble des utilisateurs et groupes présents sans restrictions. Je suis également curieuse de savoir si il est également possible de supprimer les groupes et les utilisateurs LDAP/yunohost de la même manière que les autres? c'est à dire avec deluser et delgroup !
[21:33:34]
<nalla22> Apparement c'est avec `ldapdelete` que la suppression de ses utilisateurs spéciaux peut se faire !