I don't remember all the steps I've made.
I tried so many things.
But I've found that some processes were complaining that selinux
filesystem was not mounted.
Mounted the filesystem with the command "cat /etc/systemd/system.conf"
and it helped starting some process.
That time, even if the filesystem is mounted, the services do not want
to start :/
I guess my systemd.conf is default
--
❯ cat /etc/systemd/system.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See systemd-system.conf(5) for details.
[Manager]
#LogLevel=info
#LogTarget=journal-or-kmsg
#LogColor=yes
#LogLocation=no
#LogTime=no
#DumpCore=yes
#ShowStatus=yes
#CrashChangeVT=no
#CrashShell=no
#CrashReboot=no
#CtrlAltDelBurstAction=reboot-force
#CPUAffinity=1 2
#NUMAPolicy=default
#NUMAMask=
#RuntimeWatchdogSec=0
#RebootWatchdogSec=10min
#ShutdownWatchdogSec=10min
#KExecWatchdogSec=0
#WatchdogDevice=
#CapabilityBoundingSet=
#NoNewPrivileges=no
#SystemCallArchitectures=
#TimerSlackNSec=
#StatusUnitFormat=description
#DefaultTimerAccuracySec=1min
#DefaultStandardOutput=journal
#DefaultStandardError=inherit
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
#DefaultTimeoutAbortSec=
#DefaultRestartSec=100ms
#DefaultStartLimitIntervalSec=10s
#DefaultStartLimitBurst=5
#DefaultEnvironment=
#DefaultCPUAccounting=no
#DefaultIOAccounting=no
#DefaultIPAccounting=no
#DefaultBlockIOAccounting=no
#DefaultMemoryAccounting=yes
#DefaultTasksAccounting=yes
#DefaultTasksMax=15%
#DefaultLimitCPU=
#DefaultLimitFSIZE=
#DefaultLimitDATA=
#DefaultLimitSTACK=
#DefaultLimitCORE=
#DefaultLimitRSS=
#DefaultLimitNOFILE=1024:524288
#DefaultLimitAS=
#DefaultLimitNPROC=
#DefaultLimitMEMLOCK=
#DefaultLimitLOCKS=
#DefaultLimitSIGPENDING=
#DefaultLimitMSGQUEUE=
#DefaultLimitNICE=
#DefaultLimitRTPRIO=
#DefaultLimitRTTIME=
--
I have no idea what is this "."...
I know I've disabled apparmor and selinux in the past because too many
processes were blocked by them
Le 01/02/2023 à 14:40, David a écrit :
On Thu, 2 Feb 2023 at 00:07, Freyja<sio...@sioban.net> 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 to notice:
root in /var/log
❯ ls -la journal/
total 44
drwxr-sr-x+ 3 root systemd-journal 4096 Aug 19 2021 .
drwxr-xr-x. 33 root root 12288 Feb 1 06:25 ..
^
On my system I do not have the '.' character in column 11
which you show in your output line that I have quoted
immediately above. I don't know anything about that or
if is relevant, just mentioning it in case someone else
can comment on that.
Command
info -f coreutils -n 'What information is listed'
says:
Following the file mode bits is a single character that specifies
whether an alternate access method such as an access control list
applies to the file. When the character following the file mode
bits is a space, there is no alternate access method. When it is a
printing character, then there is such a method.
GNU ‘ls’ uses a ‘.’ character to indicate a file with a security
context, but no other alternate access method.
