View source for Amahi 8 Troubleshooting

== New Installs ==

=== 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.

=== New Disk Wizard not Mounting Drives ===

There is a bug in the Disk Wizard, version 0.7.0, where it sometimes does not mount the drives it formatted, at the end of the process.

TBD - how to mount them by hand

== Fedora 19 to 21 Upgrade==
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:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
  sudo systemctl status dnsmasq.service
</div>

If its not working you will get a message similar to below with a '''failed''' status:
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
:<i>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)
</i></div><br />

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:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
  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
</div>

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.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
  sudo systemctl disable libvirtd
</div>
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
  sudo reboot
</div>