Shadowsocks-libev: ubuntu 16.04 shadowsocks-libev.service: Failed at step CAPABILITIES spawning /usr/bin/ss-server: Invalid argument
ubuntu 16.04
Current version: 3.24
shadowsocks-libev.service: Failed at step CAPABILITIES spawning /usr/bin/ss-server: Invalid argument
ptsa
All 8 comments
你的内核版本是？
ideal
on 3 Mar 2019
Ubuntu 16.04.6 LTS (GNU/Linux 2.6.32-042stab112.15 x86_64)
ptsa
on 3 Mar 2019
你的内核太老了。你把/usr/lib/systemd/system/[email protected]里：
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
这一行注释掉试试。
ideal
on 4 Mar 2019
Happens to me too.
CoolOppo
on 7 Mar 2019
Note: In my case, The file at /lib/systemd/system/shadowsocks-libev.service
chenshaoju
on 5 Jun 2019
你的内核太老了。你把
/usr/lib/systemd/system/[email protected]里：
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
这一行注释掉试试。
Would you mind translating this? I'd like to follow your advice :)
edit: For everyone wondering, here is my detailed solution:
If you use the service command do this:
nano /lib/systemd/system/shadowsocks-libev.service
add # in front of the two lines regarding capabilities (to comment them) as such:
#CapabilityBoundingSet=CAP_NET_BIND_SERVICE
#AmbientCapabilities=CAP_NET_BIND_SERVICE
Reload the config files and start service again:
systemctl daemon-reload
service shadowsocks-libev start
Also: ensure your server binary referenced in the file has the CAP_NET_BIND_SERVICE cap set, by issuing:
getcap /usr/bin/ss-server
result should be:
/usr/bin/ss-server = cap_net_bind_service+ep
if not, set it:
setcap cap_net_bind_service+ep /usr/bin/ss-server
Hope this helps!
reijin90
on 9 Jun 2019
@reijin90 So it works now?
ideal
on 10 Jun 2019
Yes ;)
On Mon, 10 Jun 2019, 03:47 Shang Yuanchun, notifications@github.com wrote:
@reijin90 https://github.com/reijin90 So it works now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shadowsocks/shadowsocks-libev/issues/2303?email_source=notifications&email_token=ABUQSPW4QAD2GPBQIHUKN4DPZWXDRA5CNFSM4G3I3SZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXIXFWQ#issuecomment-500265690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUQSPWIMUMRHUYGM5X3ZR3PZWXDRANCNFSM4G3I3SZQ
.
reijin90
on 10 Jun 2019
Related issues
d0u9
·
4Comments
DragonCat1
·
3Comments
zhfreal
·
4Comments
tony1016
·
3Comments
iceberg1369
·
3Comments
Most helpful comment
Would you mind translating this? I'd like to follow your advice :)edit: For everyone wondering, here is my detailed solution:
If you use the
servicecommand do this:nano /lib/systemd/system/shadowsocks-libev.serviceadd # in front of the two lines regarding capabilities (to comment them) as such:
Reload the config files and start service again:
Also: ensure your server binary referenced in the file has the
CAP_NET_BIND_SERVICEcap set, by issuing:getcap /usr/bin/ss-serverresult should be:
/usr/bin/ss-server = cap_net_bind_service+epif not, set it:
setcap cap_net_bind_service+ep /usr/bin/ss-serverHope this helps!