Solved jail: ioc-webmail-1: IPv4 addresses clash

byrnejb

byrnejb

tldr; duplicate ip address assignment.

OS=13.2-RELEASE-p9
py39-iocage-1.2_12

I have a iocage managed jail that I transferred from one host to another via zfs send. When I try to start it on the destination host, having first stopped the original on the source host, I get this error:
Code: 
jail: ioc-webmail-1: IPv4 addresses clash

I have searched for any jail that contains the addresses assigned to the problem jail and have come up empty:
Code: 
ip4_addr:em0|216.185.71.96/25,em1|192.168.216.96/16

grep  -H '\.96' /zroot/iocage/jails/*/config.json
/zroot/iocage/jails/webmail-1/config.json:    "ip4_addr": "em0|216.185.71.96/25,em1|192.168.216.96/16",

I then altered the assigned addresses for the transferred jail to other unused addresses and I still get the same error:
Code: 
# iocage set ip4_addr="em1|192.168.216.225/16" webmail-1

# grep  -H '\.225' /zroot/iocage/jails/*/config.json
/zroot/iocage/jails/webmail-1/config.json:    "ip4_addr": "em1|192.168.216.225/16",
ip4_addr: em1|192.168.216.95/16 -> em1|192.168.216.225/16

# iocage start webmail-1
* Starting webmail-1
  + Start FAILED
jail: ioc-webmail-1: IPv4 addresses clash
I have tried several other addresses and they all give the same error. Does anyone have any idea what might be going on?
 
I am in the process of upgrading all our system to 14.1. The move of the jail is to avoid any service interruptions when the inevitable 'Oh, we changed that. It doesn't work anymore' appears on the original host during the upgrade.
 
Found it. It was a duplicate localhost ip assignment.
Code: 
grep  -H '\0.106' /zroot/iocage/jails/*/config.json
/zroot/iocage/jails/webmail-1/config.json:    "localhost_ip": "127.0.106.1",
192.168.216.116/16,em0|216.185.71.36/25,em1|192.168.216.36/16",
/zroot/iocage/jails/webmail-2/config.json:    "localhost_ip": "127.0.106.1",
 
You must log in or register to reply here.
Back
Top