Greyhole Service Failing to Start

[dmserver]

Hi,
I know it's my 1st post but I've been silent member for just over a month. As with all good forums you will generally find someone has had a similar issue before so I have been utilising previous posts rather than creating my own (until now)
For any other newbie reading this....use the search button, it finds some very useful information.

Anyways.....I'm having a bit of an issue as Greyhole is failing to start.
I'm reasonably new to linux but thought I had got to grips with it until I was installing a 1tb USB Drive.
No matter what I do I cannot get it to mount properly, even though windows can read and reformat it without issue, and chkdsk /f reports no errors. MBR's been wiped in testdisk but both gparted and cfdisk (as root) fail to create partitions or format it properly. Anyway that is another story as I have removed it from my HDA.....
However, whilst I was messing about I noticed that the Greyhole service was not starting. I had made changes to /etc/fstab but have got that back to load the correct mounts (AFAIK)
I can still access all my files from a networked PC (phew) but I am getting errors in the greyhole.log

Feb 5 05:07:18 4 parse_logs: PHP Warning [2]: fopen(/var/log/messages): failed to open stream: Value too large for defined data type in /usr/bin/greyhole on line 2106
Feb 5 05:07:18 2 parse_logs: Can't open Samba log file '/var/log/messages' for reading.

The whole troubleshooting info is below but I can see the above lines are where it's reporting an error but I have no idea how to fix that.
I can see that two partitions are reporting back as not having valid tables, so I am not sure if that is having any effect. I followed a guide on these forums when I was installing Fed so thought partitions and formats were correct (can't remember exactly which guide)

UPDATE : I have now read and understood that these invalid partitions are not a problem
From http://www.linuxquestions.org

Those are device mapper devices. They usually are associated with LVM and correspond to the logical volumes

When the programs fdisk and sfdisk are run with the option -l and no argument, e.g.
# /sbin/fdisk -l
they look for all devices that can have cylinders, heads, sectors, etc.
If they find such a device, they output that information to standard
output and they output the partition table to standard output. If there is
no partition table, they have an error message (also standard output).
One can see this by piping to 'less', e.g.
# /sbin/fdisk -l | less
the error messages disappear

Any help would be appreciated, undoubtedly I have caused something to mess up but I can't work out what


Regards
Donald



1. What version of Fedora, Samba & Greyhole are you running?
2.6.31.5-127.fc12.i686.PAE
samba-3.4.2-47.fc12.i686
hda-greyhole-0.7.5-1.i386
2. The content of the /etc/samba/smb.conf & /etc/greyhole.conf files (provide paste URLs):
http://fpaste.org/Eswr/
http://fpaste.org/eI1q/

3. The result of the following commands:
/dev/mapper/vg_server-root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/sda3 on /var/hda/files type ext4 (rw)
/dev/sdc1 on /var/hda/files/drives/drive3 type ext4 (rw)
/dev/sdb1 on /var/hda/files/drives/drive1 type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
//127.0.0.1/Apps on /mnt/samba/Apps type cifs (rw,mand)
//127.0.0.1/Books on /mnt/samba/Books type cifs (rw,mand)
//127.0.0.1/Docs on /mnt/samba/Docs type cifs (rw,mand)
//127.0.0.1/Games on /mnt/samba/Games type cifs (rw,mand)
//127.0.0.1/Movies on /mnt/samba/Movies type cifs (rw,mand)
//127.0.0.1/Music on /mnt/samba/Music type cifs (rw,mand)
//127.0.0.1/Pictures on /mnt/samba/Pictures type cifs (rw,mand)
//127.0.0.1/Torrents on /mnt/samba/Torrents type cifs (rw,mand)
funionfs on /var/hda/apps/ushare/files type fuse.funionfs (rw,nosuid,nodev,allow_other)
gvfs-fuse-daemon on /home/donald/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=donald)

Disk /dev/sda: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b5573

Device Boot Start End Blocks Id System
/dev/sda1 * 1 26 204800 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 26 3850 30720000 8e Linux LVM
/dev/sda3 3850 24792 168216908+ 83 Linux

Disk /dev/sdc: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x006c5f87

Device Boot Start End Blocks Id System
/dev/sdc1 1 30516 245115904 83 Linux

Disk /dev/sdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x01b301b2

Device Boot Start End Blocks Id System
/dev/sdb1 1 24793 199147520 83 Linux

Disk /dev/dm-0: 25.2 GB, 25161629696 bytes
255 heads, 63 sectors/track, 3059 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 6291 MB, 6291456000 bytes
255 heads, 63 sectors/track, 764 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_server-root
24G 6.5G 16G 30% /
tmpfs 1.5G 176K 1.5G 1% /dev/shm
/dev/sda1 194M 22M 163M 12% /boot
/dev/sda3 158G 146G 4.2G 98% /var/hda/files
/dev/sdc1 231G 5.5G 213G 3% /var/hda/files/drives/drive3
/dev/sdb1 187G 169G 9.0G 95% /var/hda/files/drives/drive1
//127.0.0.1/Apps 575G 349G 227G 61% /mnt/samba/Apps
//127.0.0.1/Books 575G 349G 227G 61% /mnt/samba/Books
//127.0.0.1/Docs 575G 349G 227G 61% /mnt/samba/Docs
//127.0.0.1/Games 575G 349G 227G 61% /mnt/samba/Games
//127.0.0.1/Movies 575G 349G 227G 61% /mnt/samba/Movies
//127.0.0.1/Music 575G 349G 227G 61% /mnt/samba/Music
//127.0.0.1/Pictures 575G 349G 227G 61% /mnt/samba/Pictures
//127.0.0.1/Torrents 158G 154G 4.2G 98% /mnt/samba/Torrents
funionfs 158G 146G 4.2G 98% /var/hda/apps/ushare/files

Greyhole Statistics
===================

Storage Pool
Total - Used = Free + Attic = Possible
/var/hda/files/gh: 158G - 146G = 4G + 0G = 4G
/var/hda/files/drives/drive1/gh: 187G - 168G = 9G + 0G = 9G
/var/hda/files/drives/drive3/gh: 230G - 5G = 213G + 0G = 213G


4. The list drives in your storage pool (per Amahi platform):
+----+------------------------------+--------------+---------------------+---------------------+
| id | path | minimum_free | created_at | updated_at |
+----+------------------------------+--------------+---------------------+---------------------+
| 1 | /var/hda/files | 10 | 2011-01-28 13:33:12 | 2011-01-28 13:33:12 |
| 2 | /var/hda/files/drives/drive1 | 10 | 2011-01-28 13:33:13 | 2011-01-28 13:33:13 |
| 3 | /var/hda/files/drives/drive3 | 10 | 2011-01-31 16:18:41 | 2011-01-31 16:18:41 |
+----+------------------------------+--------------+---------------------+---------------------+

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):
http://fpaste.org/GfhT/

6. The Greyhole work queue:
Greyhole Work Queue Statistics
==============================

This table gives you the number of pending operations queued for the Greyhole daemon, per share.

Write Delete Rename
Apps 0 0 0
Books 0 0 0
Docs 0 0 0
Games 0 0 0
Movies 0 0 0
Music 0 0 0
Pictures 0 0 0
========
Total 0 + 0 + 0 = 0

tail /var/log/greyhole.log
Feb 5 05:07:18 6 daemon: Greyhole (version 0.7.5) daemon started.
Feb 5 05:07:18 7 daemon: Loading graveyard backup directories...
Feb 5 05:07:18 7 daemon: Found 2 directories in the settings table.
Feb 5 05:07:18 4 parse_logs: PHP Warning [2]: fopen(/var/log/messages): failed to open stream: Value too large for defined data type in /usr/bin/greyhole on line 2106
Feb 5 05:07:18 2 parse_logs: Can't open Samba log file '/var/log/messages' for reading.
Feb 5 05:08:18 6 daemon: Greyhole (version 0.7.5) daemon started.
Feb 5 05:08:18 7 daemon: Loading graveyard backup directories...
Feb 5 05:08:18 7 daemon: Found 2 directories in the settings table.
Feb 5 05:08:18 4 parse_logs: PHP Warning [2]: fopen(/var/log/messages): failed to open stream: Value too large for defined data type in /usr/bin/greyhole on line 2106
Feb 5 05:08:18 2 parse_logs: Can't open Samba log file '/var/log/messages' for reading.

[dmserver]

OK, I seem to have got it sorted (hopefully)

I got up this morning and tried to think with a fresh head.
I realised that my /var/log/messages was 3.7 Gig !!!!!!!!!!
so I thought...'That's maybe why it can't read it"
so I cleared it using cat /dev/null > /var/log/messages

refreshed my HDA > Settings > Servers screen and Greyhole was already running again.

There has been a flurry of activity from Greyhole and the greyhole.log is now showing things like
Feb 5 13:55:53 7 fsck: Moved copy from /var/hda/files/gh/Pictures/from phone/IMAG0012.jpg to attic: /var/hda/files/gh/.gh_attic/Pictures/from phone/IMAG0012.jpg
Feb 5 13:55:53 7 fsck: Updating symlink at /var/hda/files/pictures/from phone/IMAG0012.jpg to point to /var/hda/files/drives/drive1/gh/Pictures/from phone/IMAG0012.jpg
Feb 5 13:55:53 7 fsck: Saving 2 tombstones for Pictures/from phone/IMAG0012.jpg

so it seems to be tidying EVERYTHING up (hopefully this is good although it keeps finding more copies than it expected to)


Looks like I need to get an understanding of logrotate to clear of old logs.
I know I've been tough on this box whilst I have been trying to learn the ins and outs of linux/Fedora/Amahi, but that is a whopping size of log file for any system

[gboudreau]

If you install the latest version of Greyhole manually, you'll get a version that does not use this log anymore, and thus this situation won't be a problem.

Code: Select all

rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.8.99-1.`uname -i`.rpm

[NeverSimple]

OK, I seem to have got it sorted (hopefully)

Great, but:

Code: Select all

samba-3.4.2-47.fc12.i686 hda-greyhole-0.7.5-1.i386

you are running old versions of Samba and especially Greyhole; current is 0.8.4 which fixed a lot of bugs. The update SHOULD be automagically, but obviously it isn't . You probably should fix that.

I read elsewhere on this forum that Carlos (cpg) said that the latest greyhole version for Amahi 5 (FC12) is 0.7.5. That seems strange to me, because I'm running 0.8.3. You probably can use the 'search' function again......

Richard

EDIT: It seems that Guillaume was a bit quicker...

[dmserver]

Thanks Guys

I followed Guillaume's command and rightly got this message

[root@server ~]# rpm -Uvh http://www.greyhole.net/releases/hda-gr ... 9-1.`uname -i`.rpm
Retrieving http://www.greyhole.net/releases/hda-gr ... 1.i386.rpm
error: Failed dependencies:
samba >= 3.4.3 is needed by hda-greyhole-0.8.99-1.i386


so I ran 'yum update samba' and that went fine as did the greyhole update after that

I was then however getting these message in greyhole.log

Feb 05 14:51:10 4 daemon: PHP Warning [8]: Undefined property: stdClass::$host in /usr/bin/greyhole on line 521
Feb 05 14:51:10 4 daemon: PHP Warning [8]: Undefined property: stdClass::$user in /usr/bin/greyhole on line 521
Feb 05 14:51:10 4 daemon: PHP Warning [8]: Undefined property: stdClass::$pass in /usr/bin/greyhole on line 521
Feb 05 14:51:10 4 daemon: PHP Warning [2]: mysql_connect(): Access denied for user 'root'@'localhost' (using password: NO) in /usr/bin/greyhole on line 521
Feb 05 14:51:10 2 daemon: Can't connect sqlite to database.


I remembered seeing the greyhole wiki mentioned sqlite so went back, checked that page and converted it to MySQL
That went OK and greyhole.log now has
Feb 05 14:56:56 6 daemon: Optimizing MySQL tables...
Feb 05 14:56:56 6 daemon: Greyhole (version 0.8.99) daemon started.
Feb 05 14:56:56 7 daemon: Loading graveyard backup directories...
Feb 05 14:56:56 7 daemon: Found 2 directories in the settings table.
Feb 05 14:56:56 7 parse_logs: Parsing Samba logs...
Feb 05 14:57:17 7 parse_logs: Done parsing.
Feb 05 14:57:17 7 simplify_tasks: Simplifying pending tasks.
Feb 05 14:57:17 7 simplify_tasks: Simplifying pending tasks.
Feb 05 14:57:17 7 fsck: Now working on task ID 187100: fsck /
Feb 05 14:57:17 6 fsck: Starting fsck for
Feb 05 14:57:17 7 fsck: Entering /var/hda/files/books
Feb 05 14:57:17 7 fsck: Entering /var/hda/files/pictures
Feb 05 14:57:17 7 fsck: Entering /var/hda/files/pictures/from phone


It's still churning through my files but that's more than likely down to it reorganising them after me messing about with drives


Regards,
Donald