The issue that you're seeing is that the DHCP client (uhcpc) is unable to obtain a DHCP lease from an upstream system. It attempts to get a DHCP lease twice as a result. If it had succeeded, you would not have seen the second attempt.
What this means is that there is an interface that is set to DHCP client as its protocol (often the WAN interface) and that connection does not have a DHCP server running on an upstream device.
This seems like normal operation as far as I can see. The rest of the dnsmasq service features should be running normally.