Bug #610

Greyhole not running because share wasn't removed from greyhole.conf

Added by gboudreau almost 12 years ago. Updated over 11 years ago.

Target version:
Start date:
Due date:
% Done:



My Greyhole hasn't running for quite a while, and I didn't know about it.
(Maybe something needs to be done about that... warn the user on the dashboard homepage or something...)

From /var/log/greyhole.log:, the following message is repeated over and over, every 10 minutes.

Aug 18 07:00:05 4 initialize: Found a share (media) defined in /etc/greyhole.conf with no path in /etc/samba/smb.conf. Either add this share in /etc/samba/smb.conf, or remove it from /etc/greyhole.conf, then restart Greyhole.

I removed that share from the dashboard. It should have been removed from both the smb.conf and greyhole.conf, but it seems it wasn't remove from greyhole.conf.
Both files have different last modified dates:

[gb@hda ~]$ ls la /etc/samba/smb.conf /etc/greyhole.conf
1 root root 1553 2010-08-15 18:42 /etc/greyhole.conf
rw-r--r- 1 root root 4845 2010-08-15 18:46 /etc/samba/smb.conf

media share is not in the DB anymore:
[gb@hda ~]$ mysql -uroot -phda -e 'select * from shares where comment like "media"' hda_production
[gb@hda ~]$

To fix it, I tried to edit a share path in the dashboard, and now both files last modified date are the same:

[gb@hda ~]$ ls la /etc/samba/smb.conf /etc/greyhole.conf
1 root root 1531 2010-08-18 07:07 /etc/greyhole.conf
rw-r--r- 1 root root 4839 2010-08-18 07:07 /etc/samba/smb.conf

And media is not in greyhole.conf anymore.

It seems production.log doesn't contain log from 3 days back (I think it should keep at least a week, logrotated), so I can't look there to look for issues or detail what I did exactly. But I remember I just deleted the share...


#1 Updated by gboudreau almost 12 years ago

It seems greyhole wasn't restarted either when the share disappeared, because those appeared in greyhole.log:
Aug 15 19:00:55 7 rename: Share "media" landing zone "/var/hda/files/media" doesn't exist anymore. Will not process this task until it re-appears...

This means the share was removed, and Greyhole wasn't restarted. When it was restarted (by Greyhole's own cron.d), then it stopped running completely, because the media share specified in greyhole.conf was gone from smb.conf.

#2 Updated by Anonymous over 11 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset commit:"afe2567cec9c58733655109a34ecb56852d39083".

Also available in: Atom