Amahi 8 Troubleshooting

New Install

Could not resolve host: f21.amahi.org

If you get the error

 Could not resolve host: f21.amahi.org

this is probably because the system did not get a network connection working. This could be for a number of reasons, including bad cabling, connecting the network cable to the wrong interface or driver incompatibility. Make sure your connectivity and drivers are working well with the OS.

Upgrade

Virtualization Stack Breaks DNS/DHCP Server

This happens on some Fedora 19 to 21 upgrades, but also after installing desktop components or VNC.

After performing the upgrade, the DHCP/DNS server is not functional.

To verify if the service is functional do the following from a command line:

 sudo systemctl status dnsmasq.service

If its not working you will get a message similar to below with a failed status:

dnsmasq.service - DNS caching server.

Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled)

Active: failed (Result: exit-code) since Tue 2015-09-08 10:38:40 MST; 6s ago

Process: 7798 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=2)

Main PID: 7798 (code=exited, status=2)

This may be caused somehow by libvirtd having being installed during the upgrade to F21. Unfortunately, libvirtd uses dnsmasq for virtual machines in a way that conflicts with Amahi 8. To verify this is the issue do the following commands:

 sudo lsof -i :53

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

dnsmasq 1308 nobody 6u IPv4 20640 0t0 UDP localhost.localdomain:domain

dnsmasq 1308 nobody 7u IPv4 20641 0t0 TCP localhost.localdomain:domain (LISTEN)

 ps -ef| grep <number in bold above>

nobody 1308 1 0 10:04 ? 00:00:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/libexec/libvirt_leaseshelper

root 1309 1308 0 10:04 ? 00:00:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/libexec/libvirt_leaseshelper

The Work-around/Solution

if you see something like --conf-file=/var/lib/libvirt/dnsmasq/default.conf then you can fix the dnsmasq problem by issuing the following command and then rebooting.

 sudo systemctl disable libvirtd

 sudo reboot

Back to the Troubleshooting page.