Difference between revisions of "Greyhole troubleshooting"
(Added section headings, section on how to clear the greyhole queue) |
|||
Line 1: | Line 1: | ||
+ | ==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. | 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. | ||
Line 22: | Line 24: | ||
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: | 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 | 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 | Back to the [[Greyhole]] page |
Revision as of 09:04, 13 July 2012
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.
1. What version of Fedora, Samba & Greyhole are you running?
uname -r; rpm -q samba hda-greyhole
2. The content of the /etc/samba/smb.conf & /etc/greyhole.conf files (provide paste URLs):
yum -y install fpaste; fpaste /etc/samba/smb.conf; fpaste /etc/greyhole.conf
3. The result of the following commands:
mount; fdisk -l; df -h; greyhole --stats
4. The list drives in your storage pool (per Amahi platform):
mysql -u root -phda -e "select * from disk_pool_partitions" hda_production
5. A list of the directories on the root of the drives included in your storage pool, obtained with the following command (provide a paste URL):
mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la | fpaste
6. The Greyhole work queue:
greyhole --view-queue
If the above command returns nothing, execute tail /var/log/greyhole.log to see the problem.
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
sudo service greyhole stop
- Connect to the MYSQL engine
mysql -u greyhole -pgreyhole
- Select the Greyhole database
USE greyhole;
- Drop and Recreate the 'Tasks' table with the same structure
TRUNCATE TABLE tasks;
- Exit the MYSQL engine
exit;
- Select the Greyhole database
- Restart the greyhole daemon
sudo service greyhole start
- Schedule an fsck to clear out the files currently in the landing zone
sudo greyhole --fsck
Back to the Greyhole page