FS#70295 - [tor] service reload returns permission issue

Attached to Project: Arch Linux
Opened by Armand (Kewl) - Monday, 05 April 2021, 10:37 GMT
Last edited by kpcyrd (kpcyrd) - Tuesday, 29 August 2023, 16:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Levente Polyak (anthraxx)
kpcyrd (kpcyrd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

* Description:
Reloading the service (as root) in order to reload the configuration fails.
Tor version 0.4.5.7.
systemd 248 (248-2-arch)

* Steps to reproduce:
# systemctl reload tor.service
Job for tor.service failed.

The log shows:
kill: sending signal to 12345 failed: Operation not permitted
tor.service: Control process exited, code=exited, status=1/FAILURE
Reload failed for Anonymizing overlay network for TCP.
This task depends upon

Closed by  kpcyrd (kpcyrd)
Tuesday, 29 August 2023, 16:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.4.8.4-2
Comment by helle vaanzinn (glitsj16) - Monday, 05 April 2021, 14:43 GMT
Confirming. IMO this is caused by CapabilityBoundingSet in /usr/lib/systemd/system/tor.service. Adding CAP_KILL there fixes this issue for me.
Comment by Armand (Kewl) - Tuesday, 11 May 2021, 17:40 GMT
Still present in 0.4.5.8, I confirm that adding CAP_KILL fixes the issue.
Comment by Armand (Kewl) - Saturday, 19 June 2021, 05:32 GMT
Still present in 0.4.6.5
Comment by Vedran Miletic (rivanvx) - Tuesday, 08 February 2022, 11:09 GMT
Still present in 0.4.6.9, fixed by adding CAP_KILL
Comment by Tripple Moon (TriMoon) - Sunday, 13 November 2022, 09:34 GMT
Works without issues when https://bugs.archlinux.org/task/76546 is applied...
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.
Comment by Toolybird (Toolybird) - Sunday, 27 August 2023, 22:16 GMT
It's still an issue. Dupe  FS#79490 
Comment by Armand (Kewl) - Monday, 28 August 2023, 06:38 GMT
The issue is still present, do not close the ticker.

Loading...