ALT Linux Bugzilla
– Attachment 19020 Details for
Bug 55130
Не запускается пользовательская systemd служба
New bug
|
Search
|
[?]
|
Help
Register
|
Log In
[x]
|
Forgot Password
Login:
[x]
|
EN
|
RU
Лог службы user@1000.service
kiosk.log (text/x-log), 4.69 KB, created by
Alexey Volkov
on 2025-07-09 21:43:41 MSK
(
hide
)
Description:
Лог службы user@1000.service
Filename:
MIME Type:
Creator:
Alexey Volkov
Created:
2025-07-09 21:43:41 MSK
Size:
4.69 KB
patch
obsolete
>Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Trying to enqueue job user@1000.service/start/replace >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Installed new job user@1000.service/start as 2633 >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Enqueued job user@1000.service/start as 2633 >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: starting held back, waiting for: user-runtime-dir@1000.service >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Merged user@1000.service/start into installed job user@1000.service/start as 2633 >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: starting held back, waiting for: user-runtime-dir@1000.service >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Will spawn child (service_enter_start): /usr/lib/systemd/systemd >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Passing 0 fds to service >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: About to execute: /usr/lib/systemd/systemd --user >Jul 09 21:21:46 host-34 systemd[1]: Serializing sd-executor-state to memfd. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Forked /usr/lib/systemd/systemd as 2601 >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Changed dead -> start >Jul 09 21:21:46 host-34 systemd[1]: Starting user@1000.service - User Manager for UID 1000... >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: User lookup succeeded: uid=1000 gid=1000 >Jul 09 21:21:46 host-34 (systemd)[2601]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy >Jul 09 21:21:46 host-34 (systemd)[2601]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy >Jul 09 21:21:46 host-34 (systemd)[2601]: pam_tcb(systemd-user:session): Session opened for test by (uid=0) >Jul 09 21:21:46 host-34 (systemd)[2601]: pam_setcred() failed, ignoring: Failure setting user credentials >Jul 09 21:21:46 host-34 (systemd)[2601]: Successfully forked off '(sd-pam)' as PID 2606. >Jul 09 21:21:46 host-34 systemd[2601]: Failed to read $container of PID 1, ignoring: Permission denied >Jul 09 21:21:46 host-34 systemd[2601]: Found container virtualization none. >Jul 09 21:21:46 host-34 systemd[2601]: systemd 255.21-alt1 running in user mode for user 1000/test. (+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) >Jul 09 21:21:46 host-34 systemd[2601]: Failed to create '/run/user/1000/systemd/inaccessible/blk', ignoring: Operation not permitted >Jul 09 21:21:46 host-34 systemd[2601]: Failed at setting rlimit 513454080 for resource RLIMIT_MEMLOCK. Will attempt setting value 2097152 instead. >Jul 09 21:21:46 host-34 systemd[2601]: Failed to lookup RuntimeDirectory path: No such device or address >Jul 09 21:21:46 host-34 systemd[2601]: Failed to allocate manager object: No such device or address >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Got notification message from PID 2601 (ERRNO=6) >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Got notification message from PID 2601 (EXIT_STATUS=1) >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Child 2601 belongs to user@1000.service. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Changed start -> stop-sigkill >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Child 2606 belongs to user@1000.service. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Control group is empty. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Failed with result 'exit-code'. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Service will not restart (restart setting) >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Changed stop-sigkill -> failed >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Job 2633 user@1000.service/start finished, result=failed >Jul 09 21:21:46 host-34 systemd[1]: Failed to start user@1000.service - User Manager for UID 1000. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Unit entered failed state. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Consumed 32ms CPU time. >Jul 09 21:21:46 host-34 systemd[1]: user@1000.service: Releasing resources... >Jul 09 21:21:57 host-34 systemd[1]: user@1000.service: Trying to enqueue job user@1000.service/stop/fail >Jul 09 21:21:57 host-34 systemd[1]: user@1000.service: Installed new job user@1000.service/stop as 3197 >Jul 09 21:21:57 host-34 systemd[1]: user@1000.service: Enqueued job user@1000.service/stop as 3197 >Jul 09 21:21:57 host-34 systemd[1]: user@1000.service: Job 3197 user@1000.service/stop finished, result=done
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 55130
: 19020