Nomad stop working once DHCP lease of machine expires


I have virtual machines(VMware vmxnet) where DHCP is enabled and every 24 hours its lease expires. Due to this, ip automatically change and nomad unable to connect to nodes.

Is there any way to handle this situation so that nomad automatically updates its ip after every lease expiration.

Please help.

Thank you

Coupled with the go-sockaddr syntax (as mentioned in the Gitter channel) …

How about cron job which checks “previous ip” vs. “new ip” and then restarts the Nomad agent? (#quick-hack)

BTW forced expiry at 24 hours of DHCP IP ?!? :face_with_raised_eyebrow:


Sorry, my bad I’ve written 24 hours. Actually what happen exactly is lease renew for a very short time. I don’t know much of DHCP but these are the few logs I got :

Output checked on 15th October
Lease Expires . . . . . . . . . . : Friday, October 16, 2020 12:13:28 PM

Output checked on 16th October
Lease Expires . . . . . . . . . . : Friday, October 16, 2020 4:13:28 PM

However, IP doesn’t changed yet.