Mysql and postgresql go down

you mean YH diagnosis ?

so

myisamchk -a *.MYI  | grep error 

would show me a list of tables to fix ?

I have a question, why there is a ubuntu package here ???

Sep 24 09:34:14 mariadbd[654976]: Kernel version: Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023

i have no idea


in the YH diagnosis i see also this:

Systemressourcen (systemresources)

[INFO] The system only has 100 MiB of swap. You should consider setting up at least 512 MiB of swap to prevent situations where the system runs out of RAM.

  • Please take care and attention that running the swap partition on an SD card or SSD can drastically reduce the

Hum, read the instructions here and the steps https://wiki.labriqueinter.net/doku.php%3Fid=howto:fix_self_corrupt_mysq, but is quite technicalā€¦

I am not sure is relevantā€¦ Take care, is with an Odroid, not a rRaspberry Piā€¦

If you have no swap space, the easiest is to create a swap file. You can do it like this for a swap file of half a GB:

fallocate -l 512M /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile

It will give you an idea how much RAM you would need extra to cover your needs. Keep in mind that swap on disk is much slower than RAM.

Add it to /etc/fstab to have it mounted automatically on boot.

source: Mysql service keeps stopping - #5 by wbk

Also some utils commands for raspberry !

if i do a reboot Mysql is running for few minutes and i can e.g. log in to my Hubzilla account just fineā€¦

Now i tried to posted a new itemā€¦ it seam to show up just fineā€¦ than i did a reboot again and the post was gone - first it seamed saved but after a reboot it was lostā€¦

So i guess there are conflicts while writing data to the Mysql db.

It all stared while i had to reset some keys - look at the TopLevelPost of this thread.

maybe writing access is blocked ? How could i check and fix this?

This is incredible ! you should have a kernel Linux raspberrypi ..... SMP PREEMPT Debian, how have you install a ubuntu package ?

what returns

uname -a
root@my:~# uname -a                                                                                                                     
Linux my.doman.tld 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux                                         
root@my:~#

Itā€™s okā€¦

i think i has not to do with Mysql exclusively - but with the whole system which is not updatingā€¦

I notices now that upgrades by apt upgrade are also not there after a rebootā€¦

so it first shows that all seamed to upgrade fine but after reboot all files are still not upgraded

this is the list i get over and over again:

root@my:~# apt list --upgradable                                                                                                                                             
Listing... Done                                                                                                                                                              
galera-4/oldstable-security 26.4.20-0+deb11u1 arm64 [upgradable from: 26.4.18-0+deb11u1]
libexpat1-dev/oldstable-security 2.2.10-2+deb11u6 arm64 [upgradable from: 2.2.10-2+deb11u5]
libexpat1/oldstable-security 2.2.10-2+deb11u6 arm64 [upgradable from: 2.2.10-2+deb11u5]
libmariadb3/oldstable-security 1:10.5.26-0+deb11u2 arm64 [upgradable from: 1:10.5.23-0+deb11u1]
libnode72/oldstable-security 12.22.12~dfsg-1~deb11u5 arm64 [upgradable from: 12.22.12~dfsg-1~deb11u4]
mariadb-client-10.5/oldstable-security 1:10.5.26-0+deb11u2 arm64 [upgradable from: 1:10.5.23-0+deb11u1]
mariadb-client-core-10.5/oldstable-security 1:10.5.26-0+deb11u2 arm64 [upgradable from: 1:10.5.23-0+deb11u1]
mariadb-common/oldstable-security,oldstable-security 1:10.5.26-0+deb11u2 all [upgradable from: 1:10.5.23-0+deb11u1]
mariadb-server-10.5/oldstable-security 1:10.5.26-0+deb11u2 arm64 [upgradable from: 1:10.5.23-0+deb11u1]
mariadb-server-core-10.5/oldstable-security 1:10.5.26-0+deb11u2 arm64 [upgradable from: 1:10.5.23-0+deb11u1]
mariadb-server/oldstable-security,oldstable-security 1:10.5.26-0+deb11u2 all [upgradable from: 1:10.5.23-0+deb11u1]
nodejs-doc/oldstable-security,oldstable-security 12.22.12~dfsg-1~deb11u5 all [upgradable from: 12.22.12~dfsg-1~deb11u4]
nodejs/oldstable-security 12.22.12~dfsg-1~deb11u5 arm64 [upgradable from: 12.22.12~dfsg-1~deb11u4]
root@my:~#                                                                                                                                                                   

So the system does not save any new filesā€¦ how could i change this?

do you try yunohost tools ugrade system

root@my:~# yunohost tools ugrade system                                                                           
Segmentation fault                                                                                                
root@my:~#                                                                                                        

 

what return ?

dmesg

a not ending list of entries like this:

[21482.132608] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21482.135744] systemd-journald[156]: Failed to write entry (20 items, 707 bytes) despite vacuuming, ignoring: Argument lis
t too long
[21482.140960] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21482.144127] systemd-journald[156]: Failed to write entry (20 items, 672 bytes) despite vacuuming, ignoring: Argument lis
t too long
[21483.909187] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21483.911629] systemd-journald[156]: Failed to write entry (20 items, 807 bytes) despite vacuuming, ignoring: Argument lis
t too long
[21483.916094] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21483.919205] systemd-journald[156]: Failed to write entry (20 items, 673 bytes) despite vacuuming, ignoring: Argument lis
t too long
[21483.924408] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21483.927576] systemd-journald[156]: Failed to write entry (20 items, 768 bytes) despite vacuuming, ignoring: Argument lis
t too long
[21483.932719] systemd-journald[156]: Failed to create new system journal: Device or resource busy
[21483.936049] systemd-journald[156]: Failed to write entry (20 items, 677 bytes) despite vacuuming, ignoring: Argument lis
t too long

waouwā€¦ an application is eating all memoryā€¦ Is your server installed in a SDD ? or is it on a SD card ?

SD Cartā€¦ works perfect for years now.

so why is the memory eaten - maybe because no date can be saved but will be loaded into the memory instead ?

It becomes very hard to understand whatā€™s wrong.
I tought micro SD card wears out each time its writing and uploading, the temporally writes on a SD card will stay and allow spaceā€¦

I am afraid about something corrupted on your hardware (on the SD card), but perhaps it isnā€™t trueā€¦

Have you try this command to clean space

yunohost tools basic-space-cleanup

? You can see here what commands do this code (cleaning logs, apt, journal)

You can try to see why Device or resource busy, which process ? htop or ps -aux, the memory use ? free -m the status of the service ? journactl

For the upgrade, it is recommended use yunohost tools update & yunohost tools upgrade system, better than apt to avoid conflicts between repositories

Are you sure ?? I also have to on last weeks 2 different upgrade of mariadbā€¦

You can try to be sure of the problems of write a file some commands in a shell, create folders and files, and copy a data on this folder, just to analyze if you can write on the disk, because if you think you canā€™t, there is a big problem on the SD cardā€¦

yes i did

day ago.

i think the SD cart is working fine - files can get stored like i see here:

save

but there might be an issue with access rights or because keys not working rightā€¦ but this is just an guess - i do not at all understand how this all worksā€¦ but the system was working just fine up to this operation:

sudo apt-key del 95BD4743; wget -nv -O - ā€œhttps://packages.sury.org/php/apt.gpgā€ | sudo apt-key add -
root@my:~# yunohost tools update                                                                                       
Segmentation fault                                                                                                     
root@my:~# yunohost tools upgrade system                                                                               
Segmentation fault                                                                                                     
root@my:~# free -m                                                                                                     
               total        used        free      shared  buff/cache   available                                       
Mem:            7812        1161          76          55        6573        6472                                       
Swap:             99           0          99

wtf ā€¦ this really sounds like some sort of hardware issue ā€¦ can you try running python3 -c "print('hello')" ? And/or yunohost tools update --debug ?