I have the same problem with 3.3.1 (on Debian) with no
udp_receive_channel set in the config. Which is how we used to do it.
When I add the udp_receive_channel it works, but I don't want the daemon
to listen.
As a workaround I have now set the daemon to be "deaf", which seems to work.
But it
Argh, I hate breaking the threading but my mailbox seems to have
eaten a bunch of the messages in the thread!
Mark, your patch does the
trick, and that makes sense since most of these systems do not have
udp_receive_channels set. They are just collecting stats and forwarding
them off to a cent
I was gonna say this may be related to similar issues for which a pull
request has been submitted.
https://github.com/ganglia/monitor-core/pull/7
On Thu, 9 Feb 2012, Mark Wagner wrote:
> Do you have any udp_receive_channels defined? Between 3.1.1 and 3.3.1
> the variable "udp_last_heard" was in
Do you have any udp_receive_channels defined? Between 3.1.1 and 3.3.1
the variable "udp_last_heard" was introduced. From just looking at the
source (no experimentation) I'm guessing this is what is happening:
The function setup_listen_channels_pollset(0) sets up the listening tcp
socket. Since
Can you try 3.3.0. I'm running
Red Hat Enterprise Linux Server release 6.1 (Santiago)
2.6.32-131.12.1.el6.x86_64
Vladimir
On Thu, 9 Feb 2012, drich wrote:
In doing some more debugging I'm still stumped. It runs, it's listening on
8649, then it isn't. Running with debug turned
doesn't show
In doing some more debugging I'm still stumped. It runs, it's
listening on 8649, then it isn't. Running with debug turned doesn't show
any errors or unusual messages, just a sudden:
tcp_accept_channel
bind=NULL port=8649
Unable to create tcp_accept_channel. Exiting.
after it runs for almost
Weird, I'm seeing it on two different machines (all that we've
installed it on at this point). Both installed with the same RPM. The
RPM was built by simply extracting the spec file from the source tarball
and running rpmbuild -ba on it.
This is running on RHEL 6.2 just
reinstalled last Wed (o
I have been testing 3.3.1 on RHEL6 and I haven't seen this issue. I
actually kicked off a new VM just now, built RPMS from scratch and it's
working correctly.
Vladimir
On Thu, 9 Feb 2012, drich wrote:
I am starting to test Ganglia 3.3.1 on RedHat Enterprise 6, but have run into a
problem.
I am starting to test Ganglia 3.3.1 on RedHat Enterprise 6, but have
run into a problem. When I attempt to use the same configuration that
worked under 3.1.1 everything works fine for a minute or two, but then
gmond dies with the error: Unable to create tcp_accept_channel.
Exiting.#012. The stra
9 matches
Mail list logo
