[SERVER-26438] systemd rejects service file in debian/ubuntu packages Created: 03/Oct/16 Updated: 05/Dec/22 Resolved: 16/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | 4.1 Desired |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Build 2016-10-10 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
It looks like some versions of systemd (debian8 or ubuntu1604) don't support some of the config options that we added for This isn't true of all versions of systemd, but we need to confirm this on all versions that we support. |
| Comments |
| Comment by Iryna Zhuravlova [ 16/Nov/22 ] | ||||||||||||||||||||
|
After a careful backlog refinement, the team decided to close this ticket because of its low priority and limited resource capacity. If you believe that this ticket requires additional attention from the team and should be re-opened, feel free to change the status to "Needs Scheduling" and ping me or @alexander.neben | ||||||||||||||||||||
| Comment by Ernie Hershey [ 18/Oct/16 ] | ||||||||||||||||||||
|
I can reproduce partially in Vagrant with Debian 8.1.0. The service does stop/start for me despite the alarming log message. The worst likely consequence of this is that task limits may not be set properly for mongod.
| ||||||||||||||||||||
| Comment by Emil Burzo [ 05/Oct/16 ] | ||||||||||||||||||||
|
This is definitely an issue on Ubuntu 16.04, I got hit by it as soon as I upgraded to MongoDB 3.2.10. Here's a video reproduction using Vagrant with a fresh ubuntu xenial base box: | ||||||||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 04/Oct/16 ] | ||||||||||||||||||||
|
I tried to reproduce this issue on Debian 8.1 system built from the default Debian AMI on amazon, and was not able to reproduce this issue. It's possible that an upgrade from a wheezy package or from another version could have lead to some sort of corrupted service file, or another confusing state that wasn't included in the initial report but that might explain some of the observed behavior. It looks like report came from a user on the debian jessie vagrant box of version 8.2.0, which was released on October 22, 2015. I haven't reviewed the changes to the vagrant box since then, nor am I certain which vagrant backend was in use, which could definitely explain some of the observed behavior. I'm going to go ahead and close this ticket, but if we get more information about this issue we can definitely reopen the issue. | ||||||||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 03/Oct/16 ] | ||||||||||||||||||||
|
This issue was reported in this comment thread. User reports this problem on debian8-jessie. |