OpenVZ Forum


Home » General » Support » Tracing systemd boot errors (Sometimes systemd fails to start)
Tracing systemd boot errors [message #52294] Wed, 13 January 2016 13:59
miihael is currently offline  miihael
Messages: 1
Registered: January 2016
Location: Moscow
Junior Member
From: *broadband.corbina.ru
Is there way to trace, what systemd is doing when container is started?

I have some containers, upgraded from sysV-init to systemd (Debian Wheezy to Jessie), the whole container fails to start.
When I enter the container, I can see only these processes:

# pstree -a
systemd -z
|-(kthreadd/391)
| `-(khelper/391)
`-vzctl
`-bash
`-pstree -a


I tried to attach strace from inside, but could not.

# strace -p 1
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted


Is there way to attach strace from outside? Or enable systemd debug options somehow?

Kernel version is:
Linux 2.6.32-042stab113.11 #1 SMP Fri Dec 18 17:32:04 MSK 2015 x86_64 x86_64 x86_64 GNU/Linux

Host OS version is: CentOS release 6.7 (Final)

Container OS is Debian Jessie.
Previous Topic: MAC address
Next Topic: Does these kernel options seems right to you?
Goto Forum:
  


Current Time: Wed Feb 26 13:59:26 GMT 2020