The mysterious home server stacking issue has been resolved since updating to devuan 6.12.74+deb13+1-amd64
Hello, I'm Incompetent.
The mysterious stacking issue that has been bothering me since the end of February, which doesn't even leave a trace in syslog, has probably been resolved?
I still don't know what the cause itself was, but it was quite frustrating when nothing was left in the logs, and I even wondered if it was a hardware failure.
- RAM replacement
- Changing used slots, etc.
- Motherboard replacement
- PSU replacement
Even after doing all this, the phenomenon didn't change, so it was a very difficult situation.
It was a situation where it was stacking twice a day.
And if there's anything I can think of that fixed it, it's updating to the following packages:
dpkg:amd64
libmagickcore-7.q16-10:amd64
libc6-i386:amd64
mariadb-plugin-provider-bzip2:amd64
libmariadb-dev-compat:amd64
openssh-client:amd64
mariadb-server:amd64
python3-brlapi:amd64
imagemagick-7-common:amd64
postgresql-17:amd64
gpg:amd64
tzdata:amd64
xbrlapi:amd64
libldb2:amd64
mariadb-client-core:amd64
chrony:amd64
busybox:amd64
libbrlapi0.8:amd64
ssh:amd64
node-https-proxy-agent:amd64
libcap2-bin:amd64
libext2fs2t64:amd64
grub-pc-bin:amd64
grub-efi-ia32-unsigned:amd64
mariadb-plugin-provider-lzma:amd64
python3-jaraco.context:amd64
openssl-provider-legacy:amd64
python3-requests:amd64
mariadb-server-core:amd64
libwbclient0:amd64
openssh-server:amd64
wireless-regdb:amd64
gpg-wks-server:amd64
grub-efi-amd64-unsigned:amd64
libmagickwand-7.q16-10:amd64
tayga:amd64
gpg-agent:amd64
apache2-data:amd64
docker-cli:amd64
libcom-err2:amd64
docker.io:amd64
apache2-bin:amd64
libcap2:amd64
comerr-dev:amd64
libc6:amd64
locales:amd64
postgresql-client-17:amd64
dpkg-dev:amd64
libmagickcore-7.q16-10-extra:amd64
ifupdown:amd64
linux-image-amd64:amd64
linux-base:amd64
gpgv:amd64
libsmbclient0:amd64
bash:amd64
libsqlite3-dev:amd64
grub-efi-amd64-signed:amd64
libtdb1:amd64
linux-sysctl-defaults:amd64
libsndfile1:amd64
libssl-dev:amd64
mariadb-plugin-provider-snappy:amd64
libsqlite3-0:amd64
node-http-proxy-agent:amd64
gpgsm:amd64
mariadb-common:amd64
apache2-utils:amd64
grub-efi-amd64-bin:amd64
grub2-common:amd64
libtevent0t64:amd64
libdpkg-perl:amd64
libc-dev-bin:amd64
openssh-sftp-server:amd64
libc-l10n:amd64
grub-common:amd64
node-data-uri-to-buffer:amd64
samba-libs:amd64
libmariadb3:amd64
sudo:amd64
libc-bin:amd64
libc-devtools:amd64
apache2:amd64
mariadb-client:amd64
mariadb-plugin-provider-lz4:amd64
mariadb-plugin-provider-lzo:amd64
libssl3t64:amd64
libc6-dev:amd64
dirmngr:amd64
grub-efi-ia32-bin:amd64
gnupg-utils:amd64
libmariadb-dev:amd64
libmpg123-0t64:amd64
logsave:amd64
gpg-wks-client:amd64
sqlite3:amd64
tini:amd64
libtalloc2:amd64
libpq5:amd64
grub-pc:amd64
gpgconf:amd64
node-agent-base:amd64
libss2:amd64
openssl:amd64
e2fsprogs:amd64
linux-libc-dev:amd64Hmm, but it seems like a security update, so why would this update fix it?
It seems to be a fix for an AppArmor vulnerability.
You might say that the above hasn't changed much from before, but in reality, it was much worse before two days ago, as it kept crashing frequently and I had to restart it.
Actually, I still don't know for sure, but it's been running for over two days for the first time in a while, so I'm thinking it might be fixed, but I'll still have to wait and see.