Maintained by: NLnet Labs

[Unbound-users] Can't Bind Socket Error

Paul Stewart
Thu Oct 9 02:08:18 CEST 2014


Hi there.

 

We just started migrating some of our customer base over to Unbound.

 

Server is VM instance (VmWare) with 8 Gig RAM, 4 vCPU's running CentOS 7 (64
bit).  Unbound version 1.4.20 via YUM package install.

 

We started noticing the following errors in the logs this evening:

 

Oct  8 19:48:51 dns2-pppoe unbound: [1110:0] error: can't bind socket:
Permission denied

Oct  8 19:49:24 dns2-pppoe unbound: [1110:0] error: can't bind socket:
Permission denied

Oct  8 19:50:46 dns2-pppoe unbound: [1110:0] error: can't bind socket:
Permission denied

Oct  8 19:56:40 dns2-pppoe unbound: [1110:0] error: can't bind socket:
Permission denied

Oct  8 19:59:24 dns2-pppoe unbound: [1110:0] error: can't bind socket:
Permission denied

 

When looking at stats, the number of lookups and cache hits for that
specific instance keep incrementing.  Just wondering if anyone has any ideas
on what is causing these errors?

 

Thanks,

Paul

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20141008/1d6283cc/attachment.html>