| 1 |
On Wed, 8 Mar 2023 12:30:55 -0600 |
| 2 |
Dale <rdalek1967@×××××.com> wrote: |
| 3 |
|
| 4 |
> Michael wrote: |
| 5 |
> > On Tuesday, 7 March 2023 18:11:01 GMT Dale wrote: |
| 6 |
> >> Michael wrote: |
| 7 |
> >>> On Sunday, 5 March 2023 18:41:10 GMT Dale wrote: |
| 8 |
> >>>> Howdy, |
| 9 |
|
| 10 |
<snip> |
| 11 |
> This is from the messages file. I don't see it logged anywhere else. |
| 12 |
> |
| 13 |
> It starts at about 13:54. It seems to try to reconnect but can't. I got this by using tail -n and then grep openvpn on the end. |
| 14 |
> |
| 15 |
> |
| 16 |
> Mar 1 13:53:32 fireball openvpn[27908]: |
| 17 |
> [us-hou-v029.prod.surfshark.com] Inactivity timeout (--ping-restart), |
| 18 |
> restarting |
| 19 |
> Mar 1 13:53:32 fireball openvpn[27908]: /etc/openvpn/down.sh tun0 1500 |
| 20 |
> 1584 10.8.8.9 255.255.255.0 restart |
| 21 |
> Mar 1 13:53:32 fireball openvpn[27908]: SIGUSR1[soft,ping-restart] |
| 22 |
> received, process restarting |
| 23 |
> Mar 1 13:53:32 fireball openvpn[27908]: Restart pause, 5 second(s) |
| 24 |
> Mar 1 13:53:37 fireball openvpn[27908]: NOTE: the current |
| 25 |
<anip> |
| 26 |
> |
| 27 |
> The weird thing, I can stop openvpn, then start it again just seconds later and it works fine for a good long while. |
| 28 |
> |
| 29 |
<snip> |
| 30 |
> |
| 31 |
|
| 32 |
I have seen OpenVPN get stuck and not process a SIGUSR1 properly. Maybe try setting remap-usr1 to SIGHUP in the configuration to reset the state of openvpn or run external kicker script. |
Archives