Project

General

Profile

Actions

Bug #4779

closed

OPENVPN - Exiting due to fatal error

Added by Jan-Hendrik Meyer almost 9 years ago. Updated over 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
06/21/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Since I'm using pfSense 2.2.2 I get the following error, every time the switch is turned off - the device is disconnected.

May 18 00:10:35 openvpn8621: Inactivity timeout (--ping-restart), restarting
May 18 00:10:35 openvpn8621: SIGUSR1[soft,ping-restart] received, process restarting
May 18 00:10:37 openvpn8621: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
May 18 00:10:37 openvpn8621: Re-using pre-shared static key
May 18 00:10:37 openvpn8621: TCP/UDP: Socket bind failed on local address [AF_INET]10.184.1.2:10000: Can't assign requested address
May 18 00:10:37 openvpn8621: Exiting due to fatal error
May 18 00:10:37 openvpn8621: /usr/local/sbin/ovpn-linkdown ovpnc1 1500 1565 192.168.201.242 192.168.201.241 init
May 18 00:10:37 openvpn8621: Closing TUN/TAP interface

In my environment the network is turned off at night.
so I have to restart the openvpn service by hand each morning, which is a lot of manual work.
Maybe someone can fix it? So that the openvpn daemon sleeps until the cable is up again. (It was like that in the last pfSense version 2.2.1)

I'm not sure, if this is an issue related to changes in pfSense or in OpenVPN, please tell me if it is not due to pfSense so that I can inform the people programming OpenVPN

Actions #1

Updated by Chris Buechler almost 9 years ago

  • Category set to OpenVPN
  • Status changed from New to Feedback

The "can't assign requested address" means something is already listening on port 10000. You have something else bound to port 10000? Can check 'sockstat -4' output to see what.

Actions #2

Updated by Chris Buechler over 8 years ago

  • Status changed from Feedback to Not a Bug

This is probably caused by having some other service configured on port 10000. If not, it's #4642

Actions

Also available in: Atom PDF