a kernel update
Many thanks to all people involved in this thread and sorry that it took
me so long to answer, I was missing the energy to look deeper.
Today I just rebooted after a kernel update (5.10.0-20) and the problem
was gone...
Le 03/02/2023 à 09:59, Freyja a écrit :
I need to look
I need to look deeper in your recommendations, I will try them as soon
as I can.
Le 02/02/2023 à 17:28, songbird a écrit :
debian-u...@howorth.org.uk wrote:
...
Maybe it's worth asking on the systemd-devel mailing list?
did you reinstall rsyslog? did you purge the configs for it
(back th
I've tried they sent me back here :/
Le 02/02/2023 à 17:06, debian-u...@howorth.org.uk a écrit :
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some
packages:
I would consider complete reinstall (install from scratch). It may be
faster
Hi,
Both are installed but when I try to remove them it want to remove too
many packages :/
--
❯ dpkg -l |grep selinux
ii libselinux1:amd64
3.1-3 amd64 SELinux
runtime shared libraries
--
--
❯ apt-get remove libselinux1
Reading package list
n
unknown reason (but that's a long time ago)
Le 02/02/2023 à 13:15, Max Nikulin a écrit :
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some packages:
I would consider complete reinstall (install from scratch). It may be
faster even
ket has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit systemd-udevd-kernel.socket has finished with a
failure.
░░
░░ The job identifier is 5431 and the job result is failed.
--
Le 02/02/2023 à 12:58, songbird a écrit :
Freyja wrote:
...
Howev
n
unknown reason (but that's a long time ago)
Le 02/02/2023 à 13:15, Max Nikulin a écrit :
On 01/02/2023 21:48, Freyja wrote:
Instead of just creating the folders, I've reinstalled some packages:
I would consider complete reinstall (install from scratch). It may be
faster even
pe.
2 loaded units listed.
--
However journalctl still stucks on 24th Oct:
--
❯ journalctl -b
-- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon
2022-10-24 14:14:33 CEST. --
-- No entries --
--
Le 01/02/2023 à 15:32, Charles Curley a écrit :
On Wed, 1 Feb 2023 13:26:58 +0100
F
2023 à 14:40, David a écrit :
On Thu, 2 Feb 2023 at 00:07, Freyja wrote:
I've already tried to solve this issue in December with some success
Hi, could you describe in detail what you did?
Can you also post the output of:
cat /etc/systemd/system.conf
Also, a small thing I happened t
ystemd-journal 8388608 Oct 24 14:14 user-1000.journal
-rw-r-+ 1 root systemd-journal 8388608 Oct 23 19:56 user-1014.journal
-rw-r-+ 1 root systemd-journal 8388608 Oct 24 14:14 user-1015.journal
--
And here are our logs from the 24th October.
Le 01/02/2023 à 13:26, Freyja a écrit :
Hi
Hi greg,
--
❯ df /run
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1629236 3732 1625504 1% /run
--
For /run/systemd/journal/socket this is another story.
The folder journal does not exist at all.
--
❯ ls -la /run/systemd/
total 0
drwxr-xr-x 17 root r
11 matches
Mail list logo
