Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 43399 - Service port 0 does not start any ipvsadm routes
Service port 0 does not start any ipvsadm routes
Product: Red Hat High Availability Server
Classification: Retired
Component: piranha (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Copeland
Phil Copeland
Depends On:
  Show dependency treegraph
Reported: 2001-06-04 14:13 EDT by Bowie Bailey
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-06-04 15:02:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lvs.cf, ipvsadm -Ln, and /var/log/messages (5.43 KB, text/plain)
2001-06-04 14:17 EDT, Bowie Bailey
no flags Details

  None (edit)
Description Red Hat Bugzilla 2001-06-04 14:13:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
When I set a service to port 0 as a wildcard port, I see the service in 
ipvsadm, but the routes never show up.

How reproducible:

Steps to Reproduce:
1.Create an LVS setup using port 0 on the virtual service
2.Start Piranha

Actual Results:  You can see the service with ipvsadm, but there are no 

Expected Results:  The routes should open up like any other virtual 

Additional info:

When I tested this, I took a working setup on port 80 and changed it to 
port 0 without making any other changes.  I used "/etc/rc.d/init.d/pulse 
restart" to stop and start the daemons.

I will attach a file containing my lvs.cf, the output of 'ipvsadm -Ln' and 
the relevant portion of the log file.
Comment 1 Red Hat Bugzilla 2001-06-04 14:17:31 EDT
Created attachment 20232 [details]
lvs.cf, ipvsadm -Ln, and /var/log/messages
Comment 2 Red Hat Bugzilla 2001-06-04 15:01:57 EDT
Piranha is just a service monitor and does not define or have anything to do
with routes. That's all part of ipvsadm, ipchains, netfilter, router, etc.

Piranha just starts a monitor process, one per service (which is defined as a n
address and port number), and monitors that service. If the service goes down,
piranha removes it's definition, if it comes back, it's re-added. There are
PLENTY of ipvsadm commands you could create that cannot be mapped into piranha.
ipvs is a generic ip routing filter that can include wildcards, piranha is just
an individual service monitor.

Port 0 is a wildcard port. Piranha cannot start a monitor that means "all
ports". It can only monitor (or connect to or read from) a single port. How
could it monitor "all ports"? It has no information about any client connection
attempts, and certainly it should not start 65535 nanny daemons.

You have to define each service individually.

Note You need to log in before you can comment on or make changes to this bug.