Amahi Wiki - User contributions [en]

Amahi 8 Upgrade

2015-09-09T00:16:15Z

David Schwartz:

'''NOTE:''' There is no upgrade path from [[Fedora_14|Fedora 14]] or [[Ubuntu|Ubuntu 12.04 LTS]] to [[Amahi_8|Amahi 8]]. This will require a new install.

== Preparation ==
'''NOTE:''' We '''recommend you turn on a temporary DHCP server''', (e.g. in your router) since the network may go down for the duration of the actual upgrade.

All commands are executes as <code>root</code> user or precede commands with <code>sudo</code>
* Apps should be uninstalled to ensure success
* Ensure you have your data backed up as a precaution
* Update everything in the system:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y update
</div>
* Reboot to pick up new kernels, etc:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
reboot
</div>
* Update everything in the system again:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y update
</div>
* If there are any updates, do it again. If there are new kernels, reboot:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
reboot
</div>
* Follow with the upgrade below

== Execution ==
Install the upgrade tool:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo yum -y install fedup
</div>
Do the live update over the network:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo fedup --network 21 --product=server
</div>

You may see warnings similar to the following warning but you can ignore them for now. We will clean it up before the upgrade is complete.
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
:<i>WARNING: problems were encountered during transaction test:
:broken dependencies
:perl-PlRPC-0.2020-13.fc19.noarch requires perl-4:5.16.3-266.fc19.x86_64
:ruby-mysql-2.8.2-9.fc19.x86_64 requires ruby-libs-2.0.0.353-16.fc19.x86_64
:Continue with the upgrade at your own risk.</i></div><br />

If the upgrade does not let you due to issues with (for example) extra packages aded by Amahi-installed apps, you may want to add --nogpgcheck option, i.e.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo fedup --network 21 --product=server --nogpgcheck
</div>

Once the previous fedup command is complete, reboot the server (the command will tell you):
<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>
The actual upgrade will take place now, so you will not be able to access the server (or the network) until it is complete.

It would be good to have a monitor/keyboard on the system to cover the risk that the upgrade process becomes stuck somehow. This also should let you keep up with progress.

Be aware it may take 15 to 30 minutes at a minimum for the upgrade to complete, depending on your hardware.

Once the upgrade is complete, from the command line execute:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo yum check
</div>
The following message or similar will be displayed:
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
:<i>perl-PlRPC-0.2020-13.fc19.noarch has missing requires of perl(:MODULE_COMPAT_5.16.2)
:ruby-mysql-2.8.2-9.fc19.x86_64 has missing requires of libruby.so.2.0()(64bit)
:Error: check all</i></div><br />

To correct these issues, remove the two bad packages (though this could be dangerous if you had a lot of apps installed (in which case we do not recommend it):
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo yum remove perl-PlRPC-0.2020-13.fc19.noarch ruby-mysql.x86_64
</div>
Ensure all the problems are corrected and execute:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo yum check
</div>
The response should be <code>check all</code> which indicates everything is correct.

Now check the functionality of the Amahi dashboard after you get a DHCP lease from your HDA in your client(s). If the process completed successfully, you are now running Fedora 21 with the latest Amahi platform.

[[Amahi_8_Upgrade_Issues_and_Solutions|Amahi 8 Upgrade issues and solutions]]

Ref: [https://fedoraproject.org/wiki/FedUp FedUp Wiki]

Go back to the [[Amahi_8|Amahi 8]] page.

Amahi 8 Troubleshooting

2015-09-09T00:13:33Z

David Schwartz:

{{WorkInProgress}}







===After performing the upgrade, the dhcp and dns server are 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 similer 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 />

During the upgrade libvirtd was installed. libvirtd uses dnsmasq for virtual machines. This caused a conflict. 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>

Amahi 8 Troubleshooting

2015-09-09T00:10:17Z

David Schwartz: Created page with "  ..."

{{WorkInProgress}}







After performing the upgrade, the dhcp and dns server are 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 similer 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 />

During the upgrade libvirtd was installed. libvirtd uses dnsmasq for virtual machines. This caused a conflict. 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>