Job for wireproxy.service failed because a fatal signal was delivered to the control process.
See "systemctl status wireproxy.service" and "journalctl -xeu wireproxy.service" for details.
9月 29 02:42:24 athena systemd[1]: Starting Wireproxy socks5/http tunnel...
░░ Subject: A start job for unit wireproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit wireproxy.service has begun execution.
░░
░░ The job identifier is 43768.
9月 29 02:42:24 athena systemd[1]: wireproxy.service: Control process exited, code=killed, status=31/SYS
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStartPre= process belonging to unit wireproxy.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 31.
9月 29 02:42:24 athena systemd[1]: wireproxy.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit wireproxy.service has entered the 'failed' state with result 'signal'.
9月 29 02:42:24 athena systemd[1]: Failed to start Wireproxy socks5/http tunnel.
░░ Subject: A start job for unit wireproxy.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit wireproxy.service has finished with a failure.
░░
░░ The job identifier is 43768 and the job result is failed.
goddade
commented
1 month ago