#34550 – systemd 233 & openvz on 2.6.32: Failed to set invocation ID on control group

Bug 34550 - systemd 233 & openvz on 2.6.32: Failed to set invocation ID on control group

Summary: systemd 233 & openvz on 2.6.32: Failed to set invocation ID on control group

Status:	CLOSED WONTFIX

Alias:	None

Product:	Sisyphus
Classification:	Development
Component:	systemd (show other bugs)
Version:	unstable
Hardware:	all Linux

Importance:	P3 normal
Assignee:	Alexey Shabalin
QA Contact:	qa-sisyphus

URL:	https://bugs.launchpad.net/ubuntu/+so...
Keywords:

Depends on:
Blocks:

Reported:	2018-02-16 14:22 MSK by Vitaly Lipatov
Modified:	2024-07-09 20:48 MSK (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description

Vitaly Lipatov 2018-02-16 14:22:53 MSK

После обновления до systemd 233 в контейнере OpenVZ на ядре 2.6.32
не стартует crond с сообщением:
crond.service: Failed to set invocation ID on control group /system.slice/crond.service, ignoring: Operation not permitted

Похожая проблема описана здесь, но непонятно, как решена:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096

Comment 1

Vitaly Lipatov 2018-02-16 14:27:50 MSK

Также с другими сервисами возникает ошибка "Failed at step KEYRING spawning"

Лечится добавлением в контейнер CAPABILITY="CAP_SYS_ADMIN:on"
https://github.com/systemd/systemd/issues/6281

Comment 2

Alexey Shabalin 2024-07-09 20:48:49 MSK

думаю никто ничего не будет чинить для ядер 2.6.32.