Shadowsocks-libev: Where can I find the log file

Created on 23 Sep 2016  ·  4Comments  ·  Source: shadowsocks/shadowsocks-libev

Please answer these questions before submitting your issue. Thanks!

What version of shadowsocks-libev are you using?

shadowsocks-libev 2.5.2

What operating system are you using?

CentOS release 6.8 (Final) x86_64

What did you do?

I want read the ss-server logs ,but can't find the log file
/var/log/user.log: No such file or directory
/var/log/syslog: No such file or directory

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

NAME=shadowsocks-server
DAEMON=/usr/bin/ss-server
CONF=/etc/shadowsocks.json
PID=/var/run/$NAME/pid
daemon $DAEMON -u -c $CONF -f $PID -v

question

Most helpful comment

I also use centos 6 and I start ss-server like this.
ss-server -c /etc/ss.json -v -f /tmp/ss-tmp.pid
but /var/log/messages and /var/log/secure are both empty

So where did you finally find your log?
Thanks.

All 4 comments

Thank you

I also use centos 6 and I start ss-server like this.
ss-server -c /etc/ss.json -v -f /tmp/ss-tmp.pid
but /var/log/messages and /var/log/secure are both empty

So where did you finally find your log?
Thanks.

I've using docker image to check the logs. example.:

$ docker logs -f ss-libev 
 2020-07-17 17:48:13 [simple-obfs] INFO: obfuscating enabled
 2020-07-17 17:48:13 INFO: plugin "obfs-server" enabled
 2020-07-17 17:48:13 INFO: UDP relay enabled
 2020-07-17 17:48:13 INFO: initializing ciphers... chacha20-ietf-poly1305
 2020-07-17 17:48:13 INFO: Stream ciphers are insecure, therefore deprecated, and should be almost always avoided.
 2020-07-17 17:48:13 INFO: tcp server listening at 127.0.0.1:42960
 2020-07-17 17:48:13 INFO: udp server listening at 0.0.0.0:9000

If using service instead of docker image, then try find details from /var/log/messages and /var/log/secure, details:

$ sudo find /var/log/ -type f -exec grep -l 'ss-server' {} \; -print
/var/log/messages
/var/log/secure

$ sudo find /var/log/ -type f -exec grep -n -i -H --color=always 'obfs-server' {} \; -print
/var/log/messages:37214:Jul 16 08:11:35 <my-server> /usr/local/bin/ss-server[14953]: plugin "obfs-server" enabled
/var/log/messages:37235:Jul 16 08:14:30 <my-server> /usr/local/bin/ss-server[15730]: plugin "obfs-server" enabled
/var/log/messages:37604:Jul 16 08:16:44 <my-server> /usr/local/bin/ss-server[16189]: plugin "obfs-server" enabled
...

or using $ journalctl -f -u shadowsocks-libev.service to check if the service started by systemctl

Was this page helpful?
0 / 5 - 0 ratings