lxc-start failed to open /dev/null

Bug #1625447 reported by You-Sheng Yang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Invalid
Undecided
Unassigned

Bug Description

lxc-start[1149]: lxc-start: utils.c: open_devnull: 1760 No such file or directory - Can't open /dev/null
lxc-start[1149]: lxc-start: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5)
lxc-start[1149]: lxc-start: start.c: __lxc_start: 1354 failed to spawn 'android'
lxc-start[1149]: lxc-start: cgroups/cgfsng.c: recursive_destroy: 983 Error destroying /sys/fs/cgroup/systemd//lxc/android
lxc-start[1149]: lxc-start: cgroups/cgfsng.c: recursive_destroy: 983 Error destroying /sys/fs/cgroup/freezer//lxc/android
lxc-start[1149]: lxc-start: cgroups/cgfsng.c: recursive_destroy: 983 Error destroying /sys/fs/cgroup/cpu//lxc/android
lxc-start[1149]: lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start[1149]: lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
systemd[1]: lxc-android-config.service: Main process exited, code=exited, status=255/n/a

Tags: systemd
Jason Yen (jasonyen)
Changed in canonical-devices-system-image:
milestone: none → x1
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Enabling --logpriority DEBUG gives more hints:

WARN lxc_start - start.c:do_start:829 - using host's /dev/null for container init's std fds, migraiton won't work

tags: added: systemd
Revision history for this message
You-Sheng Yang (vicamo) wrote :
Revision history for this message
You-Sheng Yang (vicamo) wrote :

This is never a critical bug. lxc-start has started android init, but somehow it dies when trying to set property persist.service.acm.enable=0. Will close this bug and file another.

Changed in canonical-devices-system-image:
status: New → Invalid
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Filed as bug 1625549.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.