I can browse the HOME folder, but cant browse other shares

[schox]

You are a lifesaver kikkegek! - Thanks

I think I know what is going on.
...
so I manually reinstalled greyhole:

Code: Select all

rpm -q hda-greyhole rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm

...
and all shares are back again.
...
AMAHI ROCKS!

[kikkegek]

thats what this great forum if for. To help each other. Glad it helped you!

[bigfoot65]

I upgraded Greyhole to the latest recently and had the same problem. I did my update via yum.

Code: Select all

yum update https://github.com/downloads/gboudreau/Greyhole/greyhole-0.9.20-1.x86_64.rpm --nogpgcheck

then had to run again as reinstall to get the shares back:

Code: Select all

yum reinstall https://github.com/downloads/gboudreau/Greyhole/greyhole-0.9.20-1.x86_64.rpm --nogpgcheck

After that, all is well.

[ccondrup]

Seems this is becoming a common issue.
Just want to mention that so far the Greyhole developer hasn't received what he needs to debug this.
He asked for the console output when updating Greyhole (the output from running the RPM script and YUM, so not whats in yum.log)
So next time you're going to update Greyhole, please copy the console output and keep it in case this error occurs, so we can hopefully find the issue at hand.

[ciscoh]

I am thinking of updating Greyhole...if i do, i will be sure to capture that in case i run into the same issue.

[bigfoot65]

Funny thing is when I looked at the logs, I did not see any problems. It must be something that does not reflect as an error, but occurs over time. I installed the update, and my shares were fine on my client for a while. Then over a matter of hours, the shares became unavailable.

I am sure its something simple to fix, just finding the cause is the hard part some times.

[laptopfreek0]

Just thought I should mention that I as well had this problem. It happened when I added another drive to my greyhole.
Here is the console Reinstall of greyhole.

Code: Select all

yum -y install greyhole Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package greyhole.x86_64 0:0.9.22-1 set to be installed --> Finished Dependency Resolution Dependencies Resolved =============================================================================== Package Arch Version Repository Size =============================================================================== Installing: greyhole x86_64 0.9.22-1 greyhole 99 k Transaction Summary =============================================================================== Install 1 Package(s) Total download size: 99 k Installed size: 367 k Downloading Packages: greyhole-0.9.22-1.x86_64.rpm | 99 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : greyhole-0.9.22-1.x86_64 1/1 Executing post-install script... Found LIB_DIR = /usr/lib64 Detected Samba 3.5; creating symlink pointing to greyhole-samba35.so Post-install script completed. =========================================================================== See /usr/share/greyhole/USAGE to learn how to configure and start Greyhole. =========================================================================== Installed: greyhole.x86_64 0:0.9.22-1 Complete! [root@Amahi log]# ls -l /usr/lib64/samba/vfs/gre* lrwxrwxrwx 1 root root 39 Apr 27 17:46 /usr/lib64/samba/vfs/greyhole.so -> /usr/lib64/greyhole/greyhole-samba35.so

[bigfoot65]

Yes this is a known issue. It has been documented in the wiki and bug tracker.

[ Post made via Android ]

[schox]

Merry Christmas folks!

"This" is a recurring problem - and Now I´m not able to fix it good.

I´ve reistalled by both methods described here (rpm and yum) but to no avail - did a reboot in between also, and a uninstall both methods.

Greyhole is now installed via RPM method and trying to start the service give this result.

Code: Select all

# service greyhole start Starting Greyhole ... Usage: /etc/init.d/greyhole {start|stop|status|condrestart|restart} [FAILED]

While starting it as a Daemon "works" (# greyhole -D) - but is not a good solution.

Greyhole log give no reason for it to stop (...sleeping)

EDIT: Solved it (I hope) - was related to this : viewtopic.php?f=39&t=4475 )

[bigfoot65]

Unfortunately sometimes a bug creeps into code. Glad it appears to be fixed.