Greyhole on Amahi 7

[bigfoot65]

Not sure why there is an issue, but this should resolve it.

As root user, edit /etc/greyhole.conf. Change the db_user and db_password to greyhole. Save and restart Greyhole. That should fix the issue.

[whaites]

That did fix the mysql error. I'm not sure that greyhole is running for me though.

I've issued command: service greyhole start
but when I do: greyhole --stats, the drives are all listed as offline
when I do: greyhole --status, it tells me the greyhole daemon is currently stopped
when I do: greyhole --daemon - it seems to just hang, the cursor returns on a blank line, no prompt

Do I need to do something else to start greyhole?

[bigfoot65]

You have to add the drives and such to the config file or it will not do anything. There is some guidance in the wiki, but this is something more for advanced users in Amahi 7.

If you want simple Greyhole configuration, you would want to use Ubuntu Amahi 6.3 vs Fedora 19 Amahi 7.

[whaites]

I guess this should have been obvious. I had /var/hda/files/drives/drive2/gh as my storage_pool entry, but folder gh did not exist. I though greyhole would make this. I added it and now I see stats and view-queue shows items.

I have my greyhole configured to copy to 3 drives for the share I am writing to. So far, I can only find files in drive2, my landing zone drive. Did I need to make all my share folders on drive1 and drive3 manually as well?

[bigfoot65]

I presume you have added all the drives to the greyhole.conf file. Also if you have not done so, do greyhole -f and that should get things moving.

If that does not help, check out the comments in the greyhole.conf file. They usually help with configuration options.

[sgtfoo]

While we have a thread here for greyhole and Amahi 7, I'd like to chime in for anyone using Amahi in a virtual setup....
I would suggest avoiding greyhole in a virtual setup UNLESS you have drives to spare in the machine to use exclusively.

(story)
I say this because I recently spent hours trying to pull all my data from the gh folders of 2 drives I used to have for greyhole and now I've decided to move all the data to LVM shared data space in my proxmox system. I can tell that since the last propagation of data which should have been done by a 'greyhole -f' (which would have been months ago, as my F14 HDA has been off for about 6 months) , there is data missing at least until I scour my old LZ drive for remnants.
If anyone has any questions on the process, I could write a new thread or answer here or in the virtualization section.

[bigfoot65]

I would be interested in hearing more. I am currently using Greyhole with Proxmox and have 3 drives I use. My LZ is virtual, but all others are physical. Is this the setup you had problems with recently?

I am contemplating a move from Proxmox to something else since they are going commercial. I have been looking for a viable alternative, but so far Virtualbox running on Ubuntu is the only thing that seems reasonable. I like having the web interface and phpVirtualbox has come a long way in the past year.

Any thoughts?

[sgtfoo]

Yea that's the setup I had that I was getting trouble with... but only as I wanted to simplify it and expand my available storage for my other VMs.

as for the rest of my input, I put it in here...

viewtopic.php?f=41&t=3895&p=26674#p26674

I may be somewhat partial, but it's because the pros outweigh the cons.

[whaites]

Sorry to bring this thread back to my troubles getting greyhole running. I have run greyhole --fsck multiple times, but it never seems to do anything. My queue stays at 5 items in one share to write. the log show every command issues the same error, which I've seen earlier in this thread. It seemed like a warning, but maybe it is preventing greyhole from running:

Sep 06 19:45:19 4 view-queue: PHP Unknown Error [8192]: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /usr/bin/ greyhole on line 435

[bigfoot65]

This may fix your problem.
https://bugs.amahi.org/issues/1095