Description of problem: Last night our system auto updated to Samba v4.3.9-Ubuntu. Now our Samba VFS has stopped with the following error: [2016/05/05 11:19:39.483520, 0] ../lib/util/modules.c:48(load_module) Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so': /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0: version `SAMBA_4.3.8_UBUNTU' not found (required by /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so) Appears Samba-VFS-Module hasn't been updated yet to 4.3.9. Could this be updated? We've attempted to downgrade Samba on our nodes however this is what happens: http://paste.ubuntu.com/16231208/ See output of apt-cache showpkg samba here http://paste.ubuntu.com/16231215/ Version-Release number of selected component (if applicable): gluster --version glusterfs 3.7.10 built on Apr 1 2016 14:20:43 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. samba --version Version 4.3.9-Ubuntu How reproducible: Update Samba to 4.3.9 on Gluster 3.7.10 Then try to access and you will receive something along the lines of: Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so': /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0: version `SAMBA_4.3.8_UBUNTU' not found (required by /usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so) Also cannot just modify the glusterfs.so Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Samba share accessible on 4.3.9 Additional info:
Based on the discussion on irc changing the component to 'packaging' as https://launchpad.net/~monotek/+archive/ubuntu/samba-vfs-glusterfs-3.7 has not yet built for samba-4.3.9.
I'm on vacation and can't build new packages before next week. The solution would be to apt pin my packages. So they don't get overwritten by the standard samba packages without gluster support. If you use unattended updates you could also tell apt to not update samba automatically. Apt pin instructions can be found in my qemu ppa. Should work vise versa for samba packages, when you change it like this: Add /etc/apt/preferences.d/samba: Package: samba* Pin: release o=LP-PPA-monotek-samba-vfs-glusterfs-3.7 Pin-Priority: 1000
So will this help us with future updates that get released or is that going to fix it to use 4.3.8 now?
Both solutions (apt pin & exception for unattended upgrades) would help for all future releases.
Okay I'll look into the exception to try find how to apply it. Any idea of anything we can do now to have the Samba-VFS work again?
Downgrade to my 4.3.8 packages. Apt pin should do it for you.
Awesome, After adding this file, what do we need to do next?
RTM ;-) https://help.ubuntu.com/community/PinningHowto
Thanks Andre, All systems Functional Again :)
Just uploaded new packages to my ppa. Should be ready soon...