systemctl gdm3 startet nicht selbst, Prompt kommt nicht Debian 11

KDE, Gnome, Windowmanager, X11, Grafiktreiber und alles was dazu notwendig ist. Schau auch in den "Tipps und Tricks"-Bereich.
Antworten
Benutzeravatar
xcomm
Beiträge: 793
Registriert: 21.09.2003 05:12:01
Wohnort: Europe
Kontaktdaten:

systemctl gdm3 startet nicht selbst, Prompt kommt nicht Debian 11

Beitrag von xcomm » 16.10.2021 10:37:26

Hi Gemeinde,

habe hier ein älteres System auf Debian 11 aktualisiert. Jetzt erreicht er beim Booten das Prompt nicht mehr und startet auch kein X.
SSH etc ist alles gestarted. Von da kann ich auch gdm3 manuell starten.
# gdm3 &

Ich bin leider noch nicht besonders firm mit systemd.

Die Ausgabe sieht für mich aus, als seien 2 Dinge nicht aktiviert? Wie mache ich die an:

Code: Alles auswählen

boark:(/var/log)# systemctl list-units --type target
  UNIT                               LOAD   ACTIVE   SUB    JOB   DESCRIPTION
  basic.target                       loaded active   active       Basic System
  blockdev@dev-mapper-md2open.target loaded active   active       Block Device Preparation for /dev/mapper/md2open
  blockdev@dev-mapper-md3open.target loaded active   active       Block Device Preparation for /dev/mapper/md3open
  cryptsetup.target                  loaded active   active       Local Encrypted Volumes
  getty.target                       loaded active   active       Login Prompts
  graphical.target                   loaded inactive dead   start Graphical Interface
  local-fs-pre.target                loaded active   active       Local File Systems (Pre)
  local-fs.target                    loaded active   active       Local File Systems
  multi-user.target                  loaded inactive dead   start Multi-User System
  network-online.target              loaded active   active       Network is Online
  network.target                     loaded active   active       Network
  nss-user-lookup.target             loaded active   active       User and Group Name Lookups
  paths.target                       loaded active   active       Paths
  remote-fs.target                   loaded active   active       Remote File Systems
  slices.target                      loaded active   active       Slices
  sockets.target                     loaded active   active       Sockets
  sound.target                       loaded active   active       Sound Card
  swap.target                        loaded active   active       Swap
  sysinit.target                     loaded active   active       System Initialization
  timers.target                      loaded active   active       Timers

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.

20 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
boark:(/var/log)#  systemctl is-enabled multi-user.target.service
enabled
Failed to get unit file state for multi-user.target.service: No such file or directory
-bash: enabled: Kommando nicht gefunden.

Code: Alles auswählen

systemctl enable gdm3
Synchronizing state of gdm3.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gdm3
insserv: script virtualbox: service vboxdrv already provided!
insserv: script virtualbox: service virtualbox already provided!
insserv: script virtualbox: service vboxdrv already provided!
insserv: script virtualbox: service virtualbox already provided!
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
boark:(/var/log)# systemctl start gdm3
Ich nehme mal an, ich müsste das aktiviert bekommen?
multi-user.target loaded inactive dead start Multi-User System
graphical.target loaded inactive dead start Graphical Interface

Danke, xcomm

Benutzeravatar
jph
Beiträge: 1049
Registriert: 06.12.2015 15:06:07
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: Greven/Westf.

Re: systemctl gdm3 startet nicht selbst, Prompt kommt nicht Debian 11

Beitrag von jph » 16.10.2021 22:36:00

Falsche Unit erwischt – gdm3 wird über gdm.service, nicht gdm3.service gestartet.

Benutzeravatar
xcomm
Beiträge: 793
Registriert: 21.09.2003 05:12:01
Wohnort: Europe
Kontaktdaten:

Re: systemctl gdm3 startet nicht selbst, Prompt kommt nicht Debian 11

Beitrag von xcomm » 17.10.2021 09:27:39

Targets sind nun aktiviert.

Code: Alles auswählen

systemctl list-units --type target
  UNIT                               LOAD   ACTIVE SUB    DESCRIPTION
  basic.target                       loaded active active Basic System
  blockdev@dev-mapper-md2open.target loaded active active Block Device Preparation for /dev/mapper/md2open
  blockdev@dev-mapper-md3open.target loaded active active Block Device Preparation for /dev/mapper/md3open
  cryptsetup.target                  loaded active active Local Encrypted Volumes
  getty.target                       loaded active active Login Prompts
  local-fs-pre.target                loaded active active Local File Systems (Pre)
  local-fs.target                    loaded active active Local File Systems
  multi-user.target                  loaded active active Multi-User System
  network-online.target              loaded active active Network is Online
  network.target                     loaded active active Network
  nss-user-lookup.target             loaded active active User and Group Name Lookups
  paths.target                       loaded active active Paths
  remote-fs.target                   loaded active active Remote File Systems
  slices.target                      loaded active active Slices
  sockets.target                     loaded active active Sockets
  sound.target                       loaded active active Sound Card
  swap.target                        loaded active active Swap
  sysinit.target                     loaded active active System Initialization
  timers.target                      loaded active active Timers

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
19 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Prompt erreicht er aber aktuell nicht. Ich komme per SSH drauf:

Code: Alles auswählen

systemd-analyze 
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs

Code: Alles auswählen

systemctl list-jobs
JOB  UNIT                                 TYPE  STATE
1    multi-user.target                    start waiting
4197 getty@tty4.service                   start waiting
114  rc-local.service                     start running
180  systemd-update-utmp-runlevel.service start waiting
5043 getty@tty6.service                   start waiting
4338 getty@tty5.service                   start waiting
3915 getty@tty2.service                   start waiting
4056 getty@tty3.service                   start waiting

Code: Alles auswählen

systemctl stop rc-local.service
Danach startet nun auch der gdm3, aber nur mit Backportet-Kernel
i linux-image-5.7.0-0.bpo.2-amd64:amd64
statt Debian 11
i linux-image-5.10.0-9-amd64:amd64

Problem Prompt:
Wie könnte man genauer rausfinden, woran es bei Target rc.local.service genau liegt und hängt?

Problem GDM:
Der startet jetzt

Danke, xcomm

Antworten