[tor-bugs] #17713 [Tor]: Debian 8.2 latest tor package tor_0.2.7.5-1~d80.jessie+1_amd64.deb fails on start with "NO_NEW_PRIVILEGES"

[Tor Bug Tracker & Wiki]

#17713: Debian 8.2 latest tor package tor_0.2.7.5-1~d80.jessie+1_amd64.deb fails on
start with "NO_NEW_PRIVILEGES"
------------------------+----------------------------------
     Reporter:  DeS     |      Owner:
         Type:  defect  |     Status:  new
     Priority:  Medium  |  Milestone:
    Component:  Tor     |    Version:  Tor: 0.2.7.5
     Severity:  Normal  |   Keywords:  NO_NEW_PRIVILEGES VM
Actual Points:          |  Parent ID:
       Points:          |    Sponsor:
------------------------+----------------------------------
 Hello,
 I operate a tor middle node since several years on a VM in a datacenter.
 The VM is running Debian Jessie 8.2.
 Up to now I never had a problem.
 After Upgrade to the lates 0.2.7.5.-1 package the tor service does not
 start anymore.
 See below the syslog information. There is no info in the tor server log

 {{{
 Nov 27 10:22:19 vmd tor[11811]: Nov 27 10:22:19.381 [notice] Read
 configuration file "/etc/tor/torrc".
 Nov 27 10:22:19 vmd tor[11811]: Nov 27 10:22:19.383 [notice] Based on
 detected system memory, MaxMemInQueues is set to 2976 MB. You can override
 this by setting MaxMemInQueues by hand.
 Nov 27 10:22:19 vmd tor[11811]: Configuration was valid
 Nov 27 10:22:19 vmd systemd[11814]: Failed at step NO_NEW_PRIVILEGES
 spawning /usr/bin/tor: Invalid argument
 Nov 27 10:22:19 vmd systemd[1]: tor at default.service: main process exited,
 code=exited, status=227/NO_NEW_PRIVILEGES
 Nov 27 10:22:19 vmd systemd[1]: Failed to start Anonymizing overlay
 network for TCP.
 Nov 27 10:22:19 vmd systemd[1]: Unit tor at default.service entered failed
 state.
 Nov 27 10:22:19 vmd systemd[1]: tor at default.service start request repeated
 too quickly, refusing to start.
 Nov 27 10:22:19 vmd systemd[1]: Failed to start Anonymizing overlay
 network for TCP.
 Nov 27 10:22:19 vmd systemd[1]: Unit tor at default.service entered failed
 state.
 }}}

 Reinstalling the old version  0.2.5.12-1 fixed the Problem.
 On another metal maschine I do not experience this problem running several
 exits.

 Might have something to do with the KVM based virtualization. But this is
 just an guess.
 Let me know if you need more information

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17713>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online