Project

General

Profile

Bug #6993

OpenVPN status error during CARP state transition

Added by James Webb over 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
OpenVPN
Target version:
-
Start date:
12/07/2016
Due date:
% Done:

0%

Estimated time:
0.50 h
Affected Version:
Affected Architecture:

Description

Running two devices in HA and have stacked one IP Alias onto the CARP IP. If I bind a OpenVPN server to the IP Alias (on both machines) then during a switch of a carp state, one of the devices will throw the error on the status page "error contacting daemon". This doesn't affect functionality as the OpenVPN service is still running underneath. It just tries to start another OpenVPN instance over an existing one -> address already bound by currently running instance.
So can it be fixed that a new OpenVPN instance is not trying to start without the other one being shutdown first :)

History

#1 Updated by Mario Lener about 2 years ago

James Webb wrote:

Running two devices in HA and have stacked one IP Alias onto the CARP IP. If I bind a OpenVPN server to the IP Alias (on both machines) then during a switch of a carp state, one of the devices will throw the error on the status page "error contacting daemon". This doesn't affect functionality as the OpenVPN service is still running underneath. It just tries to start another OpenVPN instance over an existing one -> address already bound by currently running instance.
So can it be fixed that a new OpenVPN instance is not trying to start without the other one being shutdown first :)

Same error. Two appliance running pfSense 2.3.3_p1.

Also available in: Atom PDF