SOLVED: Loss of access to samba shares

[dannyoleson]

Hello there -
I searched linux forums and this forum for an answer, but I haven't found anything that seems applicable to my situation yet, so I'm hoping someone here will be able to help.

I had to rebuild my Amahi installation recently, and just went through the long process of reconnecting my drive pool and landing zone, which was long and arduous. Finally, after everything settled down, I started installing some of the applications I ran on my old Amahi install, like Disk Stats, Owncloud8 and webmin. After installing those, I noticed that my shares were suddenly inaccessible. I've rebooted the server, all network equipment, and the windows 8.1 I'm trying to access from (though note that other clients on the network are similarly unable to access the shares. Looking at the Samba error log, I see this -
[2015/08/15 10:24:47, 0] ../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)
find_domain_master_name_query_fail:
Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Unable to sync browse lists in this workgroup.

I've been defeated thus far in troubleshooting. Anyone have any idea what may be going on?

Thanks!

[bigfoot65]

There are a few things to check here.

1. Is Samba running?

2. Did you recreate the shares exactly as they were in the previous installation. Capitalization is important. Most shares are all lower case in the file system, but Sentence Case in Samba.

This is the first place I would start looking. Greyhole will reflect the Samba name for shares vs the file system as it must be for /var/hda/files.

[dannyoleson]

You are so awesome at replying quickly. I really really appreciate that.

One very critical step I forgot to do was run yum update, which is a silly thing to forget. I don't why it worked fine until I started installing other applications, but I'm guessing some application updated a dependency or something and broke the version of samba (or a related service) that I was running.

In any event, all is well. Sorry for the false alarm.

[bigfoot65]

No problem.

Glad it's all sorted out now.

[dannyoleson]

OK shoot - I spoke too soon. The shares came back under \\hda, but I can't access them. Greyhole logs show the following error -
Aug 15 13:15:24 DEBUG daemon: Checking symlink at /usr/lib64/samba/vfs/greyhole.so...
Aug 15 13:15:24 WARN daemon: PHP Warning [2]: is_file(): open_basedir restriction in effect. File(/usr/lib64/samba/vfs/greyhole.so) is not within the allowed path(s): (/) in /usr/bin/greyhole on line 4569; BT: greyhole[L3286] run() => greyhole[L3258] initialize() => greyhole[L3275] samba_check_vfs() => greyhole[L4569] is_file(/usr/lib64/samba/vfs/greyhole.so)
Aug 15 13:15:24 WARN daemon: Greyhole VFS module for Samba was missing, or the wrong version for your Samba. It will now be replaced with a symlink to /usr/lib64/greyhole/greyhole-samba40.so
Aug 15 13:15:24 WARN daemon: PHP Warning [2]: is_file(): open_basedir restriction in effect. File(/usr/lib64/samba/vfs/greyhole.so) is not within the allowed path(s): (/) in /usr/bin/greyhole on line 4579; BT: greyhole[L3286] run() => greyhole[L3258] initialize() => greyhole[L3275] samba_check_vfs() => greyhole[L4579] is_file(/usr/lib64/samba/vfs/greyhole.so)
Aug 15 13:15:24 WARN daemon: PHP Warning [2]: symlink(): No such file or directory in /usr/bin/greyhole on line 1497; BT: greyhole[L3286] run() => greyhole[L3258] initialize() => greyhole[L3275] samba_check_vfs() => greyhole[L4582] gh_symlink(/usr/lib64/greyhole/greyhole-samba40.so,/usr/lib64/samba/vfs/greyhole.so) => greyhole[L1497] symlink(/usr/lib64/greyhole/greyhole-samba40.so,/usr/lib64/samba/vfs/greyhole.so)
Aug 15 13:15:24 WARN daemon: PHP Warning [2]: is_file(): open_basedir restriction in effect. File(/usr/lib64/samba/vfs/greyhole.so) is not within the allowed path(s): (/) in /usr/bin/greyhole on line 1583; BT: greyhole[L3286] run() => greyhole[L3258] initialize() => greyhole[L3275] samba_check_vfs() => greyhole[L4582] gh_symlink(/usr/lib64/greyhole/greyhole-samba40.so,/usr/lib64/samba/vfs/greyhole.so) => greyhole[L1500] gh_is_file(/usr/lib64/samba/vfs/greyhole.so) => greyhole[L1583] is_file(/usr/lib64/samba/vfs/greyhole.so)
Aug 15 13:15:24 INFO daemon: The Samba daemon will now restart...

Any thoughts?

[bigfoot65]

Did you reboot after the OS updates?

Often there is a kernel update and it requires reboot.

This is a different issue from your initial post.

[dannyoleson]

I did reboot. Should I start a new thread since this is a different issue?

[dannyoleson]

when I ls in /usr/lib64/samba/vfs/, i see that greyhole.so is red, which google searches indicate means it's an archived file. Can I simply unarchive the file or something?

[bigfoot65]

A new thread would be best.

However this may fix it.

As root user do:

Code: Select all

yum reinstall amahi-greyhole

[dannyoleson]

You are a wizard. Thank you!