Project

General

Profile

Actions

Bug #2958

closed

Load Balancer: relayd must be manually restarted when added second virtual server

Added by Larry Titus almost 11 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Load Balancer
Target version:
-
Start date:
04/19/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.x
Affected Architecture:
i386

Description

I have 2 CARP WAN IPs setup for use with my 2 DNS servers. I configured the Pool for loadbalance and added the 2 LAN IPs for my DNS servers monitored via ICMP. I then configured a Virtual Server for my first CARP WAN IP (ns1.domain.tld) pointed to my DNS load balance pool, saved and applied changes. This works fine. I then added a second Virtual Server pointing to a second CARP WAN IP (ns2.domain.tld) using the same pool. This second Virtual Server will not start until you manually restart the relayd service. Under Status > Load Balancer > Virtual Servers, the first VS is Active but the second shows "Unknown - relayd not running?". The system log shows:

php: /load_balancer_virtual_server.php: The command '/usr/local/sbin/relayctl reload' returned exit code '1', the output was 'command failed'

To fix you must restart relayd using the restart button in Status > Services. This must be done on both the primary and backup CARP members before the VS will work.

Actions #1

Updated by Larry Titus almost 11 years ago

Also DNSMasq being bound to *:53 by default prevents relayd from binding to port 53 for inbound DNS load balancing. I've been using port 54 for testing load balancing rather than 53.

Actions #2

Updated by Chris Buechler almost 10 years ago

  • Status changed from New to Resolved

not an issue on 2.1x or 2.2

Actions

Also available in: Atom PDF