flyride

Hello, I'm a Synology user running sabnzbdvpn and delugevpn and first off, thanks to BinHex for the awesome work. Also thanks for the recent dig fix for us Synology users... fortunately it was trivial to backrev to a functional version using Docker. That said, once upgraded to the most recent delugevpn, I noticed a memory leak, about 500K per minute. Started poking around with debug on and noticed that every 30 seconds, the tunnel was (re) verified "up." Note that deluge is downloading and otherwise appears to be working okay despite this message snippet repeated ad infinitum in the logs. The same repeated "up" verification now also appears in the sabnzbd logs but I haven't noticed such a memory leak (at least not quite as aggressive). The repeated message is quoted here: 2018-11-02 14:15:52 stdout 2018-11-02 07:15:52,140 DEBG 'deluge-script' stdout output: 2018-11-02 14:15:52 stdout [debug] Waiting for valid IP address from tunnel... 2018-11-02 14:15:52 stdout 2018-11-02 14:15:52 stdout 2018-11-02 07:15:52,255 DEBG 'deluge-script' stdout output: 2018-11-02 14:15:52 stdout [debug] Valid IP address from tunnel acquired '10.89.10.6' 2018-11-02 14:15:52 stdout 2018-11-02 14:15:52 stdout 2018-11-02 07:15:52,258 DEBG 'deluge-script' stdout output: 2018-11-02 14:15:52 stdout [debug] Incoming port for tunnel is '37273' 2018-11-02 14:15:52 stdout 2018-11-02 14:15:52 stdout 2018-11-02 07:15:52,261 DEBG 'deluge-script' stdout output: 2018-11-02 14:15:52 stdout [debug] VPN incoming port is 37273 2018-11-02 14:15:52 stdout [debug] VPN IP is 10.89.10.6 2018-11-02 14:15:52 stdout [debug] Deluge incoming port is 37273 2018-11-02 14:15:52 stdout [debug] Deluge IP is 10.89.10.6 It seems this is new with the latest release. I can post the startup log if necessary, and/or can stand by for further forensics. Best regards!