Status: New
Owner: ----
New issue 918 by [email protected]: ganeti-mond listening not as
described
http://code.google.com/p/ganeti/issues/detail?id=918
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
What distribution are you using?
# gnt-cluster --version
gnt-cluster (ganeti v2.11.5) 2.11.5
# gnt-cluster version
Software version: 2.11.5
Internode protocol: 2110000
Configuration format: 2110000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.11.5
# hspace --version
hspace (ganeti) version v2.11.5
compiled with ghc 7.4
running on linux x86_64
# cat /etc/debian_version
7.6
# apt-cache policy ganeti
ganeti:
Installed: 2.11.5-1~bpo70+1
Candidate: 2.11.5-1~bpo70+1
Package pin: 2.11.5-1~bpo70+1
Version table:
*** 2.11.5-1~bpo70+1 990
100 http://debian.xxxxxxxx.de/debian/ wheezy-backports/main amd64
Packages
100 /var/lib/dpkg/status
2.10.5-1~bpo70+1 990
100 http://debian.xxxxxxxx.de/debian/ wheezy-backports/main amd64
Packages
2.9.5-1~bpo70+1 990
100 http://debian.xxxxxxxx.de/debian/ wheezy-backports/main amd64
Packages
What steps will reproduce the problem?
1. init cluster with primary ipv6
2. netstat -tulpen
What is the expected output? What do you see instead?
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State User Inode PID/Program name
< tcp 0 0 0.0.0.0:1815 0.0.0.0:*
LISTEN 0 5257707 7084/ganeti-mond
tcp 0 :::1815 0.0.0.0:*
LISTEN 0 5257707 7084/ganeti-mond
Please provide any additional information below.
the other daemons to it correctly
# ganeti-mond --help
ganeti-mond (ganeti) version v2.11.3
Usage: ganeti-mond [OPTION...]
[...]
-b ADDR --bind=ADDR Bind address (default depends on cluster
configuration)
Notes:
- version v2.11.3 seams to be wrong to
- "depends on cluster configuration" isn't a exact explanation, one could
think that it will bind it to the primary / secondary IP Address, or that
there is an option for that
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
