nullmailer service doesn't start if already running in a child container under LXC
Bug #1496100 reported by
Mark Thornton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nullmailer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
If you are running containers with LXC and one or more has nullmailer running, then you can't start a nullmailer service on the host. This happens because the service script looks for an existing process by name. The child nullmailer process(es) is visible on the host under the same name.
You could argue that the fault lies with inadequate isolation by LXC. Also the problem may disappear when (if) the service is updated to use systemd instead of a legacy rc script.
As a work around make sure that the host nullmailer service is started before that in any child container. (Child containers do not see host processes or those of other containers.)
Problem detected on Ubuntu 14.04.2 LTS
| affects: | compiz (Ubuntu) → nullmailer (Ubuntu) |
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in nullmailer (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.