@schard @Gerry_Ghetto
Hier eure gewünschten Infos, der Journal-Output ist gekürzt:
root# whoami
root
root# systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
● dbus.service loaded failed failed D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
kmod-static-nodes.service loaded active exited Create List of Static Device Nodes
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-network-generator.service loaded active exited Generate network units from Kernel command line
● systemd-networkd.service loaded failed failed Network Configuration
systemd-random-seed.service loaded active exited Load/Save OS Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev-early.service loaded active exited Create Static Device Nodes in /dev gracefully
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited Coldplug All udev Devices
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
systemd-update-utmp.service loaded active exited Record System Boot/Shutdown in UTMP
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Virtual Console Setup
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'.
root# systemctl start systemd-networkd.service
Job for systemd-networkd.service failed because the control process exited with error code.
See "systemctl status systemd-networkd.service" and "journalctl -xeu systemd-networkd.service" for details.
root# journalctl -xeu systemd-networkd.service
.
.
.
Sep 19 20:48:02 ws2 systemd[1]: Starting Network Configuration...
░░ Subject: A start job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 173.
Sep 19 20:48:02 ws2 (networkd)[610]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit systemd-networkd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 200.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-networkd.service has entered the 'failed' state with result 'exit-code'.
Sep 19 20:48:02 ws2 systemd[1]: Failed to start Network Configuration.
░░ Subject: A start job for unit systemd-networkd.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has finished with a failure.
░░
░░ The job identifier is 173 and the job result is failed.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit systemd-networkd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
.
.
.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Sep 19 20:48:02 ws2 systemd[1]: Failed to start Network Configuration.
root# systemctl status systemd-networkd.socket
× systemd-networkd.socket - Network Service Netlink Socket
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.socket; enabled; preset: disabled)
Active: failed (Result: service-start-limit-hit) since Tue 2023-09-19 20:48:02 CEST; 224ms ago
Duration: 342ms
Triggers: ● systemd-networkd.service
Docs: man:systemd-networkd.service(8)
man:rtnetlink(7)
Listen: route 1361 (Netlink)
Sep 19 20:48:02 ws2 systemd[1]: Listening on Network Service Netlink Socket.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.socket: Failed with result 'service-start-limit-hit'.
root# systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Tue 2023-09-19 20:44:49 CEST; 3min 12s ago
TriggeredBy: ● systemd-journald.socket
● systemd-journald-dev-log.socket
○ systemd-journald-audit.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 391 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 38214)
FD Store: 2 (limit: 4224)
Memory: 12.6M
CPU: 116ms
CGroup: /system.slice/systemd-journald.service
└─391 /usr/lib/systemd/systemd-journald
Sep 19 20:44:49 ws2 systemd-journald[391]: Collecting audit messages is disabled.
Sep 19 20:44:49 ws2 systemd-journald[391]: Journal started
Sep 19 20:44:49 ws2 systemd-journald[391]: Runtime Journal (/run/log/journal/30965215e10047c8b6c13f02b26db77e) is 8.0M, max 1.5G, 1.5G free.
Sep 19 20:44:50 ws2 systemd-journald[391]: Time spent on flushing to /var/log/journal/30965215e10047c8b6c13f02b26db77e is 647.259ms for 907 entries.
Sep 19 20:44:50 ws2 systemd-journald[391]: System Journal (/var/log/journal/30965215e10047c8b6c13f02b26db77e) is 59.1M, max 4.0G, 3.9G free.
Sep 19 20:44:53 ws2 systemd-journald[391]: Received client request to flush runtime journal.
Sep 19 20:44:53 ws2 systemd-journald[391]: /var/log/journal/30965215e10047c8b6c13f02b26db77e/system.journal: Journal file uses a different sequence number ID, rotating.
Sep 19 20:44:53 ws2 systemd-journald[391]: Rotating system journal.
Notice: journal has been rotated since unit was started, output may be incomplete.
root# systemctl status systemd-journald.socket
● systemd-journald.socket - Journal Socket
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.socket; static)
Active: active (running) since Tue 2023-09-19 20:44:49 CEST; 3min 12s ago
Triggers: ● systemd-journald.service
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Listen: /run/systemd/journal/socket (Datagram)
/run/systemd/journal/stdout (Stream)
CGroup: /system.slice/systemd-journald.socket
Notice: journal has been rotated since unit was started, output may be incomplete.
root# networkctl status
systemd-networkd is not running, output might be incomplete.
● State: n/a
Online state: unknown
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4.
Sep 19 20:48:02 ws2 systemd[1]: Starting Network Configuration...
Sep 19 20:48:02 ws2 (networkd)[615]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=200/CHDIR
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Sep 19 20:48:02 ws2 systemd[1]: Failed to start Network Configuration.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Sep 19 20:48:02 ws2 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Sep 19 20:48:02 ws2 systemd[1]: Failed to start Network Configuration.
Moderativer Edit: Code bitte in Codeblöcke einfassen. Ich habs mal erledigt, ansonsten steht hier wie das geht 🙂