Dhcp: Could not run unbound-control local_data

Networking
12

Tried it on a VirtualBox test environment, I do not get those errors.

Does that mean my unbound data is corrupt somewhere?

13

Hi Paul,

I am not sure why you are encountering what you are. However I can confirm that I don’t see any messages like that in my production or vm development IPFire machines.

I tried searching on the error code number but unbound-control has an error number of 0 when everything works well and 1 when any error occurs.

All the IP’s showing a problem are from the dhcp dynamic range. The earliest ones had no additional info after the error code: 1: entry but the latest ones you show have error code: 1: b’’ but I haven’t been able to find anything when searching for that either.

Do any of those entries giving a problem appear in /etc/unbound/hosts.conf/

Do any of the hostnames for those clients having a problem have peculiar characters in their hostnames such as spaces.

So T5600.lan in the above presumably means that T5600 is the hostname for that client . Is T5600 the complete hostname or did something get cut off due to a space or unusual character.

Beyond the above I don’t have any further ideas.

14

I’m stumped as well …
I rebooted my ipfire, I still see those errors.
I turned OFF my ipfire, let the electrons die, then powered up. Still, same errors.
My thought is take a backup, re-install ipfire, reconfigure it, and restore from backup.

15

That error comes from the unbound-dhcp-leases-bridge code, line 546

ref: ipfire-2.x/unbound-dhcp-leases-bridge at master · ipfire/ipfire-2.x · GitHub

16

@bonnietwin regarding /etc/unbound/hosts.conf

I only have 2 static hosts, (ipfire 10.0.0.1 and pve5 10.0.0.5) but if I cat the file, line 1 is repeated as line 5, line 3 I have no idea where it came from (none of my network uses 192.168.*) so something is out of whack. Tried to flush everything in unbound, was not successful.

[root@ipfire ~]# cat /etc/unbound/hosts.conf 
# This file is automatically generated and any changes
# will be overwritten. DO NOT EDIT!

local-data: "ipfire.lan 60 IN A 10.0.0.1"
local-data: "1.0.0.10.in-addr.arpa 60 IN PTR ipfire.lan"
local-data: "1.1.168.192.in-addr.arpa 60 IN PTR ipfire.lan"
local-zone: lan transparent
local-data: "ipfire.lan 60 IN A 10.0.0.1"
local-data: "pve5.lan 60 IN A 10.0.0.5"
local-data: "5.0.0.10.in-addr.arpa 60 IN PTR pve5.lan"
17

ipfire.lan appears twice in the above list. Probably the first once from setup. Maybe the second one from menu Network > Edit Hosts ?

I am curious - do you have ipfire in the edit hosts page? (I do not)

Screen Shot 2021-12-05 at 11.52.31 AM
Screen Shot 2021-12-05 at 11.52.31 AM1946×666 97 KB

If so, you may want to delete it and see if it helps.

18

I need to have it else the hostname ipfire would not resolve.

image
image929×150 17.6 KB

19

FYI - I created an SSH config file so shorten my ssh entries. Instead of:

ssh -p '222' root@192.168.1.1

I type

ssh ipfire

look up ssh config

20

That is probably a different issue. ( I am trying to remember where hostname is stored on the IPFire…)

EDIT:
Here is one in setup:
hostname_v1

EDIT2:
Here is the other:
interface_red_dhcp

What are yours set to?

21

Both are set to ipfire

Notes:
/etc/hosts does not contain ipfire, only localhost
/etc/hostname: no such file or directory

if I type hostname, I get
ipfire.lan

I type ssh root@ipfire since I’m not root at my system, my username is pavlos
If I would type ssh ipfire, it would try to connect to pavlos@ipfire (no such user)
hence I need to explicitly type root@ipfire

22

I saw the same. That is why I looked for the setup screens

FYI - I can ping ipfire from any of my computers and it works a-ok. And I have no separate hostname for ipfire.

I am not saying this will cure the above issue (first post). It was just a curious observation on my side.

23

Agreed - if there is no ssh config file.

see:

This is my ssh config file (on my personal computer):

Host ipfire
	HostName=192.168.1.1
	User=root
	Port=222
24

update: I will consider them solved.

First issue: the error line is generated b/c my little reset script issues:

/etc/init.d/dhcp stop
/etc/init.d/dhcp start
/etc/init.d/unbound restart

A sleep 2 before the last line gives time to dhcp to start and then unbound to restart, I no longer see these errors in /var/log/messages

Second issue:

local-data: "1.1.168.192.in-addr.arpa 60 IN PTR ipfire.lan"

this line appears b/c 9 months ago I plugged in a usb wifi and configured a blue network. I no longer use the blue network but I found that /var/ipfire/ethernet/settings still contained references for the blue network which is long gone.

2 Likes
25

Hi,

well, this should not happen, but usually, such leftovers do not cause as much trouble as you experienced. Glad you found this one… :slight_smile:

Thanks, and best regards,
Peter Müller

26

Peter, I kept the old /var/ipfire/ethernet/settings file

BLUE_DEV=blue0
BLUE_MACADDR=zzzzzzzzzzzzzzzzzz
BLUE_DESCRIPTION='"usb: Linksys WUSB600N v1 Dual-Band Wireless-N Network Adapter [Ralink RT2870]"'
BLUE_DRIVER=rt2800usb
BLUE_ADDRESS=192.168.1.1
BLUE_NETMASK=255.255.255.0
BLUE_NETADDRESS=192.168.1.0
BLUE_BROADCAST=192.168.1.255

Since I got rid of the blue network 9 months ago, those lines should have been removed from /var/ipfire/ethernet/settings The puzzle was that /etc/unbound/hosts.conf had a reference to 192.* and that led me to a wild chase to find out why. Glad I found it so I can sleep at night :slight_smile:

27

Can you ssh root@ipfire?

Or ping ipfire now?

28

yes, as I wrote before I had to add ipfire in my static hosts.

29

to me that is just odd…

I’ve never had to add ipfire as a static host. Do you need to add all of your devices as static hosts? I see only two in an above post.

30

Jon, I removed ipfire as one of my static hosts. I can still ping ipfire from a client so you’re correct, I do not need to define ipfire as a static host. But if I remove pve5 from the static hosts list, I cannot ping pve5 I only define in static hosts those hosts that I would like to ping by name.

1 Like