On July 16, 2015 2:57:27 PM EDT, Jason Rhinelander <jager...@jagerman.com> wrote: >On Wed, 15 Jul 2015 01:01:41 -0400 Scott Kitterman ><deb...@kitterman.com> wrote: >> On Wednesday, July 15, 2015 12:24:18 AM Cyrille Mescam wrote: >> > Package: opendkim >> ... >> > Trying to start the service: service opendkim start >> ... >> > Init: systemd (via /run/systemd/system) >> ... >> >> You started opendkim with the sysv init interface (which used the old >sysv >> init script) even though you are running systemd as your init system >and a >> systemd service file is provided. What happens if you do: >> >> systemctl start opendkim >> >> You may have to clear the failed state first. I think this will do >that: >> >> systemctl reset-failed opendkim >> > >I get exactly the same problem, and the above did not fix it. I found >the problem, however: systemd environment files do *not* support >in-line >comments such as: > >SOCKET="local:/var/run/opendkim/opendkim.sock" # default > >in the original report, or in my case: > >SOCKET="inet:12345@localhost" # listen on loopback on port 12345 > >which is how the examples in /etc/default/opendkim used to be (prefixed > >with another # at the beginning of the line). It really isn't obvious >that this change was significant across the upgrade (it looked more >like >just cosmetic reformatting), and so I just selected to keep my >currently-installed version. > >That broke because systemd doesn't see an inline # as starting a >comment, and so ends up trying to start opendkim by running (in the >original reporter's case): > >/usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P >/var/run/opendkim/opendkim.pid -p local:/var/run/opendkim/opendkim.sock > >"#" default > >which is obviously wrong, and hence opendkim fails to start. > >So Cyrille can fix this by removing " # default" from the end of the >line in /etc/default/opendkim, and I've fixed my own similarly. > >But since these inline comments were the default /etc/default/opendkim >examples in the previous version, this seems like something that is >going to come up for a lot of people when upgrading opendkim on a >systemd-running system, since basically the old /etc/default/opendkim >configuration file won't work with the new package. Is there something > >else that can be done to catch and/or fix this on upgrade?
Thanks for the additional troubleshooting and information. I did make the change specifically because the old format didn't work with the service file. The best thing I've thought is so far is adding a Debian.News entry to warn people on upgrade, but that's certainly not ideal. I'm open to suggestions. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
