[08:42:47]
<tituspijean> yvanq: what's its location?
[08:50:09]
<yvanq> On my server.
[08:50:25]
<yvanq> Hello do you know how I can "clean" hubzilla yunohost folder? When I backup my server, I see hubzilla is 155gb fat! huge!
Sincerely.
[08:54:00]
<yvanq> I have also a "challenge" with wireguard and davinci resolve, I'm ok to pay for it (spend too many hours now)...
[09:24:01]
<miro5001> Hi there
I'm looking for the best way to share videos with students with restricted access. I may use any cms but is there a dedicated app for this use case?
[13:30:06]
<Diogo> > <@miro5001:matrix.org> Hi there
> I'm looking for the best way to share videos with students with restricted access. I may use any cms but is there a dedicated app for this use case?
Not sure what you mean..when inwas reading, peer tube came to mind.
[14:08:15]
<lapineige> > <@miro5001:matrix.org> Hi there
> I'm looking for the best way to share videos with students with restricted access. I may use any cms but is there a dedicated app for this use case?
With a web player ? Or to download ?
[15:08:04]
<miro5001> > With a web player ? Or to download ?
A web player would be very appreciated.
A responsive design to ease access for the students, they will certainly be using smartphones and mobile data
[15:20:37]
<Crou2> Hello !
Yesterday I installed ddclient on my yunohost server through normal debian repository and I configured it to update IP (if change) toward my infomaniak DNS provider following https://www.infomaniak.com/fr/support/faq/40/configurer-ddclient-avec-dyndns-infomaniak
I have not made any other modification. My beloved server that was working well for years (with same application) is now out of reach because of a fantastic "500 Internal Server Error - nginx" when I try to access it through web, and no SSH connexion.
When I reboot, I can access through webUI or SSH for 1min-5min and then error again. Diognostic through webUI when connected didn't show anything.
The server is at home so I can connect directly to it, but how/where to look for the problem?
[15:54:17]
<Crou2> I removed ddclient (sudo apt-get remove ddclient) but my server still doesn't work as I face "404 Not Found - nginx"
Have I done something wrong?
[16:03:17]
<Aleks (he/him/il/lui)> 404 errors can happen for a lot of reason in various places ... what url are you trying to access exactly ...
[17:04:51]
<Crou2> I connected a screen and keyboard to my server and I see now:
systemd-journald[242] failed to rotate /var/log/journal/....
systemd-journald [242] failed to write entry (9 items, 245bytes)...
[17:27:25]
<Azu> sounds like you might be low on space to me
[17:43:22]
<Crou2> https://aria.im/_matrix/media/v1/download/matrix.org/thVoNIthwlZYxKEMXpthTbva
[17:43:27]
<Crou2> I though about that but you see the output of diagnosis...
[17:45:01]
<Crou2> I am thinking about corrupted log journal.
Running ``journalctl --verify`` I found one
So I did ``sudo systemctl restart systemd-journald``... should it be enough to get rid of these corrupted files?
[17:50:56]
<Crou2> But can this problem be linked to the fact I installed ``ddclient`` yesterday?
This looks strange to me. ddclient is a basic and well known program, no?
[17:58:38]
<Aleks (he/him/il/lui)> this may or may not be related, just because you bought a microwave yesterday has probably nothing to do with the fact that it's snowing today
[17:59:00]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯ or maybe it does
[17:59:34]
<Crou2> But I didn't bought any mycrowave
[18:00:06]
<Crou2> 😄
[18:01:04]
<Crou2> Aleks (he/him/il/lui) Do you think ``sudo systemctl restart systemd-journald``... should be enough to get rid of these corrupted files?
[18:01:50]
<Aleks (he/him/il/lui)> i don't know what corrupted files you are talking about
[18:05:21]
<Crou2> When I did ''journalctl --verify'', I found one corrupted log file...
[18:09:03]
<Aleks (he/him/il/lui)> right but without seeing the exact output this is just a really fuzzy description ... but yeah why not, or just `rm` the file idk
[18:41:24]
<yvanq> Hello, I would like to know the speed rate of my yunohost server connected to a VPN(wireguard) on my VPS provider (fast or speedtest or whatever). because I also have a WG vpn installed on my server and the rates are pretty slow. How can I do it ? Sincerely.
[18:41:40]
<yvanq> https://aria.im/_matrix/media/v1/download/matrix.org/qUxuQYMGvAOHQhnqrPaxKeUJ
[18:41:43]
<yvanq> https://aria.im/_matrix/media/v1/download/matrix.org/PoWXQJtQXtKiTniGdTxZHeMa
[18:42:01]
<yvanq> with and without vpn
[18:42:15]
<Aleks (he/him/il/lui)> you can install speedtest-cli
[18:46:42]
<yvanq> > <@Alekswag:matrix.org> you can install speedtest-cli
I see also an app librespeed, will try, thanks Aleks (he/him/il/lui)
[18:49:19]
<yvanq> https://aria.im/_matrix/media/v1/download/matrix.org/uSHKRcQFfvBiFBxnlFnBfmhS
[18:49:21]
<yvanq> so strange slowdown from the WG installed on Yunohost
[20:14:40]
<Crou2> Indeed it seem my system crash when I start to make a full backup (including files) through webUI. The backup archive is 40Gb.
The system crash with
``systemd-journald[242] failed to rotate /var/log/journal/....``
``systemd-journald [242] failed to write entry (9 items, 245bytes)..``
on the screen connected to my home server.
Then when I restart the serveur and I check for log with ``journalctl --verify`` then I find :
``8bff08: Invalid entry item (12/24 offset: 000000
8bff08: Invalid object contents: Bad message
File corruption detected at /var/log/journal/1adefe4644714958b95a2bcdfc0a6bfd/system@00060ca1ce98826f-3f42f18a37d54f8f.journal~:8bff08 (of 16777216 bytes, 54%).
FAIL: /var/log/journal/1adefe4644714958b95a2bcdfc0a6bfd/system@00060ca1ce98826f-3f42f18a37d54f8f.journal~ (Bad message)``
then I do ``sudo systemctl restart systemd-journald`` but I still have my corrupted log file but the system is working again...
Why this crash during the backup? How to do a backup then?
I still have 62Gb on / and 700Gb on /home
[20:15:29]
<Crou2> Indeed it seem my system crash when I start to make a full backup (including files) through webUI. The backup archive is 40Gb.
The system crash with
``systemd-journald[242] failed to rotate /var/log/journal/....``
``systemd-journald [242] failed to write entry (9 items, 245bytes)..``
on the screen connected to my home server.
Then when I restart the serveur and I check for log with ``journalctl --verify`` then I find :
``8bff08: Invalid entry item (12/24 offset: 000000``
``8bff08: Invalid object contents: Bad message``
``File corruption detected at /var/log/journal/1adefe4644714958b95a2bcdfc0a6bfd/system@00060ca1ce98826f-3f42f18a37d54f8f.journal~:8bff08 (of 16777216 bytes, 54%).``
``FAIL: /var/log/journal/1adefe4644714958b95a2bcdfc0a6bfd/system@00060ca1ce98826f-3f42f18a37d54f8f.journal~ (Bad message)``
then I do ``sudo systemctl restart systemd-journald`` but I still have my corrupted log file but the system is working again...
Why this crash during the backup? How to do a backup then?
I still have 62Gb on / and 700Gb on /home
[20:15:52]
<Aleks (he/him/il/lui)> i doubt that the system crash just because journalctl gets some corrupted file somehow ...
[20:17:09]
<Crou2> I had the feeling the system crash because ``systemd-journald[242] failed to rotate /var/log/journal/...``
Can it be the reason?
[20:18:35]
<Aleks (he/him/il/lui)> yes it can be the reason ... but don't you see anything else when you say that the "system crashes" ... like doesn't yunohost display a red error message with tips on how to share the logs ...
[20:21:14]
<Crou2> I only have these two long lines (fail to rotate and fail to write) repeating again and again on the screen.
SSH and webUi are inaccessible when server "crash".
Where can I get additional information?
[20:21:29]
<Crou2> And when server restart, yunohost diagnosis is all green
[20:21:49]
<Aleks (he/him/il/lui)> as far as i understand you're talking about a backup that you triggered, are you triggering it from the cli or webui ?
[20:22:01]
<Crou2> from the webui
[20:22:42]
<Crou2> should I try from the cli with --verbose ?
[20:24:06]
<Aleks (he/him/il/lui)> so you are launching from the webui ... what do you see in the webui exactly when the thing "crashes" ...
[20:25:35]
<Crou2> https://aria.im/_matrix/media/v1/download/matrix.org/mcuoDMIKLYiYOvJFhIeNCUHi
[20:26:19]
<Crou2> I don't see anything, it seems it freeze as nothing happen after a long time. And I am used to the backup process to be long...
[20:30:36]
<Aleks (he/him/il/lui)> then idk i would naively try to identify which app weights for ~35GB and try only backuping the others
[20:37:23]
<Crou2> The "fat" one is nextcloud, as I backup also files.
You feel the backup is too big to be handle through webUI?
I used to make full backu of 39-40GB without problem so far (expect the time to do it...)
I can try without nextcloud
[20:39:01]
<Aleks (he/him/il/lui)> idk this is a random guess to see if that could be related, as log corruption could be related to some partition getting full or whatever
[20:41:17]
<Crou2> Just to give another information (I gave this afternoon ealrier in the conversation), these problem happen after I installed ddclient on my yunohost server through normal debian repository and I configured it to update IP (if change) toward my infomaniak DNS provider following https://www.infomaniak.com/fr/support/faq/40/configurer-ddclient-avec-dyndns-infomaniak
I have not made any other modifications.
I have uninstalled ddclient this morning thinking this was the problem. It might not be indeed.
[20:42:00]
<Crou2> without nextcloud, the archive is 17GB... backup is going on...
[20:44:13]
<Crou2> and it crash but with issue raised :
Erreur: "500"
Action: "POST" /yunohost/api/backups
[20:44:51]
<Crou2> Retraçage
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 1968, in backup
tar.add(path["source"], arcname=path["dest"])
File "/usr/lib/python3.9/tarfile.py", line 1985, in add
File "/usr/lib/python3.9/tarfile.py", line 1985, in add
File "/usr/lib/python3.9/tarfile.py", line 1985, in add
[Previous line repeated 5 more times]
File "/usr/lib/python3.9/tarfile.py", line 1979, in add
File "/usr/lib/python3.9/tarfile.py", line 2007, in addfile
File "/usr/lib/python3.9/tarfile.py", line 247, in copyfileobj
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 410, in func_wrapper
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 2283, in backup_create
backup_manager.backup()
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 772, in backup
method.mount_and_backup()
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 1705, in mount_and_backup
self.backup()
File "/usr/lib/python3/dist-packages/yunohost/backup.py", line 1979, in backup
raise YunohostError("backup_creation_failed")
yunohost.utils.error.YunohostError: Impossible de créer l'archive de la sauvegarde
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/logging/__init__.py", line 1153, in close
File "/usr/lib/python3.9/logging/__init__.py", line 1063, in flush
OSError: [Errno 30] Read-only file system
During handling of the above exception, another exception occurred:
OSError: [Errno 30] Read-only file system
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/moulinette/interfaces/api.py", line 453, in process
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 580, in process
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 412, in func_wrapper
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 678, in error
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 707, in close
File "/usr/lib/python3.9/logging/__init__.py", line 1158, in close
OSError: [Errno 30] Read-only file system
[20:45:36]
<Aleks (he/him/il/lui)> >OSError: [Errno 30] Read-only file system
[20:46:04]
<Aleks (he/him/il/lui)> yeah so this + the other symptoms tend to point to some disk reaching end of life maybe
[20:47:11]
<Crou2> can I check if this is really a hardware issue?
[20:48:35]
<Crou2> Nooo... the disk are less than a year!
It's a new server I installed after receiveing fibre at home :-(
[20:54:38]
<Aleks (he/him/il/lui)> or could be like idk the base sd card if you are running on a SD card + another disk
[20:54:42]
<Aleks (he/him/il/lui)> i don't know your setup
[21:01:05]
<Crou2> The SSD is a cruxial BX500 1To for /home
and the / is on a 128GB M.2 SATA SSD
and it's a Mini-PC Intel N5100 with 8GB DDR4 RAM
... so no sd card :-(
[21:06:14]
<Aleks (he/him/il/lui)> ¯\_(ツ)_/¯
[21:09:21]
<Crou2> How do you advice me to check if this is really a hardware issue? Is there a test I can do?
[21:13:18]
<Aleks (he/him/il/lui)> Yeah checking with maybe "mount" if the disk is indeed readonly mode instead of RW to confirm
[21:32:31]
<Crou2> nothing with checking with smartctl
and ``cat /proc/mounts`` gives:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=invisible 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=3935792k,nr_inodes=983948,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,noexec,relatime,size=790872k,mode=755 0 0
/dev/sda2 / ext4 rw,relatime,errors=remount-ro 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
none /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=10633 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
/dev/sdb1 /home ext4 rw,relatime 0 0
/dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /run/user/73306 tmpfs rw,nosuid,nodev,relatime,size=790868k,nr_inodes=197717,mode=700,uid=73306,gid=73306 0 0
... it seems I will have to investigate more another day (to be able to do again full backup)
Thanks Aleks (he/him/il/lui) once again for your feedback and advices!
[21:35:16]
<Aleks (he/him/il/lui)> `errors=remount-ro` on /dev/sda2 seems consistent with what we've seen but it's flagged as `rw` in this output ... did you reboot the system between when the error arose and the mount command?
[21:37:28]
<Crou2> Yes I rebooted because when it crash, I can't run any command.
[21:42:43]
<Crou2> should I change to ``errors=remount-rw`` or is it normal as it is?
I installed Yunohost following strictly the procedure (minimal debain install then Yunohost script).
[21:48:29]
<Aleks (he/him/il/lui)> no the issue ain't that it's configured to `errors=remount-ro`, having `errors=remount-ro` is a classical "failsafe mechanism" when errors are triggered, the issue is understanding what error is happening exactly triggering the ro mode, though these are usually hardware issues
[21:50:30]
<Aleks (he/him/il/lui)> there might be some tips and further info in https://askubuntu.com/questions/251284/ubuntu-goes-into-read-only-mode-randomly
[21:51:04]
<Aleks (he/him/il/lui)> or https://unix.stackexchange.com/questions/79309/filesystem-suddenly-read-only
[21:54:21]
<Crou2> Great, I will read tomorrow these tips and article and continue searching. I will find the problem!
One again thanks you very much Aleks (he/him/il/lui)