Can't bind socket (192.168.0.10:9989)!

[Tomas]

Hi experts,

I am doing test on MMM on ubuntu 9.04, all fine.

but while i migrate it to redhat 5, I encounter some error.

My redhat is 64bit and I compiled source code libnet 1.1.4 for MMM.

but I can not start mmm_agent.

it report error like this "Can't bind socket (192.168.0.10:9989)!"

Is that because of My miss some package of MMM in redhat ?

here is what i installed:

libnet-1.1.4.tar.gz

Algorithm-Diff-1.15

libproc-daemon-perl_0.03.orig.tar.gz

and I compile the send_arp.c file after change LIBNET_VERSION=1_0 to
LIBNET_VERSION=1_1,
the file is compiled ok.

Any suggestion ?

I checked the code and error happened while execute lib/
agent_commands.pm.

Thanks a lot.

Yours Tomas

[Walter Heck]

Usually that means something is already listening on that port. Try
netstat -l and see if it shows up?

Walter

[Tomas]

sorry , as i check netstat, port 9989 is not used by anyother things.
I am using host rent from a cloud system, is that a possible reason ?

On Oct 13, 6:29 pm, Walter Heck <walterh...@gmail.com> wrote:
> Usually that means something is already listening on that port. Try
> netstat -l and see if it shows up?
>
> Walter
>

[Walter Heck]

What does 'ip addr show' give at the new host?

Walter

[Tomas]

Thanks , i change a new version of Algorithm-Diff-1.19 and now the
agent is working.

But I encounter another problem.
My virtual IP on agent host can not be pinged by monitor, and other
agent host,
So , I can not provide virtual write IP for application server because
the application server can not ping the virtual ip,
Which is quite strange, here is the list of "ip addr show"

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 40:40:20:98:fe:8f brd ff:ff:ff:ff:ff:ff
inet 167.123.42.32/24 brd 167.123.42.255 scope global eth0
inet 167.123.42.21/32 scope global eth0
inet 167.123.42.20/32 scope global eth0
inet6 fe80::4240:20ff:fe98:fe8f/64 scope link
valid_lft forever preferred_lft forever

In this agent server I can ping 167.123.42.32 (this is the real ip),
167.123.42.21 167.123.42.20 (these two are virtual ip generated by
MMM )

but in my another agent server 167.123.42.28, I can ping
167.123.42.32, but can not ping 167.123.42.21, 167.123.42.20 why ?


what kind of issue is that ? Can you give me a help ?

Thanks a lot

Tomas

On Oct 14, 8:40 am, Walter Heck <walterh...@gmail.com> wrote:
> What does 'ip addr show' give at the new host?
>
> Walter
>

[Walter Heck]

Which cloud are you using? Amazon doesn't support virtual IP's. Check
with your cloud provider..

Walter

[Tomas]

I am using rackspace cloud, but why those ip can be shown in ip addr
list ?

but can not reach ???

Thanks a lot.

On Oct 14, 10:53 am, Walter Heck <walterh...@gmail.com> wrote:
> Which cloud are you using? Amazon doesn't support virtual IP's. Check
> with your cloud provider..
>
> Walter
>

[Tim Soderstrom]

Hi Tomas!

Unfortunately, neither Rackspace CloudServers or SliceHost currently
support VIPs which is why Triple-M is not working. This is something
that they are aware of though I am not sure if it is something that
can be easily resolved. In this case, Triple-M might not be a good fit
for a Cloud-based solution :/

Regards,

Tim