Socks server ss5 in Mageia 4

[leif]

ss5 does not work for me in Mageia 4. I have never had any problems with this server before. Does it work for anyone else?

[doktor5000]

"Does not work" is not really a clear problem description.

[leif]

OK, here is more information. I use ss5 only in my home network and it is protected by a firewall. My /etc/ss5/ss5.conf file looks essentially like this:

Code: Select all

proxy - - - 1080 -
auth 0.0.0.0/0 - -
permit - 0.0.0.0/0 - 0.0.0.0/0 - - - - -


Code: Select all

systemctl restart ss5.service

results in:

Job for ss5.service failed. See 'systemctl status ss5.service' and 'journalctl -xn' for details.

Code: Select all

systemctl status ss5.service

results in:

ss5.service - The Socks Proxy server
Loaded: loaded (/usr/lib/systemd/system/ss5.service; disabled)
Active: failed (Result: timeout) since ons 2014-02-12 07:34:24 CET; 6min ago
Process: 8360 ExecStart=/usr/sbin/ss5 -t $SS5_OPTS (code=exited, status=0/SUCCESS)

feb 12 07:32:54 localhost systemd[1]: PID file /run/ss5/freeswitch.pid not readable (yet?) after start.
feb 12 07:34:24 localhost systemd[1]: ss5.service operation timed out. Terminating.
feb 12 07:34:24 localhost systemd[1]: Failed to start The Socks Proxy server.
feb 12 07:34:24 localhost systemd[1]: Unit ss5.service entered failed state.

Code: Select all

journalctl -xn

results in:

feb 12 07:34:24 localhost systemd[1]: ss5.service operation timed out. Terminating.
feb 12 07:34:24 localhost systemd[1]: Failed to start The Socks Proxy server.
-- Subject: Unit ss5.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit ss5.service has failed.
--
-- The result is failed.
feb 12 07:34:24 localhost systemd[1]: Unit ss5.service entered failed state.

[doktor5000]

feb 12 07:32:54 localhost systemd[1]: PID file /run/ss5/freeswitch.pid not readable (yet?) after start.
feb 12 07:34:24 localhost systemd[1]: ss5.service operation timed out. Terminating.

Did you check the PID file, if one maybe exists already, or permissions issue?

[leif]

Did you check the PID file, if one maybe exists already, or permissions issue?

The PID file /run/ss5/freeswitch.pid does not show up. The issue could be related to this, but I don't know what to do. I have tried to make the directory /run/ss5 writable for everyone, but it did not help. There is however a file ss5.pid in this directory. I looked in another computer, where I run Mageia 3, and I could only find the file ss5.pid in the directory /run/ss5.

[leif]

I edited the file /usr/lib/systemd/system/ss5.service and changed the line PIDFile=/run/ss5/freeswitch.pid to PIDFile=/run/ss5/ss5.pid. After this, I could start ss5. This should be corrected in an updated version of ss5.

[leif]

I edited the file /usr/lib/systemd/system/ss5.service and changed the line PIDFile=/run/ss5/freeswitch.pid to PIDFile=/run/ss5/ss5.pid. After this, I could start ss5. This should be corrected in an updated version of ss5.

Maybe I was too quick here. Yes, ss5 starts now, but I cannot see any indication that the SOCKS server actually works. I have to investigate if there could be anything else wrong. I use the same settings as in Mageia 3. But honestly, I don't think anyone has tested ss5 in Mageia 4.

[doktor5000]

But honestly, I don't think anyone has tested ss5 in Mageia 4.

Probably. Best report both issues into one bug.

FWIW, you cannot used ssh -D for the functionality you require from ss5?