FS#56802 - [shadowsocks-libev] Unable to start shadowsocks-libev-server@s1 after systemd upgraded to 236
Attached to Project:
Community Packages
Opened by Eric Wang (enihcam) - Thursday, 21 December 2017, 10:56 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 05 April 2023, 05:27 GMT
Opened by Eric Wang (enihcam) - Thursday, 21 December 2017, 10:56 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 05 April 2023, 05:27 GMT
|
Details
Description:
Unable to start server after systemd upgraded to 236. Error message is "ss-server[586]: 2017-12-21 18:54:07 ERROR: Invalid config path." But the path is correct (with nobody/root in permission) Additional info: * package version(s) shadowsocks-libev-3.1.1-1 * config and/or log files etc. ● shadowsocks-libev-server@s1.service - Shadowsocks-Libev Server Service Loaded: loaded (/usr/lib/systemd/system/shadowsocks-libev-server@.service; indirect; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2017-12-21 18:54:07 CST; 17s ago Process: 586 ExecStart=/usr/bin/ss-server -c /etc/shadowsocks/s1.json (code=exited, status=255) Main PID: 586 (code=exited, status=255) Steps to reproduce: Upgrade to systemd 236 and restart |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 05 April 2023, 05:27 GMT
Reason for closing: None
Additional comments about closing: Closing this old and stale ticket in favor of FS#71925
Wednesday, 05 April 2023, 05:27 GMT
Reason for closing: None
Additional comments about closing: Closing this old and stale ticket in favor of
sudo -u nobody /usr/bin/ss-server -c /etc/shadowsocks/s1.json
Here is my folder:
/etc/shadowsocks $ ls -la
total 8.0K
drwxr-xr-x 1 root root 28 Apr 24 2017 ./
drwxr-xr-x 1 root root 1.7K Dec 21 18:47 ../
-rw-r----- 1 nobody root 411 Nov 21 13:20 s1.json
-rw-r----- 1 nobody root 411 Nov 21 13:20 s2.json
I also filed this bug to systemd, and someone suggests using DynamicUser=.
https://github.com/systemd/systemd/issues/7717
● shadowsocks@us9.service - Shadowsocks Client Service
Loaded: loaded (/usr/lib/systemd/system/shadowsocks@.service; indirect; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2017-12-23 09:55:13 CST; 12h ago
Process: 531 ExecStart=/usr/bin/sslocal -c /etc/shadowsocks/us9.json (code=exited, status=1/FAILURE)
Main PID: 531 (code=exited, status=1/FAILURE)
Dec 23 09:55:13 thinkless sslocal[531]: _CONFIG_VARS['userbase'] = _getuserbase()
Dec 23 09:55:13 thinkless sslocal[531]: File "/usr/lib/python3.6/sysconfig.py", line 205, in _getuserbase
Dec 23 09:55:13 thinkless sslocal[531]: return joinuser("~", ".local")
Dec 23 09:55:13 thinkless sslocal[531]: File "/usr/lib/python3.6/sysconfig.py", line 184, in joinuser
Dec 23 09:55:13 thinkless sslocal[531]: return os.path.expanduser(os.path.join(*args))
Dec 23 09:55:13 thinkless sslocal[531]: File "/usr/lib/python3.6/posixpath.py", line 247, in expanduser
Dec 23 09:55:13 thinkless sslocal[531]: userhome = pwd.getpwuid(os.getuid()).pw_dir
Dec 23 09:55:13 thinkless sslocal[531]: KeyError: 'getpwuid(): uid not found: 65534'
Dec 23 09:55:13 thinkless systemd[1]: shadowsocks@us9.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 09:55:13 thinkless systemd[1]: shadowsocks@us9.service: Failed with result 'exit-code'.
This bug can be closed because nothing to do here.