Unbound TCP buffer settings not sticky

markn62 · Nov 4, 2013, 11:41 PM

I occasionally get the error "unbound [23056:0] error: read (in tcp:s): Operation timed out" which got me looking at this more closely. I thought perhaps if I used UDP "only" this error wouldn't occur.

What I found was the Unbound package GUI appears to have an issue with regard to incoming and outgoing TCP buffer settings. The GUI guidance is that if set to zero then no TCP queries will be sent to the authoritative server. I set both to zero and the /usr/pbi/unbound-amd64/etc/unbound/unbound.conf still reports a default value of 10 on both even after restarting the Unbound service.

Any reason the GUI settings don't modify the .conf file?

markn62 · Nov 14, 2013, 4:52 PM

wagonza · Feb 23, 2014, 2:07 PM

@markn62 was this problem fixed for you? or is it still an issue?

wagonza · Feb 23, 2014, 5:38 PM

@markn62 - ive made some changes which should make these options stick. Let me know if it works for you.

markn62 · Feb 23, 2014, 6:10 PM

Presume I would need to apply a snapshot. Is the snapshot dated today?

wagonza · Feb 23, 2014, 6:12 PM

Nope - just update your Unbound package.

markn62 · Feb 23, 2014, 6:18 PM

Thanks I'll check and report back.

doktornotor · Feb 23, 2014, 7:30 PM

I guess something got broken here on the way? On trying to save advanced settings I get


The following input errors were detected:

You must enter a valid number in 'TTL for lame delegation'.

wagonza · Feb 23, 2014, 7:42 PM

Fixed. Reinstall :/

doktornotor · Feb 23, 2014, 7:48 PM

@wagonza:

Reinstall :/

Hehe, I'll cron an hourly reinstall I guess. :D

Fixed, thanks again! 8)

wagonza · Feb 24, 2014, 4:09 AM

@doktornotor:

Hehe, I'll cron an hourly reinstall I guess. :D

Ha! Cool thanks for the feedback.

markn62 · Feb 26, 2014, 8:20 AM

Upgraded the service watchdog package fine. Then went onto the unbound upgrade and it failed. Now I get "Unable to retrieve package info from www.pfsense.com. Cached data will be used" which doesn't get me anywhere.

markn62 · Feb 26, 2014, 9:34 AM

First attempt at a package upgrade failed. Had to reboot pfsense then the unbound version 1.4.21_3 package would install. Go figure.

In the GUI I changed both "incoming TCP buffers" and "outgoing TCP buffers" from 10 to zero and /usr/pbi/unbound-amd64/etc/unbound/unbound.conf reports;

outgoing-num-tcp: 10
incoming-num-tcp: 10

So no change that I can see.

wagonza · Feb 26, 2014, 9:45 AM

Thanks for the feedback. Found the problem and fixed.

markn62 · Feb 26, 2014, 4:01 PM

When do you plan to release the fix?

wagonza · Feb 26, 2014, 4:53 PM

Its released so you just need to reinstall the package. I didnt bump the version.

markn62 · Feb 26, 2014, 5:31 PM

Ahhh, didn't know I could PKG from the "installed packages" tab. I'll report back by tomorrow.

shinzo · Feb 26, 2014, 6:16 PM

After installing unbound 1.4.21_3 none of the custom options i am using seem to work anymore. The error is

php: config.inc: The command '/usr/pbi/unbound-amd64/sbin/unbound-control start' returned exit code '1', the output was '/usr/pbi/unbound-amd64/etc/unbound/unbound.conf:104: error: syntax error read /usr/pbi/unbound-amd64/etc/unbound/unbound.conf failed: 1 errors in configuration file [1393437916] unbound[79295:0] fatal error: Could not read config file: /usr/pbi/unbound-amd64/etc/unbound/unbound.conf'

When i went into the file it starts on the first line of the custom options, if i remove all the options i have it will boot fine.

"msg-cache-slabs: 1;rrset-cache-slabs: 1;infra-cache-slabs: 1;key-cache-slabs: 1;outgoing-range: 950;val-clean-additional: yes;harden-glue: yes;do-not-query-localhost: yes;do-ip6: no;use-caps-for-id: no;hide-identity: yes;hide-version: yes"

the custom options i was using. I even tried using them one at a time and it still give me the errors.

bryan.paradis · Feb 26, 2014, 6:30 PM

@shinzo:

After installing unbound 1.4.21_3 none of the custom options i am using seem to work anymore. The error is

php: config.inc: The command '/usr/pbi/unbound-amd64/sbin/unbound-control start' returned exit code '1', the output was '/usr/pbi/unbound-amd64/etc/unbound/unbound.conf:104: error: syntax error read /usr/pbi/unbound-amd64/etc/unbound/unbound.conf failed: 1 errors in configuration file [1393437916] unbound[79295:0] fatal error: Could not read config file: /usr/pbi/unbound-amd64/etc/unbound/unbound.conf'

When i went into the file it starts on the first line of the custom options, if i remove all the options i have it will boot fine.

"msg-cache-slabs: 1;rrset-cache-slabs: 1;infra-cache-slabs: 1;key-cache-slabs: 1;outgoing-range: 950;val-clean-additional: yes;harden-glue: yes;do-not-query-localhost: yes;do-ip6: no;use-caps-for-id: no;hide-identity: yes;hide-version: yes"

the custom options i was using. I even tried using them one at a time and it still give me the errors.

The options in the configuration file should be like below


option: blah
option: blah
option: blah

the gui should take the custom options then split them by the delimiter ; then it puts them on a new line for each option

	# Handle custom options
	if (!empty($adv_config['custom_options'])) {
		$custom_options = explode(";", ($adv_config['custom_options']));
		$unbound_conf .= "\n# Unbound Custom options\n";
		foreach ($custom_options as $ent)
			$unbound_conf .= $ent."\n";

Is that the line you see exactly in your config file? What are you putting in the advanced options form in the gui?

shinzo · Feb 26, 2014, 6:42 PM

@bryan.paradis:

@shinzo:

After installing unbound 1.4.21_3 none of the custom options i am using seem to work anymore. The error is

php: config.inc: The command '/usr/pbi/unbound-amd64/sbin/unbound-control start' returned exit code '1', the output was '/usr/pbi/unbound-amd64/etc/unbound/unbound.conf:104: error: syntax error read /usr/pbi/unbound-amd64/etc/unbound/unbound.conf failed: 1 errors in configuration file [1393437916] unbound[79295:0] fatal error: Could not read config file: /usr/pbi/unbound-amd64/etc/unbound/unbound.conf'

When i went into the file it starts on the first line of the custom options, if i remove all the options i have it will boot fine.

"msg-cache-slabs: 1;rrset-cache-slabs: 1;infra-cache-slabs: 1;key-cache-slabs: 1;outgoing-range: 950;val-clean-additional: yes;harden-glue: yes;do-not-query-localhost: yes;do-ip6: no;use-caps-for-id: no;hide-identity: yes;hide-version: yes"

the custom options i was using. I even tried using them one at a time and it still give me the errors.

The options in the configuration file should be like below
option: blah
option: blah
option: blah
the gui should take the custom options then split them by the delimiter ; then it puts them on a new line for each option
	# Handle custom options
	if (!empty($adv_config['custom_options'])) {
		$custom_options = explode(";", ($adv_config['custom_options']));
		$unbound_conf .= "\n# Unbound Custom options\n";
		foreach ($custom_options as $ent)
			$unbound_conf .= $ent."\n";
Is that the line you see exactly in your config file? What are you putting in the advanced options form in the gui?

I looked over the code and it is the same. In the advanced options in the gui i have

"msg-cache-slabs: 1;rrset-cache-slabs: 1;infra-cache-slabs: 1;key-cache-slabs: 1;outgoing-range: 950;val-clean-additional: yes;harden-glue: yes;do-not-query-localhost: yes;do-ip6: no;use-caps-for-id: no;hide-identity: yes;hide-version: yes" as the semi colon is used to make a new line.

when i go into the config file, it is being set correctly.

Unbound Custom options

msg-cache-slabs: 1
rrset-cache-slabs: 1
infra-cache-slabs: 1
key-cache-slabs: 1
outgoing-range: 950
val-clean-additional: yes
harden-glue: yes
do-not-query-localhost: yes
do-ip6: no
use-caps-for-id: no
hide-identity: yes
hide-version: yes