Greyhole updating

From Amahi Wiki
Jump to: navigation, search

Disclaimer

Amahi releases new versions of Greyhole (GH) after they've been tested. Official Greyhole for Amahi on Fedora 14: 0.9.2

If you follow this guide to update your GH install manually you do so on your own risk. If it breaks, it's on you. All the steps below should be executed as root.

Option 1 - Use the Greyhole YUM repository

1. If you didn't already, add the Greyhole YUM repository to your YUM configuration.

bash code
​curl -o /etc/yum.repos.d/greyhole.repo http://www.greyhole.net/releases/rpm/greyhole.repo.disabled​


2. If you want to use this repository every time yum is used (including for Amahi automatic updates), change /etc/yum.repos.d/greyhole.repo from:

Text
​enabled=0​

to

Text
​enabled=1​

NOTE: You can safely skip this step if you want to manually update in the future.

3. Update hda-greyhole to the latest version:

bash code
​yum --enablerepo=greyhole update hda-greyhole​


Fedora Option 2 - Manually install the latest RPM

1. Find current version:

bash code
​rpm -q hda-greyhole​


2. Is there a new version?

http://www.greyhole.net/download/

3. Browse the archive and copy the link for the latest hda-greyhole (Amahi needs hda-greyhole, the regular greyhole will conflict)

http://www.greyhole.net/download/archives.html

4. Back to terminal, make sure you are root (su). Example update command:

bash code
​rpm -Uvh http://www.greyhole.net/releases/rpm/`uname -i`/hda-greyhole-0.9.13-1.`uname -i`.rpm​


5. Check the GH log for any errors that might have occurred after the upgrade

bash code
​tail -f /var/log/greyhole.log​


6. Re-check the version of your newly updated Greyhole install, and enjoy!

bash code
​rpm -q hda-greyhole​


Fedora Troubleshooting

Can't access your shares after you upgraded ? Try to re-install the same RPM a second time. Sometimes, the script included in the RPM can't create the Greyhole module for Samba where it should, and this will cause your Greyhole pooled shares to become unaccessible. Re-installing the same RPM a second time always fix that issue. Use the following command to reinstall the currently installed RPM:

bash code
​rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm​


Use the following command to verify that the Samba symlink was indeed created:

bash code
​ls -l /usr/lib*/samba/vfs/greyhole.so​


Ubuntu Option 1 - Use the Greyhole APT repository

If you didn't already, add the Greyhole APT repository to your APT configuration.

bash code
​sudo sh -c 'echo "deb http://www.greyhole.net/releases/deb stable main" > /etc/apt/sources.list.d/greyhole.list' curl -s http://www.greyhole.net/releases/deb/greyhole-debsig.asc | sudo apt-key add - sudo apt-get update​


Ubuntu Option 2 - Manually install the latest DEB

1. Find current version:

bash code
​sudo greyhole​


2. Is there a new version? Browse the archive and copy the link for the latest greyhole.

http://www.greyhole.net/releases/deb/

3. Back to terminal, make sure you execute as root (sudo). Example update command:

bash code
​wget http://www.greyhole.net/releases/deb/greyhole-0.9.26-4.amd64.deb sudo dpkg -i greyhole-0.9.26-4.amd64.deb​


4. Check the GH log for any errors that might have occurred after the upgrade

bash code
​tail -f /var/log/greyhole.log​


5. Re-check the version of your newly updated Greyhole install, and enjoy!

bash code
​sudo greyhole​