Greyhole troubleshooting

2010-12-25T00:28:24Z

Talk:Fedora 14 network install

2010-12-07T11:00:04Z

Gboudreau: Created page with "Yo. This could all be packaged as an Amahi app. But then, using Amahi to install another Amahi might have limited usefulness..."

Yo. This could all be packaged as an Amahi app.
But then, using Amahi to install another Amahi might have limited usefulness...

Greyhole

2010-12-02T00:04:15Z

Gboudreau:

Mount Shares Locally

2010-11-29T10:47:57Z

Gboudreau:

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

* Add each share you want to mount locally to your /etc/fstab, like this:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
#smb#//127.0.0.1/<share_name> /mnt/samba/<share_name> cifs credentials=/home/<username>/.smb_credentials,uid=500,gid=100,file_mode=0660,dir_mode=0770,hard,_netdev 0 0
</div>

You'll need to replace ''<share_name>'' with the actual share name.<br/>
And ''<username>'' with your username. That user will own all the files in the mounted shares, though all users that are part of the ''users'' group (gid=100) will also be able to write in those mounted shares.

* Create the ''/home/<username>/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=<your_username>
password=<your_password>
domain=HOME
</div>

* Manually create the /mnt/samba/<share_name> directory.

* Finally, add the following lines in /etc/rc.local:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
# Mount own Samba shares locally
/bin/sed -ie 's/#smb#//g' /etc/fstab
/bin/mount -a
/bin/sed -ie 's@//127.0.0.1@#smb#//127.0.0.1@g' /etc/fstab
</div>

To test your new mounts, you can execute the commands you added in rc.local.<br/>
rc.local is executed on boot, after all other services have been started.<br/>
This is necessary because mounts found in fstab are mounted before the Samba service starts, so just having your shares in fstab is not enough. The commands added in rc.local will un-comment your share lines from fstab, then mount them all, then re-comment them again, so that when fstab is executed on boot, it doesn't give you errors about those shares not being available.

Mount Shares Locally

2010-11-29T10:45:14Z

Gboudreau: Created page with "Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed thr..."

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

* Add each share you want to mount locally to your /etc/fstab, like this:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
#smb#//127.0.0.1/<share_name> /mnt/samba/<share_name> cifs credentials=/home/<username>/.smb_credentials,uid=500,gid=100,file_mode=0660,dir_mode=0770,hard,_netdev 0 0
</div>
You'll need to replace ''<share_name>'' with the actual share name.<br/>
And ''<username>'' with your username. That user will own all the files in the mounted shares, though all users that are part of the ''users'' group (gid=100) will also be able to write in those mounted shares.

* Create the ''/home/<username>/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=<your_username>
password=<your_password>
domain=HOME
</div>

* Manually create the /mnt/samba/<share_name> directory.

* Finally, add the following lines in /etc/rc.local:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
# Mount own Samba shares locally
/bin/sed -ie 's/#smb#//g' /etc/fstab
/bin/mount -a
/bin/sed -ie 's@//127.0.0.1@#smb#//127.0.0.1@g' /etc/fstab
</div>

To test your new mounts, you can execute the commands you added in rc.local.<br/>
rc.local is executed on boot, after all other services have been started.<br/>
This is necessary because mounts found in fstab are mounted before the Samba service starts, so just having your shares in fstab is not enough. The commands added in rc.local will un-comment your share lines from fstab, then mount them all, then re-comment them again, so that when fstab is executed on boot, it doesn't give you errors about those shares not being available.

2010-08-23T11:35:11Z

Gboudreau:

[[Category:apps]]
== What is Greyhole ==

A new feature in Amahi is [[Storage pooling]] using [http://greyhole.pommepause.com/ Greyhole].

This feature is installed by default, but requires a few simple steps to begin utilizing the features.

You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].

To add a drive to your Greyhole storage pool. First open your dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.

== Important Warnings ==
<div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard.<br/>
You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').

Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.

We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].
</div><br/><br/>

== First things first ==

You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/>
Without Advanced Settings enabled, you won't see the following page and options.

== For Storage Pool (Partitions) ==

[[File:Storage_Pool_1.png|600px|thumb|left]]

Select the drives you want available for your storage pool.

== Greyhole options ==

The next step is to select the share you want to replicate across the pool.

From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.

[[File:Greyhole_Options_1.png|600px|thumb|left]]

Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.

Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.

== Greyhole advanced options ==

You can further configure Greyhole by manually editing the following file:<br/>
'''/var/hda/platform/html/config/greyhole.yml'''

To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.

greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/>
Here's an example of how those should appear:

To specify the following to Greyhole in greyhole.conf:

sticky_files = Music/
sticky_files = Videos/Movies/
stick_into = /mnt/hdd1/gh
stick_into = /mnt/hdd5/gh
sticky_files = Backups/CrashPlan/
stick_into = /mnt/hdd0/gh

one should specify this in the greyhole.yml file, where '''precise indentation matters''':

sticky_files:
- - Music/
- - Videos/Movies/
- - /mnt/hdd1/gh
- /mnt/hdd5/gh
- - Backups/CrashPlan/
- - /mnt/hdd0/gh

For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.

== Copying you data into Greyhole shares the first time ==

When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.

Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/>
The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.

Once way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.
This can be time consuming, but it is the safest way to use Greyhole.

Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.

Here's a more detailed walkthrough for this method:

# Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.
# Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.
# Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''
# Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.
# Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck
# Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.
# Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).
# Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name
# Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).
# If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''

You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.

== /media ==
Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/>
Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/>
This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.

Follow [[Adding a second hard drive to your HDA|this guide]] to permanently mount your drives, before you include them in your storage pool.

File:Colorus-Amahi-Theme.png

2010-08-12T00:12:17Z

Gboudreau:

User talk:Gboudreau

2010-08-04T21:38:32Z

Gboudreau:

Vote for one (or two, or three):

Which of those should become an Amahi theme ?

* [http://www.opendesigns.org/od/wp-content/designs/1/1633/?KeepThis=true& 1633] -- 1 vote
* [http://www.opendesigns.org/od/wp-content/designs/1/1117/?KeepThis=true& 1117] -- 2 votes
* [http://www.opendesigns.org/od/wp-content/designs/1/1182/?KeepThis=true& 1182]
* [http://www.opendesigns.org/od/wp-content/designs/1/1249/?KeepThis=true& 1249] -- 4 votes DONE: http://www.amahi.org/apps/colorus-theme
* [http://www.opendesigns.org/od/wp-content/designs/1/1537/?KeepThis=true& 1537] -- 3 votes
* [http://www.opendesigns.org/od/wp-content/designs/0/859/?KeepThis=true& 859]
* [http://www.opendesigns.org/od/wp-content/designs/0/904/?KeepThis=true& 904] -- 2 votes
* [http://www.opendesigns.org/od/wp-content/designs/0/962/?KeepThis=true& 962] -- 2 votes
* [http://www.opendesigns.org/od/wp-content/designs/0/771/?KeepThis=true& 771]

File:Colorus-Theme-sshot.png

2010-08-04T19:55:00Z

Gboudreau: uploaded a new version of "File:Colorus-Theme-sshot.png"

File:Colorus-theme-thumb.png

2010-08-04T19:54:48Z

Gboudreau:

2010-08-03T17:32:01Z

Gboudreau:

For installation notes, etc. see [[SP notes]].

When you note a problem, please indicate what version you're running (0.2, 0.3, ...)

= Warboard =

* VPN works. the date needs to be set to something recent:
date --set 'Thu May 27 16:44:57 EDT 2010'
hwclock --systohc --utc
* tar and unzip need to be in the image:
yum -y install tar unzip
* Greyhole *is* working
* crontab does not appear to be working
* had to add with noatime in / to prevent flash burnout
* should control monit - it keeps on pounding the flash with messages in /var/log/monit
* would like to add swap to flash based drives
* mt-daapd and amahi-transmission are dying
* ntpd is not installed??
[root@fedora-arm ~]# date
Sun Apr 30 06:57:12 EDT 2000

= OpenVPN =

<small>
# service openvpn start
Starting openvpn: FATAL: Module ip_tables not found.
iptables v1.4.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Module ip_tables not found.
iptables v1.4.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
FATAL: Module ip_tables not found.
iptables v1.4.5: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
[FAILED]
</small>

= Fixed =

* local DNS server is not working for external hostnames (caused by dnssec enabled in named.conf). Workaround
echo -e 'DNSSEC="off"\nDLV="off"' > /etc/sysconfig/dnssec
service named restart

= Commands not found =
* which: command not found
* man: command not found
* scp: command not found
* make: command not found

To install those:
yum -y install which man openssh-clients make