LINUX.ORG.RU

lxc Operation not permitted

 , ,


0

4

есть debian 9

на нем поднят Proxmox и через него созданы lxc контейнеры
lxc - 3.1.0-devel
сейчас на одном контейнере посыпались ошибки

Jun  7 12:32:12 server systemd[1]: systemd-journal-flush.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting Flush Journal to Persistent Storage...
Jun  7 12:32:12 server keyboard-setup.sh[47]: Couldn't get a file descriptor referring to the console
Jun  7 12:32:12 server systemd[1]: Started Nameserver information manager.
Jun  7 12:32:12 server keyboard-setup.sh[47]: Couldn't get a file descriptor referring to the console
Jun  7 12:32:12 server systemd[1]: Started Set the console keyboard layout.
Jun  7 12:32:12 server resolvconf[54]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
Jun  7 12:32:12 server keyboard-setup.sh[47]: Couldn't get a file descriptor referring to the console
Jun  7 12:32:12 server systemd[1]: Reached target Local File Systems (Pre).
Jun  7 12:32:12 server keyboard-setup.sh[47]: setupcon: We are not on the console, the console is left unconfigured.
Jun  7 12:32:12 server systemd[1]: Reached target Local File Systems.
Jun  7 12:32:12 server systemd[1]: plymouth-read-write.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jun  7 12:32:12 server netfilter-persistent[89]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start
Jun  7 12:32:12 server systemd[1]: console-setup.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting Set console font and keymap...
Jun  7 12:32:12 server systemd[1]: netfilter-persistent.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting netfilter persistent configuration...
Jun  7 12:32:12 server systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jun  7 12:32:12 server systemd[1]: Reached target Local Encrypted Volumes.
Jun  7 12:32:12 server systemd[1]: Started Set console font and keymap.
Jun  7 12:32:12 server systemd[1]: Started Flush Journal to Persistent Storage.
Jun  7 12:32:12 server systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Jun  7 12:32:12 server systemd[1]: systemd-tmpfiles-setup.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting Create Volatile Files and Directories...
Jun  7 12:32:12 server systemd[1]: Started Create Volatile Files and Directories.
Jun  7 12:32:12 server systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Failed to attach 97 to compat systemd cgroup /system.slice/systemd-resolved.service: No such file or directory
Jun  7 12:32:12 server systemd[1]: Starting Network Name Resolution...
Jun  7 12:32:12 server systemd[1]: systemd-update-utmp.service: Failed to reset devices.list: Operation not permitted
Jun  7 12:32:12 server systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Jun  7 12:32:12 server systemd[1]: Reached target System Time Synchronized.
Jun  7 12:32:12 server systemd[97]: Failed to attach 97 to compat systemd cgroup /system.slice/systemd-resolved.service: No such file or director

ни один сервис не стартует, как такое вылечить?


Ответ на: комментарий от das_tier

все стартовало, тот же заббикс работал, а сейчас

service zabbix-agent status
● zabbix-agent.service - LSB: Start zabbix-agent daemon
   Loaded: loaded (/etc/init.d/zabbix-agent; generated)
   Active: active (exited) since Fri 2019-06-07 18:47:56 MSK; 20min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 211 ExecStart=/etc/init.d/zabbix-agent start (code=exited, status=0/SUCCESS)

Jun 07 18:47:56 server systemd[1]: Starting LSB: Start zabbix-agent daemon...
Jun 07 18:47:56 server systemd[1]: Started LSB: Start zabbix-agent daemon.

при рестарте

-- The start-up result is RESULT.
Jun 07 19:12:29 server systemd[1]: zabbix-agent.service: Failed to reset devices.list: Operation not permitted
Jun 07 19:12:29 server systemd[1]: Stopping LSB: Start zabbix-agent daemon...
-- Subject: Unit zabbix-agent.service has begun shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit zabbix-agent.service has begun shutting down.
Jun 07 19:12:29 server systemd[1]: Stopped LSB: Start zabbix-agent daemon.
-- Subject: Unit zabbix-agent.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit zabbix-agent.service has finished shutting down.
Jun 07 19:12:29 server systemd[1]: zabbix-agent.service: Failed to reset devices.list: Operation not permitted
Jun 07 19:12:29 server systemd[1]: Starting LSB: Start zabbix-agent daemon...
-- Subject: Unit zabbix-agent.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit zabbix-agent.service has begun starting up.
Jun 07 19:12:29 server systemd[1]: Started LSB: Start zabbix-agent daemon.
-- Subject: Unit zabbix-agent.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit zabbix-agent.service has finished starting up.
Garcia ()
Ответ на: комментарий от anonymous

ребут, пробовал, не помогло

похоже проблема была в squid, он не стартовал из-за ошибки в конфиге и не стартовали другие процессы, хотя это странно, но поправив конфиг, остальные процессы начали запускаться нормально

Operation not permitted

похоже и вправду просто информативное сообщение

Garcia ()