Aprsend detecting another computer.

[drott]

I cannot figure this one out

I moved hosts over the weekend. The ip addressing and everything is working fine but one CT.

I am supposed to be on a dedicated block with a /24 assigned addresses.

Yet if I ping for that IP address I get no response when I turn of the container. Container is Deb 7. Latest build of proxmox 3.4 with all patches applied.

The two containers to the left and right of it by ip address +1 and -1 are running just fine.

Starting container ...
Container is mounted
Adding IP address(es): 1xx.142.167.1xx
arpsend: 1xx.142.167.1xx is detected on another computer : 74:8e:f8:62:43:81
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 1xx.142.167.1xx vmbr0 FAILED
Setting CPU units: 1000
Setting CPUs: 2
Container start in progress...
TASK OK

output from pveversion -v

proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve)
pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
pve-kernel-2.6.32-40-pve: 2.6.32-160
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-38-pve: 2.6.32-155
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[udo]

Hi,
and can you find the machine with the same IP?

arping -i vmbr0 74:8e:f8:62:43:81

Udo

 

[drott]

Hi, sorry for the delayed in response. We found the problem. The hosting provider forgot to add that ip address in the assigned pool. It took them a bit as because of the false positiive as to arp reply and the indicator an ip address was in use. Thanks.