dhcp constantly renewing.. I think

English Network/Internet
#1

I found my logs full today with this message repeating constantly…

Jan 10 10:04:49 owncloud wickedd[20412]: received signal LeaseAcquired for interface eno16777736 (ifindex 2), lease ipv4:dhcp/granted, uuid=dc9f7458-0097-0600-bc4f-000003000000, update=0x3ff, flags=0x1
Jan 10 10:04:49 owncloud wickedd[20412]: eno16777736: received ipv4:dhcp lease update in state granted
Jan 10 10:04:49 owncloud wickedd[20412]: timeout 0 adjusted by 65 to 65 (jr 100)
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: sending DHCP4_REQUEST with xid 0xe11f2144
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: incoming dhcp4 packet from 38:2c:4a:4a:02:a8
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: server does not send client-id back
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: received DHCP4_ACK message xid 0x44211fe1 in state RENEWING sender 38:2c:4a:4a:02:a8
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: address 192.168.0.12 is on link, omit validation
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: committing lease
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: schedule renewal of lease in 423465175 seconds
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: setting fsm timeout to 2558379992 msec
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: Committed DHCPv4 lease with address 192.168.0.12 (lease time 4165425092 sec, renew in 423465175 sec, rebind in 423465176 sec)
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: Preparing xml lease data for ‘/var/lib/wicked/lease-eno16777736-dhcp-ipv4.xml’
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: Writing lease to temporary file for ‘/var/lib/wicked/lease-eno16777736-dhcp-ipv4.xml’
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: Lease written to file ‘/var/lib/wicked/lease-eno16777736-dhcp-ipv4.xml’
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: dhcp4_protocol_event(ev=0, dev=2, uuid=dc9f7458-0097-0600-bc4f-000003000000)
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: timeout in state BOUND
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: Initiating renewal of DHCPv4 lease
Jan 10 10:04:50 owncloud wickedd-dhcp4[20411]: eno16777736: setting fsm timeout to 10000 msec
Jan 10 10:04:50 owncloud wickedd[20412]: received signal LeaseAcquired for interface eno16777736 (ifindex 2), lease ipv4:dhcp/granted, uuid=dc9f7458-0097-0600-bc4f-000003000000, update=0x3ff, flags=0x1
Jan 10 10:04:50 owncloud wickedd[20412]: eno16777736: received ipv4:dhcp lease update in state granted
Jan 10 10:04:50 owncloud wickedd[20412]: timeout 0 adjusted by 54 to 54 (jr 100)

I am not sure what to do about it. Also found this output for ps -ef (times about 1000)

root 28700 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 28781 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 28935 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 28975 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 29084 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 29120 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 29384 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 30087 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 30715 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4
root 30874 1 0 10:06 ? 00:00:00 /bin/bash /sbin/netconfig modify -i eno16777736 -s wicked-dhcp-ipv4

I am not sure what else to share to help troubleshoot. I have been googling all night with no luck.

TKS
Chris

#2

Just an idea…Is there a chance that NetworkManager is running as well?

systemctl status NetworkManager

I ask only because I found a mailing list thread where it was found NM/dhclient were running and confusing wicked with respect to DHCP communication.

#3

No, but it gave me an idea that maybe there was multiple if cfg-xxx files. And it turned out that I had left 3 in there. once I removed them and restarted wickedd it all went back to normal. Thanks for the idea!

#4

Well that would do it! :smiley: Glad to have been of help with the thinking anyway.