[SOLVED] error in dns resolver



  • Hello, after updating to pfsense 2.4.0.r.20171004.1205, in the dns resolver menu, if I make any changes I have this error:

    The following input errors were detected:
    
        The generated config file cannot be parsed by unbound. Please correct the following errors:
        /usr/local/lib/libpython2.7.so.1: invalid file format
    

    Another thing: the unbound DNS Resolver service does not even start manually.
    Can you help me to fix everything?

    many thanks in advance

    log

    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.91.13 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.203.230.10 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.91.13 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.58.128.30 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 193.0.14.129 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.58.128.30 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.5.5.241 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.36.148.17 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 198.41.0.4 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.112.36.4 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 193.0.14.129 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 193.0.14.129 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.203.230.10 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 198.41.0.4 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.203.230.10 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.83.42 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 192.203.230.10 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.83.42 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.83.42 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.83.42 port 53
    Sep 30 01:29:17 	unbound 	62231:3 	notice: sendto failed: Permission denied
    Sep 30 01:29:17 	unbound 	62231:3 	notice: remote address is 199.7.83.42 port 53
    Sep 30 01:31:17 	unbound 	20928:0 	notice: init module 0: validator
    Sep 30 01:31:17 	unbound 	20928:0 	notice: init module 1: iterator
    Sep 30 01:31:17 	unbound 	20928:0 	info: start of service (unbound 1.6.3).
    Sep 30 01:35:43 	unbound 	24994:0 	notice: init module 0: validator
    Sep 30 01:35:43 	unbound 	24994:0 	notice: init module 1: iterator
    Sep 30 01:35:43 	unbound 	24994:0 	info: start of service (unbound 1.6.3).
    Oct 5 09:13:42 	kernel 		unbound: 1.6.3 -> 1.6.6 [pfSense]
    Oct 5 09:13:42 	kernel 		dnsmasq: 2.77_1,1 -> 2.78,1 [pfSense] 
    




  • I solved!!!
    I've copied the files, which you find in attachment and I've solved it.

    libpython2.7.zip


  • Rebel Alliance Developer Netgate

    I can't seem to reproduce that on any of my 2.4 systems tracking snapshots.

    Do you have anything custom in your DNS Resolver configuration?

    The libpython2.7.so.1 file on my systems appears to be fine and in the correct format. I get no errors from the resolver and everything is running as expected.

    Did you have any errors during the upgrade? Anything noteworthy in /conf/upgrade_log.latest.txt ?



  • pfsense upgrade crashed and I had this kind of error.
    Unfortunately I can not send the error log file, because I was forced to format and reinstall pfsense.
    Yesterday I had a much worse problem: I did upgrade to pfsense 2.4.0.r.20171008.0625 and now I can no longer associate any ip.
    I have the same error:
    https://forum.pfsense.org/index.php?topic=137672.0
    Tonight I have to format and restore the backup.