Dnsmasq fails to start with libidn.so.17: unsupported file layout

groverby

dnsmasq refused to start from web ui

I logged the command used to start dnsmasq in services.inc. That command is:
/usr/local/sbin/dnsmasq –all-servers --dhcp-hostsfile=/var/etc/hosts --server=/cisco.com/64.102.6.247 --dns-forward-max=5000 --cache-size=10000 --local-ttl=1

The command is later wrapped with nohup and stdout and stderr to /dev/null when ran normally.

Running this dnsmasq with these args as root, I get:
/libexec/ld-elf.so.1: /usr/local/lib/libidn.so.17: unsupported file layout

This so is 32bit and the linker is 64bit. I'm pretty sure this is the problem, but I don't get why this would fail unprovoked on some random day. The pfsense box hasn't been touched in quiet some time. I don't see any 64bit libs, should there be any? The hardware is a 64bit vm.

Should this be using 32bit ld or 64bit so? Recommend way to fix?

[2.1.4-RELEASE][root@twigbastion.twigs]/usr/local(24): file /usr/local/lib/libidn.so.17
/usr/local/lib/libidn.so.17: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped
[2.1.4-RELEASE][root@twigbastion.twigs]/usr/local(25): ls /libexec/
ld-elf.so.1 ld-elf32.so.1
[2.1.4-RELEASE][root@twigbastion.twigs]/usr/local(26): file /libexec/ld-elf.so.1
/libexec/ld-elf.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped

groverby

Version info:

2.1.4-RELEASE (amd64)
built on Fri Jun 20 12:59:50 EDT 2014
FreeBSD 8.3-RELEASE-p16

doktornotor

Frankly, noone here cares about outdated versions and nothing will get fixed there. Plus, looks like you did an accidental cross-arch upgrade at least once, leaving junk behind.

groverby

Frankly, noone here cares about outdated versions and nothing will get fixed there.
Fair enough.

Plus, looks like you did an accidental cross-arch upgrade at least once, leaving junk behind.
Could be. As near as I could tell, it had not been updated since install, but clearly something happened.

My guess is:

Sometime in the past, libraries, ld.so.conf or something got hosed.
dnsmasq fell over today for unrelated reason and couldn't restart.

I reinstalled it. It's a lab, so meh…