==Gathering Good Troubleshooting Information==
When reporting an issue with Greyhole, or asking for help regarding Greyhole, you should provide the following. You'll need to execute the given commands as root.
7. If you have issues with a particular file (file disappeared, is wrong size, has wrong filename), execute the following to find out what Greyhole did with this file:
greyhole --debug filename
==Clearing The Greyhole Work Queue==
I've not seen too many other reports of this occuring on the internet, so I suspect it's something that may be specific to my setup. However, the fix is pretty general, so I'm documenting it here for others to use.
Sometimes, greyhole will have too many tasks queued, and will lock up, leaving you with a full landing zone and an fsck queue that just isn't processing. Always leave your server overnight (or longer, depending on the size of your landing zone (overnight should be sufficient for most) to ensure that its not just taking a while to process, but if its really, definitely stuck, you may want to follow these instructions to clear the queue.
#Stop the greyhole daemon
##<pre>sudo service greyhole stop</pre>
#Connect to the MYSQL engine
##<pre>mysql -u greyhole -pgreyhole</pre>
###Select the Greyhole database
####<pre>USE greyhole;</pre>
###Drop and Recreate the 'Tasks' table with the same structure
####<pre>TRUNCATE TABLE tasks;</pre>
###Exit the MYSQL engine
####<pre>exit;</pre>
#Restart the greyhole daemon
##<pre>sudo service greyhole start</pre>
#Schedule an fsck to clear out the files currently in the landing zone
##<pre>sudo greyhole --fsck</pre>
Back to the [[Greyhole]] page