Shadowsocks-libev: The right way to start/stop shadowsocks-libev

[sethcreate]

What version of shadowsocks-libev are you using?

3.1.0

What operating system are you using?

SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

What did you do?

I found two method to start ss:
way1:

sudo /etc/init.d/shadowsocks-libev start    # for sysvinit, or

this way doesn't work for me, but it replied [ok]

way2:

sudo ss-server -c /etc/shadowsocks-libev/config.json -f .ss.pid

This way worked for me , but I can't find the way to stop it(expect kill the_process, there isn't a way something like ss-server stop.

What did you expect to see?

I just want to know which way is the better one?
If the first one is the better one, but why it doesn't work for me? any configeration I missed?
If the 2nd is the choice, Is there a good way to stop the ss-server, I found that if I run sudo ss-server -c /etc/shadowsocks-libev/config.json -f .ss.pid repeatedly , then a lot of process will be created.
That's not what I want, obviously.

What did you see instead?

way1 doen't work for me.
for way2 can't found a good way to stop the ss-server process.

What is your config in detail (with all sensitive info masked)?

End

Thanks so much for what your team did!

[sethcreate]

I Had read https://github.com/shadowsocks/shadowsocks-libev/issues/1580 , but didn't worked for me.

[eastmalon]

1. sudo /etc/init.d/shadowsocks-libev stop
2. sudo kill -9 $(cat .ss.pid)

[sethcreate]

I think it would be great If there was a command like ss-server start/stop/status/restart/log .

[hosiet]

ss-libev already provides systemd service and sysvinit service for users to use when installed from distribution package. I think implementing another start/stop layer is unnecessary.

If you find any difficulties when using ss-libev as system service, feel free to submit issues here and describe your problem.

[sethcreate]

sudo /etc/init.d/shadowsocks-libev start doesn't work for me. I don't know why? Any else information need to be provided ?

[hosiet]

If you are on Debian 9: stop using things inside /etc/init.d/. This file only exists for compatibility purposes with old init system.

Please use systemctl command to manage ss-libev's service as described in "Configure and start the service" part in README.md. You will need basic knowledges about systemd.

[sethcreate]

@hosiet Thx for your patient explain, I'll try later, and let you know the result!

[sethcreate]

@hosiet I executed sudo systemctl start shadowsocks-libev , but ss didn't started successfully!
Any advice?

[lxx4380]

try

sudo systemctl start shadowsocks-libev@config

[sethcreate]

@lxx4380 Failed to start [email protected]: Unit [email protected] not found.

[hosiet]

@lxx4380 Your words are misleading because that service never exists.

If you look into files provided by ss-libev packages in /lib/systemd/system/, there are several service files related to ss-libev:

• shadowsocks-libev.service
• [email protected]
• [email protected]
• [email protected]
• [email protected]

The first one is the example default service which reads /etc/shadowsocks-libev/config.json and all other services are template services that accepts a config file name as argument to distinguish between each other instances. I don't know if there are any other words that can better explain things, but anyone who knows a little about systemd should be able to utilize them.

Note that none of them are written to work seamlessly with simple-obfs. You may have to modify them using commands like systemctl edit to fit your need.

[sethcreate]

@madeye @hosiet I still want to recommand that ss-libev should has the commands ss-server start/stop/status/restart/log just like shadowsocks-python . Since the commands are easy to understand and use.

[hosiet]

Personally I'm not for this idea. Anyway, this decision should be made by the main maintainer here.

[lxx4380]

@hosiet You're right. I wrote a wrong command. However obfs works really well on my server:

~# systemctl status shadowsocks-libev -l
● shadowsocks-libev.service - Shadowsocks-libev Default Server Service
   Loaded: loaded (/lib/systemd/system/shadowsocks-libev.service; disabled)
   Active: active (running) since Tue 2017-10-24 15:13:53 UTC; 7min ago
     Docs: man:shadowsocks-libev(8)
 Main PID: 14484 (ss-server)
   CGroup: /system.slice/shadowsocks-libev.service
           ├─14484 /usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -u
           └─14485 obfs-server

@ghuiii Can you provide full log of shadowsocks-libev.service?

[sethcreate]

@lxx4380

[leonshaw]

@ghuiii It's almost always better to manage services in the way distro provides.

[lxx4380]

I don't think the picture you provided has enough information to find out what's wrong.
You may need to provide more detailed information like this:

[sethcreate]

@lxx4380 That's all , I checked it again.
ss-server works well for me, currently I gived up the systemctl command.
And Killed by sudo kill.

[leonshaw]

Try [email protected]

[hosiet]

There's no fundamental difference between shadowsocks-libev.service and [email protected].

If you want to debug and find out the problem, please provide complete screenshot of output of systemctl status shadowsocks-libev.service.Previous screenshot missed some critical part of the log thus I cannot tell you the reason of problem.

[lxx4380]

There must be some text after "[simple-obfs]", and that is just what we need.

[sethcreate]

@lxx4380 You're right, I missed the important part.

[lxx4380]

Or use port higher than 1024, or edit the service to let ss-server run with root privileges.

[sethcreate]

@debug18 Still doesn't work

[lxx4380]

/usr/local/bin/obfs-server

[debiansid]

You should not install from source. Coz you are not so familiar with Linux.

[dlc9113]

supervisorctl works, or just write a simple shell script:

#!/bin/bash

if [[ $1 == "on" ]]; then
  ss-server -c /etc/shadowsocks.json -u -f /etc/sss.pid
  echo "Shadowsocks turned on"
elif [[ $1 == "off" ]]; then
  kill -9 $(cat /etc/sss.pid)
  echo "Shadowsocks turned off"
else
  echo "Usage: on/off"
fi