Bugs: tinydns server and radvd



  • pfSense version: pfSense-LiveCD-2.2-RC-i386-20150116-1153 (i386)
    Server poweredge 1600SC (no x64 capable)
    NICS: Intel e1000

    Hi,
    Im testing the latest snapshot, but I've found some problems:
    tinydns refuses to start, I've tried everything, and nothing: no error in system logs, no errors via console. I just installed pfsense 2.1.5 on the same server and tinydns works out of the box.
    The only errors in system log that I found were:

    
    php-fpm[277]: /rc.start_packages: XML error: no packagegui object found!
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: [tinydns] tinydns_xmlrpc_sync.php is starting.
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: Sync items done.
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: [tinydns] tinydns_xmlrpc_sync.php is starting.
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: Ping items done.
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: Zone file done.
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: Begin tinydns resync
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: XML error: Invalid document end at line 59 in /usr/local/pkg/pf/tinydns_xmlrpc_sync.php
    Jan 19 15:05:43	php-fpm[277]: /rc.start_packages: [tinydns] tinydns_xmlrpc_sync.php is starting.
    
    

    How to reproduce:
    Clean install using pfSense version: pfSense-LiveCD-2.2-RC-i386-20150116-1153.iso
    Configure wan and lan ip/interface via console
    Follow the initial wizard (configure dns, hostname, etc.)
    Go to packages and install dns-server
    start svscan  and it says "svscan has been started" but it remains in stopped state.

    I thought that maybe unbound may be using the dns port, but even disabling unbound doesn't fix it.

    The same steps works in 2.1.5 with no problems.

    RADVD
    I'don't know why every time the system boots, the system log shows an error telling that radvd cannot start because /usr/local/lib/libdaemon.so.0 is not found.
    If I try to start radvd using the same command that appears in system log I get the same error.

    I can reproduce the error using the server and a virtual machine, so I suspect that is not hardware related.

    Someone can help me?

    Thanks.
    PD: Sorry for my english, I'm not a native english speaker.


Log in to reply