您尚未登录。

#1 2023-02-01 22:56:32

akumaexs
会员
注册时间: 2023-01-12
帖子: 19

systemd-nspawn无法验证密码

下载了ArchLinuxARM-armv7-latest.tar.gz ,并且安装了qemu-user-static

当我试图

 sudo systemd-nspawn -D path/rootfs -b 

启动时,root账户无法登录

 Login incorrect 

,如果使用自己设置的账户登录时出现,

 login: timed out after 60 seconds 

以下是

 systemd 252.4-2-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
Detected virtualization systemd-nspawn.
Detected architecture arm.

Welcome to Arch Linux ARM!

Hostname set to <alarm>.
bpf-lsm: BPF LSM hook not enabled in the kernel, BPF LSM not supported
Queued start job for default target Graphical Interface.
[  OK  ] Created slice Slice /system/getty.
[  OK  ] Created slice Slice /system/modprobe.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Local Integrity Protected Volumes.
[  OK  ] Reached target Path Units.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slice Units.
[  OK  ] Reached target Swaps.
[  OK  ] Reached target Local Verity Protected Volumes.
[  OK  ] Listening on Device-mapper event daemon FIFOs.
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
         Mounting Huge Pages File System...
         Mounting FUSE Control File System...
systemd-journald.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
(This warning is only shown for the first unit using IP firewalling.)
         Starting Journal Service...
         Starting Generate network units from Kernel command line...
         Starting Remount Root and Kernel File Systems...
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Finished Generate network units from Kernel command line.
[  OK  ] Reached target Preparation for Network.
[  OK  ] Started Journal Service.
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
         Starting Flush Journal to Persistent Storage...
         Starting Create Static Device Nodes in /dev...
[FAILED] Failed to start Create Static Device Nodes in /dev.
See 'systemctl status systemd-tmpfiles-setup-dev.service' for details.
[  OK  ] Reached target Preparation for Local File Systems.
[  OK  ] Reached target Local File Systems.
[  OK  ] Finished Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
         Starting Network Name Resolution...
[  OK  ] Reached target System Time Set.
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Refresh existing PGP keys of archlinux-keyring regularly.
[  OK  ] Started Daily verification of password and group files.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timer Units.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
         Starting D-Bus System Message Bus...
[  OK  ] Started OpenSSH Daemon.
         Starting User Login Management...
         Starting Permit User Sessions...
[  OK  ] Started Verify integrity of password and group files.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Console Getty.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started User Login Management.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.

Arch Linux 6.1.8-arch1-1 (pts/0) 

最近编辑记录 akumaexs (2023-02-01 22:57:26)

离线

#2 2023-02-01 23:03:59

akumaexs
会员
注册时间: 2023-01-12
帖子: 19

Re: systemd-nspawn无法验证密码

以如下方式启动rootfs

 sudo systemd-nspawn -D path/rootfs 

输入 <code> journalctl -r </code> 后,显示如下

 Feb 01 22:57:40 alarm systemd[1]: Stopped Console Getty.
Feb 01 22:57:40 alarm systemd[1]: console-getty.service: Scheduled restart job, restart counter is at 3.
Feb 01 22:57:39 alarm systemd[1]: console-getty.service: Deactivated successfully.
Feb 01 22:56:14 alarm systemd[1]: user@1001.service: start operation timed out. Terminating.
Feb 01 22:55:35 alarm systemd[1]: Started Console Getty.
Feb 01 22:55:35 alarm systemd[1]: Stopped Console Getty.
Feb 01 22:55:35 alarm systemd[1]: console-getty.service: Scheduled restart job, restart counter is at 2.
Feb 01 22:55:35 alarm systemd[1]: console-getty.service: Deactivated successfully.
Feb 01 22:54:44 alarm systemd[114]: Listening on p11-kit server.
Feb 01 22:54:44 alarm systemd[114]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 01 22:54:44 alarm systemd[114]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 01 22:54:44 alarm systemd[114]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 01 22:54:44 alarm systemd[114]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 01 22:54:44 alarm systemd[114]: Listening on GnuPG network certificate management daemon.
Feb 01 22:54:44 alarm systemd[114]: Starting D-Bus User Message Bus Socket...
Feb 01 22:54:44 alarm systemd[114]: Reached target Timers.
Feb 01 22:54:44 alarm systemd[114]: Reached target Paths.
Feb 01 22:54:44 alarm systemd[114]: Created slice User Application Slice.
Feb 01 22:54:44 alarm systemd[114]: Queued start job for default target Main User Target.
Feb 01 22:54:44 alarm systemd[114]: Failed to make us a subreaper, ignoring: Invalid argument
Feb 01 22:54:44 alarm systemd[114]: pam_unix(systemd-user:session): session opened for user akuma(uid=1001) by (uid=0)
Feb 01 22:54:44 alarm systemd[114]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[akuma] ruser=[<unknown>] rhost=[<unknown>]
Feb 01 22:54:44 alarm systemd[114]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 01 22:54:44 alarm dbus-daemon[75]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Feb 01 22:54:44 alarm dbus-daemon[75]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.5' (uid=0 pid=114 comm="/usr/bin/qemu-arm-static /usr/lib/systemd/>
Feb 01 22:54:44 alarm systemd[1]: Starting User Manager for UID 1001...
Feb 01 22:54:44 alarm systemd[1]: Finished User Runtime Directory /run/user/1001.
Feb 01 22:54:44 alarm systemd-logind[79]: New session 9 of user akuma.
Feb 01 22:54:44 alarm systemd[1]: Starting User Runtime Directory /run/user/1001...
Feb 01 22:54:44 alarm systemd[1]: Created slice User Slice of UID 1001.
Feb 01 22:54:44 alarm login[107]: pam_unix(login:session): session opened for user akuma(uid=1001) by (uid=0)
Feb 01 22:54:40 alarm login[107]: FAILED LOGIN 1 FROM pts/0 FOR akuma, Authentication failure
Feb 01 22:54:37 alarm login[107]: pam_unix(login:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/pts/0 ruser= rhost=  user=akuma
Feb 01 22:54:35 alarm login[107]: pam_systemd_home(login:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 01 22:54:35 alarm dbus-daemon[75]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Feb 01 22:54:35 alarm dbus-daemon[75]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.3' (uid=0 pid=107 comm="/usr/bin/qemu-arm-static /bin/login /bin/l>
Feb 01 22:54:26 alarm systemd[1]: Started Console Getty.
Feb 01 22:54:26 alarm systemd[1]: Stopped Console Getty.
Feb 01 22:54:26 alarm systemd[1]: console-getty.service: Scheduled restart job, restart counter is at 1.
Feb 01 22:54:26 alarm systemd[1]: console-getty.service: Deactivated successfully.
Feb 01 22:53:56 alarm dbus-daemon[75]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30029ms)
Feb 01 22:53:30 alarm login[90]: FAILED LOGIN 1 FROM pts/0 FOR root, Authentication failure
Feb 01 22:53:26 alarm login[90]: pam_securetty(login:auth): access denied: tty 'pts/0' is not secure !
Feb 01 22:53:24 alarm systemd[1]: Failed to start OpenSSH Daemon.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Start request repeated too quickly.
Feb 01 22:53:24 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:24 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 5.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 01 22:53:24 alarm sshd[103]: fatal: Cannot bind any address.
Feb 01 22:53:24 alarm sshd[103]: error: Bind to port 22 on :: failed: Address already in use.
Feb 01 22:53:24 alarm sshd[103]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 01 22:53:24 alarm systemd[1]: Started OpenSSH Daemon.
Feb 01 22:53:24 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:24 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 4.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:24 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 01 22:53:24 alarm sshd[100]: fatal: Cannot bind any address.
Feb 01 22:53:24 alarm sshd[100]: error: Bind to port 22 on :: failed: Address already in use.
Feb 01 22:53:24 alarm sshd[100]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 01 22:53:23 alarm systemd[1]: Started OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:23 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 3.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 01 22:53:23 alarm sshd[97]: fatal: Cannot bind any address.
Feb 01 22:53:23 alarm sshd[97]: error: Bind to port 22 on :: failed: Address already in use.
Feb 01 22:53:23 alarm sshd[97]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 01 22:53:23 alarm systemd[1]: Started OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:23 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 2.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 01 22:53:23 alarm sshd[94]: fatal: Cannot bind any address.
Feb 01 22:53:23 alarm sshd[94]: error: Bind to port 22 on :: failed: Address already in use.
Feb 01 22:53:23 alarm sshd[94]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 01 22:53:23 alarm systemd[1]: Started OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:23 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 1.
Feb 01 22:53:23 alarm systemd[1]: Startup finished in 1.470s.
Feb 01 22:53:23 alarm systemd[1]: Reached target Graphical Interface.
Feb 01 22:53:23 alarm systemd[1]: Reached target Multi-User System.
Feb 01 22:53:23 alarm systemd[1]: Started User Login Management.
Feb 01 22:53:23 alarm systemd-logind[79]: New seat seat0.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 01 22:53:23 alarm sshd[77]: fatal: Cannot bind any address.
Feb 01 22:53:23 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 01 22:53:23 alarm sshd[77]: error: Bind to port 22 on :: failed: Address already in use.
Feb 01 22:53:23 alarm sshd[77]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 01 22:53:23 alarm systemd[1]: Started D-Bus System Message Bus.
Feb 01 22:53:23 alarm systemd[1]: Reached target Login Prompts.
Feb 01 22:53:23 alarm systemd[1]: Getty on tty1 was skipped because of an unmet condition check (ConditionPathExists=/dev/tty0).
Feb 01 22:53:23 alarm systemd[1]: Started Console Getty.
Feb 01 22:53:23 alarm systemd[1]: Finished Permit User Sessions.
Feb 01 22:53:22 alarm systemd[1]: shadow.service: Failed with result 'exit-code'.
Feb 01 22:53:22 alarm systemd[1]: shadow.service: Main process exited, code=exited, status=225/NETWORK
Feb 01 22:53:22 alarm systemd[85]: shadow.service: Failed at step NETWORK spawning /bin/sh: Input/output error
Feb 01 22:53:22 alarm systemd[85]: shadow.service: Failed to set up network namespacing: Input/output error
Feb 01 22:53:22 alarm systemd[1]: Started Verify integrity of password and group files.
Feb 01 22:53:22 alarm systemd[1]: Starting Permit User Sessions...
Feb 01 22:53:22 alarm systemd[1]: Starting User Login Management...
Feb 01 22:53:22 alarm systemd[1]: Started OpenSSH Daemon.
Feb 01 22:53:22 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 01 22:53:22 alarm systemd[1]: Starting D-Bus System Message Bus...
Feb 01 22:53:22 alarm systemd[1]: Reached target Basic System.
Feb 01 22:53:22 alarm systemd[1]: Reached target Socket Units.
Feb 01 22:53:22 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 01 22:53:22 alarm systemd[1]: Reached target Timer Units.
Feb 01 22:53:22 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Feb 01 22:53:22 alarm systemd[1]: Started Daily verification of password and group files.
Feb 01 22:53:22 alarm systemd[1]: Started Refresh existing PGP keys of archlinux-keyring regularly.
Feb 01 22:53:22 alarm systemd[1]: Reached target System Initialization.
Feb 01 22:53:22 alarm systemd[1]: Reached target Host and Network Name Lookups.
Feb 01 22:53:22 alarm systemd[1]: Reached target Network.
Feb 01 22:53:22 alarm systemd[1]: Started Network Name Resolution.
Feb 01 22:53:22 alarm systemd-resolved[69]: Using system hostname 'alarm'.
Feb 01 22:53:22 alarm systemd-resolved[69]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa >
Feb 01 22:53:22 alarm systemd-resolved[69]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 01 22:53:22 alarm systemd-resolved[69]: Positive Trust Anchors:
Feb 01 22:53:22 alarm systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Feb 01 22:53:22 alarm systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Feb 01 22:53:22 alarm systemd[1]: Update is Completed was skipped because no trigger condition checks were met.
Feb 01 22:53:22 alarm systemd[1]: Reached target System Time Set.
Feb 01 22:53:22 alarm systemd[1]: Network Time Synchronization was skipped because of an unmet condition check (ConditionVirtualization=!container).
Feb 01 22:53:22 alarm systemd[1]: Starting Network Name Resolution...
Feb 01 22:53:22 alarm systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var).
Feb 01 22:53:22 alarm systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 01 22:53:22 alarm systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
Feb 01 22:53:22 alarm systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=243/CREDENTIALS
Feb 01 22:53:22 alarm systemd[67]: systemd-tmpfiles-setup.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 01 22:53:22 alarm systemd[67]: systemd-tmpfiles-setup.service: Failed to set up credentials: Invalid argument
Feb 01 22:53:22 alarm systemd[1]: Starting Create Volatile Files and Directories...
Feb 01 22:53:22 alarm systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 01 22:53:22 alarm systemd-journald[45]: System Journal (/var/log/journal/d154a054480b48b3bea06fe96c2652d2) is 176.0M, max 1.2G, 1.0G free.
Feb 01 22:53:22 alarm systemd-journald[45]: Time spent on flushing to /var/log/journal/d154a054480b48b3bea06fe96c2652d2 is 8.874ms for 31 entries.
Feb 01 22:53:22 alarm systemd[1]: Network Configuration was skipped because of an unmet condition check (ConditionCapability=CAP_NET_ADMIN).
Feb 01 22:53:22 alarm systemd[1]: Rule-based Manager for Device Events and Files was skipped because of an unmet condition check (ConditionPathIsReadWrite=/sys).
Feb 01 22:53:22 alarm systemd[1]: Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id).
Feb 01 22:53:22 alarm systemd[1]: Set Up Additional Binary Formats was skipped because of an unmet condition check (ConditionPathIsReadWrite=/proc/sys).
Feb 01 22:53:22 alarm systemd[1]: Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met.
Feb 01 22:53:22 alarm systemd[1]: Reached target Local File Systems.
Feb 01 22:53:22 alarm systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/machines.raw).
Feb 01 22:53:22 alarm systemd[1]: Reached target Preparation for Local File Systems.
Feb 01 22:53:22 alarm systemd[1]: Failed to start Create Static Device Nodes in /dev.
Feb 01 22:53:22 alarm systemd[1]: systemd-tmpfiles-setup-dev.service: Failed with result 'exit-code'.
Feb 01 22:53:22 alarm systemd[1]: systemd-tmpfiles-setup-dev.service: Main process exited, code=exited, status=243/CREDENTIALS
Feb 01 22:53:22 alarm systemd[63]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 01 22:53:22 alarm systemd[63]: systemd-tmpfiles-setup-dev.service: Failed to set up credentials: Invalid argument
Feb 01 22:53:22 alarm systemd[1]: Starting Create Static Device Nodes in /dev...
Feb 01 22:53:22 alarm systemd[1]: Create System Users was skipped because no trigger condition checks were met.
Feb 01 22:53:22 alarm systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Feb 01 22:53:22 alarm systemd[1]: Load/Save Random Seed was skipped because of an unmet condition check (ConditionVirtualization=!container).
Feb 01 22:53:22 alarm systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 01 22:53:22 alarm systemd[1]: Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc).
Feb 01 22:53:22 alarm systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Feb 01 22:53:22 alarm systemd[1]: Failed to start Remount Root and Kernel File Systems.
Feb 01 22:53:22 alarm systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
Feb 01 22:53:22 alarm systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 22:53:22 alarm systemd-remount-fs[57]:        dmesg(1) may have more information after failed mount system call.
Feb 01 22:53:22 alarm systemd-remount-fs[57]: mount: /sys: mount point not mounted or bad option.
Feb 01 22:53:22 alarm systemd-remount-fs[55]:        dmesg(1) may have more information after failed mount system call.
Feb 01 22:53:22 alarm systemd-remount-fs[55]: mount: /proc: mount point not mounted or bad option.
Feb 01 22:53:22 alarm systemd-remount-fs[50]: /usr/bin/mount for /sys exited with exit status 32.
Feb 01 22:53:22 alarm systemd-remount-fs[50]: /usr/bin/mount for /proc exited with exit status 32.
Feb 01 22:53:22 alarm systemd-journald[45]: Runtime Journal (/run/log/journal/d154a054480b48b3bea06fe96c2652d2) is 8.0M, max 276.6M, 268.6M free.
Feb 01 22:53:22 alarm systemd-journald[45]: Journal started
-- Boot 41fa703d91fa47d289fbe5ea89ecc477 -- 

离线

#3 2023-02-02 14:52:07

matrikslee
会员
注册时间: 2017-04-21
帖子: 442
个人网站

Re: systemd-nspawn无法验证密码

有把rootfs里面的/etc/shadow文件中root账户的哈希值改成主系统/etc/shadow的吗?

离线

#4 2023-02-02 18:21:45

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 8,384
个人网站

Re: systemd-nspawn无法验证密码

你这好多报错啊。用 journalctl -D 目录 的方式去看看日志吧。

离线

#5 2023-02-02 20:21:03

akumaexs
会员
注册时间: 2023-01-12
帖子: 19

Re: systemd-nspawn无法验证密码

matrikslee 说:

有把rootfs里面的/etc/shadow文件中root账户的哈希值改成主系统/etc/shadow的吗?

没有改成主系统的hash,我用的是默认的密码登录的(如果没记错的话应该密码就是root吧)

需要换成把rootfs的shadow换成主机的吗?(试了一下,改了以后也依旧是incorrect)

离线

#6 2023-02-02 20:40:32

akumaexs
会员
注册时间: 2023-01-12
帖子: 19

Re: systemd-nspawn无法验证密码

依云 说:

你这好多报错啊。用 journalctl -D 目录 的方式去看看日志吧。

我在 chroot 下执行<code> journalctl -D /var/log/journalctl -e </code> 可以吗

实质上主要就几个error,分别是tmpfile相关,和SSH相关

  1. Feb 02 20:16:38 alarm systemd[55]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument

  2. Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed to set up credentials: Invalid argument
    Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
    Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=243/CREDENTIALS
    Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
    Feb 02 20:16:38 alarm systemd[1]: Failed to start Create Volatile Files and Directories.

  3. Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
    Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on :: failed: Address already in use.
    Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
    Feb 02 20:16:39 alarm sshd[71]: fatal: Cannot bind any address.
    Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
    Feb 02 20:16:40 alarm systemd[1]: sshd.service: Start request repeated too quickly.
    Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
    Feb 02 20:16:40 alarm systemd[1]: Failed to start OpenSSH Daemon.

  4. Feb 02 20:16:46 alarm login[80]: pam_systemd(login:session): Failed to create session: Input/output error

完整内容如下

 
Feb 02 20:16:38 alarm systemd-journald[45]: Journal started
Feb 02 20:16:38 alarm systemd-journald[45]: Runtime Journal (/run/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 8.0M, max 276.6M, 268.6M free.
Feb 02 20:16:38 alarm systemd[55]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 02 20:16:38 alarm systemd-journald[45]: Time spent on flushing to /var/log/journal/0f965e568f3d4fa69e6bd24a8620883a is 5.392ms for 4 entries.
Feb 02 20:16:38 alarm systemd-journald[45]: System Journal (/var/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 80.0M, max 1.2G, 1.1G free.
Feb 02 20:16:38 alarm systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 02 20:16:38 alarm systemd[1]: Starting Create Volatile Files and Directories...
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed to set up credentials: Invalid argument
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=243/CREDENTIALS
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
Feb 02 20:16:38 alarm systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 02 20:16:38 alarm systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var).
Feb 02 20:16:38 alarm systemd[1]: Starting Network Name Resolution...
Feb 02 20:16:38 alarm systemd[1]: Network Time Synchronization was skipped because of an unmet condition check (ConditionVirtualization=!container).
Feb 02 20:16:38 alarm systemd[1]: Reached target System Time Set.
Feb 02 20:16:38 alarm systemd[1]: Update is Completed was skipped because no trigger condition checks were met.
Feb 02 20:16:38 alarm systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Feb 02 20:16:38 alarm systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Feb 02 20:16:39 alarm systemd-resolved[63]: Positive Trust Anchors:
Feb 02 20:16:39 alarm systemd-resolved[63]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 02 20:16:39 alarm systemd-resolved[63]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.a>
Feb 02 20:16:39 alarm systemd-resolved[63]: Using system hostname 'alarm'.
Feb 02 20:16:39 alarm systemd[1]: Started Network Name Resolution.
Feb 02 20:16:39 alarm systemd[1]: Reached target Network.
Feb 02 20:16:39 alarm systemd[1]: Reached target Host and Network Name Lookups.
Feb 02 20:16:39 alarm systemd[1]: Reached target System Initialization.
Feb 02 20:16:39 alarm systemd[1]: Started Refresh existing PGP keys of archlinux-keyring regularly.
Feb 02 20:16:39 alarm systemd[1]: Started Daily verification of password and group files.
Feb 02 20:16:39 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Feb 02 20:16:39 alarm systemd[1]: Reached target Timer Units.
Feb 02 20:16:39 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 02 20:16:39 alarm systemd[1]: Reached target Socket Units.
Feb 02 20:16:39 alarm systemd[1]: Reached target Basic System.
Feb 02 20:16:39 alarm systemd[1]: Starting D-Bus System Message Bus...
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: Starting User Login Management...
Feb 02 20:16:39 alarm systemd[1]: Starting Permit User Sessions...
Feb 02 20:16:39 alarm systemd[1]: Finished Permit User Sessions.
Feb 02 20:16:39 alarm systemd[1]: Started Console Getty.
Feb 02 20:16:39 alarm systemd[1]: Getty on tty1 was skipped because of an unmet condition check (ConditionPathExists=/dev/tty0).
Feb 02 20:16:39 alarm systemd[1]: Reached target Login Prompts.
Feb 02 20:16:39 alarm systemd[1]: Started D-Bus System Message Bus.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm sshd[71]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd-logind[73]: New seat seat0.
Feb 02 20:16:39 alarm systemd[1]: Started User Login Management.
Feb 02 20:16:39 alarm systemd[1]: Reached target Multi-User System.
Feb 02 20:16:39 alarm systemd[1]: Reached target Graphical Interface.
Feb 02 20:16:39 alarm systemd[1]: Startup finished in 1.380s.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 1.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 2.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: fatal: Cannot bind any address.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 3.
Feb 02 20:16:40 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:40 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:40 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:38 alarm systemd-journald[45]: Journal started
Feb 02 20:16:38 alarm systemd-journald[45]: Runtime Journal (/run/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 8.0M, max 276.6M, 268.6M free.
Feb 02 20:16:38 alarm systemd[55]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 02 20:16:38 alarm systemd-journald[45]: Time spent on flushing to /var/log/journal/0f965e568f3d4fa69e6bd24a8620883a is 5.392ms for 4 entries.
Feb 02 20:16:38 alarm systemd-journald[45]: System Journal (/var/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 80.0M, max 1.2G, 1.1G free.
Feb 02 20:16:38 alarm systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 02 20:16:38 alarm systemd[1]: Starting Create Volatile Files and Directories...
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed to set up credentials: Invalid argument
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=243/CREDENTIALS
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
Feb 02 20:16:38 alarm systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 02 20:16:38 alarm systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var).
Feb 02 20:16:38 alarm systemd[1]: Starting Network Name Resolution...
Feb 02 20:16:38 alarm systemd[1]: Network Time Synchronization was skipped because of an unmet condition check (ConditionVirtualization=!container).
Feb 02 20:16:38 alarm systemd[1]: Reached target System Time Set.
Feb 02 20:16:38 alarm systemd[1]: Update is Completed was skipped because no trigger condition checks were met.
Feb 02 20:16:38 alarm systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Feb 02 20:16:38 alarm systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Feb 02 20:16:39 alarm systemd-resolved[63]: Positive Trust Anchors:
Feb 02 20:16:39 alarm systemd-resolved[63]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 02 20:16:39 alarm systemd-resolved[63]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.a>
Feb 02 20:16:39 alarm systemd-resolved[63]: Using system hostname 'alarm'.
Feb 02 20:16:39 alarm systemd[1]: Started Network Name Resolution.
Feb 02 20:16:39 alarm systemd[1]: Reached target Network.
Feb 02 20:16:39 alarm systemd[1]: Reached target Host and Network Name Lookups.
Feb 02 20:16:39 alarm systemd[1]: Reached target System Initialization.
Feb 02 20:16:39 alarm systemd[1]: Started Refresh existing PGP keys of archlinux-keyring regularly.
Feb 02 20:16:39 alarm systemd[1]: Started Daily verification of password and group files.
Feb 02 20:16:39 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Feb 02 20:16:39 alarm systemd[1]: Reached target Timer Units.
Feb 02 20:16:39 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 02 20:16:39 alarm systemd[1]: Reached target Socket Units.
Feb 02 20:16:39 alarm systemd[1]: Reached target Basic System.
Feb 02 20:16:39 alarm systemd[1]: Starting D-Bus System Message Bus...
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: Starting User Login Management...
Feb 02 20:16:39 alarm systemd[1]: Starting Permit User Sessions...
Feb 02 20:16:39 alarm systemd[1]: Finished Permit User Sessions.
Feb 02 20:16:39 alarm systemd[1]: Started Console Getty.
Feb 02 20:16:39 alarm systemd[1]: Getty on tty1 was skipped because of an unmet condition check (ConditionPathExists=/dev/tty0).
Feb 02 20:16:39 alarm systemd[1]: Reached target Login Prompts.
Feb 02 20:16:39 alarm systemd[1]: Started D-Bus System Message Bus.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm sshd[71]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd-logind[73]: New seat seat0.
Feb 02 20:16:39 alarm systemd[1]: Started User Login Management.
Feb 02 20:16:39 alarm systemd[1]: Reached target Multi-User System.
Feb 02 20:16:39 alarm systemd[1]: Reached target Graphical Interface.
Feb 02 20:16:39 alarm systemd[1]: Startup finished in 1.380s.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 1.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 2.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: fatal: Cannot bind any address.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 3.
Feb 02 20:16:40 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:40 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:40 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:38 alarm systemd-journald[45]: Journal started
Feb 02 20:16:38 alarm systemd-journald[45]: Runtime Journal (/run/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 8.0M, max 276.6M, 268.6M free.
Feb 02 20:16:38 alarm systemd[55]: systemd-tmpfiles-setup-dev.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 02 20:16:38 alarm systemd-journald[45]: Time spent on flushing to /var/log/journal/0f965e568f3d4fa69e6bd24a8620883a is 5.392ms for 4 entries.
Feb 02 20:16:38 alarm systemd-journald[45]: System Journal (/var/log/journal/0f965e568f3d4fa69e6bd24a8620883a) is 80.0M, max 1.2G, 1.1G free.
Feb 02 20:16:38 alarm systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 02 20:16:38 alarm systemd[1]: Starting Create Volatile Files and Directories...
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed to set up credentials: Invalid argument
Feb 02 20:16:38 alarm systemd[61]: systemd-tmpfiles-setup.service: Failed at step CREDENTIALS spawning systemd-tmpfiles: Invalid argument
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=243/CREDENTIALS
Feb 02 20:16:38 alarm systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
Feb 02 20:16:38 alarm systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 02 20:16:38 alarm systemd[1]: Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var).
Feb 02 20:16:38 alarm systemd[1]: Starting Network Name Resolution...
Feb 02 20:16:38 alarm systemd[1]: Network Time Synchronization was skipped because of an unmet condition check (ConditionVirtualization=!container).
Feb 02 20:16:38 alarm systemd[1]: Reached target System Time Set.
Feb 02 20:16:38 alarm systemd[1]: Update is Completed was skipped because no trigger condition checks were met.
Feb 02 20:16:38 alarm systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Feb 02 20:16:38 alarm systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Feb 02 20:16:39 alarm systemd-resolved[63]: Positive Trust Anchors:
Feb 02 20:16:39 alarm systemd-resolved[63]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Feb 02 20:16:39 alarm systemd-resolved[63]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.a>
Feb 02 20:16:39 alarm systemd-resolved[63]: Using system hostname 'alarm'.
Feb 02 20:16:39 alarm systemd[1]: Started Network Name Resolution.
Feb 02 20:16:39 alarm systemd[1]: Reached target Network.
Feb 02 20:16:39 alarm systemd[1]: Reached target Host and Network Name Lookups.
Feb 02 20:16:39 alarm systemd[1]: Reached target System Initialization.
Feb 02 20:16:39 alarm systemd[1]: Started Refresh existing PGP keys of archlinux-keyring regularly.
Feb 02 20:16:39 alarm systemd[1]: Started Daily verification of password and group files.
Feb 02 20:16:39 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Feb 02 20:16:39 alarm systemd[1]: Reached target Timer Units.
Feb 02 20:16:39 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 02 20:16:39 alarm systemd[1]: Reached target Socket Units.
Feb 02 20:16:39 alarm systemd[1]: Reached target Basic System.
Feb 02 20:16:39 alarm systemd[1]: Starting D-Bus System Message Bus...
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: Starting User Login Management...
Feb 02 20:16:39 alarm systemd[1]: Starting Permit User Sessions...
Feb 02 20:16:39 alarm systemd[1]: Finished Permit User Sessions.
Feb 02 20:16:39 alarm systemd[1]: Started Console Getty.
Feb 02 20:16:39 alarm systemd[1]: Getty on tty1 was skipped because of an unmet condition check (ConditionPathExists=/dev/tty0).
Feb 02 20:16:39 alarm systemd[1]: Reached target Login Prompts.
Feb 02 20:16:39 alarm systemd[1]: Started D-Bus System Message Bus.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[71]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm sshd[71]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd-logind[73]: New seat seat0.
Feb 02 20:16:39 alarm systemd[1]: Started User Login Management.
Feb 02 20:16:39 alarm systemd[1]: Reached target Multi-User System.
Feb 02 20:16:39 alarm systemd[1]: Reached target Graphical Interface.
Feb 02 20:16:39 alarm systemd[1]: Startup finished in 1.380s.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 1.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:39 alarm sshd[84]: fatal: Cannot bind any address.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:39 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 2.
Feb 02 20:16:39 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:39 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:39 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:40 alarm sshd[87]: fatal: Cannot bind any address.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 3.
Feb 02 20:16:40 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:40 alarm sshd[90]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:40 alarm sshd[90]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:40 alarm sshd[90]: fatal: Cannot bind any address.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 4.
Feb 02 20:16:40 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:40 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:40 alarm systemd[1]: Started OpenSSH Daemon.
Feb 02 20:16:40 alarm sshd[93]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 02 20:16:40 alarm sshd[93]: error: Bind to port 22 on :: failed: Address already in use.
Feb 02 20:16:40 alarm sshd[93]: fatal: Cannot bind any address.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Main process exited, code=exited, status=255/EXCEPTION
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Scheduled restart job, restart counter is at 5.
Feb 02 20:16:40 alarm systemd[1]: Stopped OpenSSH Daemon.
Feb 02 20:16:40 alarm systemd[1]: SSH Key Generation was skipped because no trigger condition checks were met.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Start request repeated too quickly.
Feb 02 20:16:40 alarm systemd[1]: sshd.service: Failed with result 'exit-code'.
Feb 02 20:16:40 alarm systemd[1]: Failed to start OpenSSH Daemon.
Feb 02 20:16:46 alarm login[80]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Feb 02 20:16:46 alarm login[80]: pam_systemd(login:session): Failed to create session: Input/output error
Feb 02 20:17:11 alarm login[80]: ROOT LOGIN ON pts/0
Feb 02 20:17:11 alarm login[80]: pam_unix(login:session): session closed for user root
Feb 02 20:17:12 alarm systemd[1]: console-getty.service: Deactivated successfully.
Feb 02 20:17:12 alarm systemd[1]: console-getty.service: Scheduled restart job, restart counter is at 1.
Feb 02 20:17:12 alarm systemd[1]: Stopped Console Getty.
Feb 02 20:17:12 alarm systemd[1]: Started Console Getty.

离线

#7 2023-02-02 21:07:06

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 8,384
个人网站

Re: systemd-nspawn无法验证密码

离线

#8 2023-02-03 09:24:11

luxni
会员
注册时间: 2014-06-08
帖子: 280

Re: systemd-nspawn无法验证密码

我用硬件测试了下 ArchlinuxARM,可以登录呀。

    Login as the default user alarm with the password alarm.
    The default root password is root.

虽然人菜菜的,但也想做个有趣的人。

离线

#9 2023-02-03 11:23:26

akumaexs
会员
注册时间: 2023-01-12
帖子: 19

Re: systemd-nspawn无法验证密码

luxni 说:

我用硬件测试了下 ArchlinuxARM,可以登录呀。

    Login as the default user alarm with the password alarm.
    The default root password is root.

回头等我成功把系统烧进板子以后再试试吧
目前还在慢慢学习:)

离线

页脚