Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[Samba] Samba4 fails to work following upgrade - library version errors
152 views
Skip to first unread message
Graeme Porter
Apr 3, 2013, 12:06:31 PM4/3/13
to
Hello,
I was running Samba4 for a while on my Raspberry Pi (Raspbian distro, running 3.6.11+ #371 PREEMPT armv6l kernel). The version of Samba I was running was 4.1.0pre1-GIT-fd8b258.
Last night I decided to try to upgrade to see if I could upgrade it without breaking it.
Note that the AD this Pi is the DC for doesn't have any physical clients as members; I was using a Virtual PC running WinXP and another running Ubuntu just to test it out - so technically there's no great loss if it did break - but I do want to start using the Pi as a DC for my physical Windows clients (my family's 3x computers - one Vista, one Win7, and one Win8), and I wanted to ensure I could upgrade it cleanly without loss of service first.
So I used "git pull" to download the latest changes, as described in the Samba4 HOWTO guide. The configure, make, and make install stages went without a hitch (although the little Pi doesn't exactly blast through the compile, so it took several long hours). As a just-in-case, I even stopped Samba from running before I ran "make install" just in case the script couldn't overwrite a file that was in use.
So I tried to check which version this had upgraded to by running samba -V:
root@raspberrypi:/usr/local/samba4# samba -V
samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required
by samba)
samba: /usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
... huh.
I hoped that maybe it was just the version argument that stopped working - so I tried to start up the samba daemon (rather than using the "service samba4 start" command I had used previously without fail, as this script suppresses command line output):
root@raspberrypi:/usr/local/samba4# samba
samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba:
/usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
... and a quick check of "ps -A | grep samba" confirms that it is indeed not running.
I checked that all of the above files actually do exist at the given paths:
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libcliauth.so
-rwxr-xr-x 1 root staff 157540 Apr 3 08:21 /usr/local/samba/lib/private/libcliauth.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libauth4.so
-rwxr-xr-x 1 root staff 200714 Apr 3 08:40 /usr/local/samba/lib/private/libauth4.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libevents.so
-rwxr-xr-x 1 root staff 6858 Apr 3 08:18 /usr/local/samba/lib/private/libevents.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libcluster.so
-rwxr-xr-x 1 root staff 14230 Apr 3 08:19 /usr/local/samba/lib/private/libcluster.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libprocess_model.so
-rwxr-xr-x 1 root staff 21163 Apr 3 08:20
/usr/local/samba/lib/private/libprocess_model.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libsamdb-common.so
-rwxr-xr-x 1 root staff 222416 Apr 3 08:21 /usr/local/samba/lib/private/libsamdb-common.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libsamba-modules.so
-rwxr-xr-x 1 root staff 15430 Apr 3 08:19 /usr/local/samba/lib/private/libsamba-modules.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libndr-samba4.so
-rwxr-xr-x 1 root staff 2565327 Apr 3 08:21 /usr/local/samba/lib/private/libndr-samba4.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/liberrors.so
-rwxr-xr-x 1 root staff 406455 Apr 3 08:19 /usr/local/samba/lib/private/liberrors.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libservice.so
-rwxr-xr-x 1 root staff 73408 Apr 3 08:40
/usr/local/samba/lib/private/libservice.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libldbsamba.so
-rwxr-xr-x 1 root staff 367089 Apr 3 08:22 /usr/local/samba/lib/private/libldbsamba.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libMESSAGING.so
-rwxr-xr-x 1 root staff 71125 Apr 3 08:27 /usr/local/samba/lib/private/libMESSAGING.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libntvfs.so
-rwxr-xr-x 1 root staff 2366899 Apr 3 08:39 /usr/local/samba/lib/private/libntvfs.so
The smbclient command also fails with the same issue, so I can't even connect to other PCs.
I got the Pi primarily to learn Linux as I am not an experienced Linux user (Windows and Cisco IOS guy here) - I have no idea how to check what version each of these files actually is - so I'm not really sure what to try out next.
Can anyone give me any pointers? It'd be nice to get this back up and running.
Kind regards
Graeme Porter
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
I was running Samba4 for a while on my Raspberry Pi (Raspbian distro, running 3.6.11+ #371 PREEMPT armv6l kernel). The version of Samba I was running was 4.1.0pre1-GIT-fd8b258.
Last night I decided to try to upgrade to see if I could upgrade it without breaking it.
Note that the AD this Pi is the DC for doesn't have any physical clients as members; I was using a Virtual PC running WinXP and another running Ubuntu just to test it out - so technically there's no great loss if it did break - but I do want to start using the Pi as a DC for my physical Windows clients (my family's 3x computers - one Vista, one Win7, and one Win8), and I wanted to ensure I could upgrade it cleanly without loss of service first.
So I used "git pull" to download the latest changes, as described in the Samba4 HOWTO guide. The configure, make, and make install stages went without a hitch (although the little Pi doesn't exactly blast through the compile, so it took several long hours). As a just-in-case, I even stopped Samba from running before I ran "make install" just in case the script couldn't overwrite a file that was in use.
So I tried to check which version this had upgraded to by running samba -V:
root@raspberrypi:/usr/local/samba4# samba -V
samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required
by samba)
samba: /usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
... huh.
I hoped that maybe it was just the version argument that stopped working - so I tried to start up the samba daemon (rather than using the "service samba4 start" command I had used previously without fail, as this script suppresses command line output):
root@raspberrypi:/usr/local/samba4# samba
samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba:
/usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
... and a quick check of "ps -A | grep samba" confirms that it is indeed not running.
I checked that all of the above files actually do exist at the given paths:
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libcliauth.so
-rwxr-xr-x 1 root staff 157540 Apr 3 08:21 /usr/local/samba/lib/private/libcliauth.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libauth4.so
-rwxr-xr-x 1 root staff 200714 Apr 3 08:40 /usr/local/samba/lib/private/libauth4.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libevents.so
-rwxr-xr-x 1 root staff 6858 Apr 3 08:18 /usr/local/samba/lib/private/libevents.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libcluster.so
-rwxr-xr-x 1 root staff 14230 Apr 3 08:19 /usr/local/samba/lib/private/libcluster.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libprocess_model.so
-rwxr-xr-x 1 root staff 21163 Apr 3 08:20
/usr/local/samba/lib/private/libprocess_model.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libsamdb-common.so
-rwxr-xr-x 1 root staff 222416 Apr 3 08:21 /usr/local/samba/lib/private/libsamdb-common.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libsamba-modules.so
-rwxr-xr-x 1 root staff 15430 Apr 3 08:19 /usr/local/samba/lib/private/libsamba-modules.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libndr-samba4.so
-rwxr-xr-x 1 root staff 2565327 Apr 3 08:21 /usr/local/samba/lib/private/libndr-samba4.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/liberrors.so
-rwxr-xr-x 1 root staff 406455 Apr 3 08:19 /usr/local/samba/lib/private/liberrors.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libservice.so
-rwxr-xr-x 1 root staff 73408 Apr 3 08:40
/usr/local/samba/lib/private/libservice.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libldbsamba.so
-rwxr-xr-x 1 root staff 367089 Apr 3 08:22 /usr/local/samba/lib/private/libldbsamba.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libMESSAGING.so
-rwxr-xr-x 1 root staff 71125 Apr 3 08:27 /usr/local/samba/lib/private/libMESSAGING.so
root@raspberrypi:/usr/local/samba4# ls -al /usr/local/samba/lib/private/libntvfs.so
-rwxr-xr-x 1 root staff 2366899 Apr 3 08:39 /usr/local/samba/lib/private/libntvfs.so
The smbclient command also fails with the same issue, so I can't even connect to other PCs.
I got the Pi primarily to learn Linux as I am not an experienced Linux user (Windows and Cisco IOS guy here) - I have no idea how to check what version each of these files actually is - so I'm not really sure what to try out next.
Can anyone give me any pointers? It'd be nice to get this back up and running.
Kind regards
Graeme Porter
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Ricky Nance
Apr 3, 2013, 12:21:47 PM4/3/13
to
The last time you did ./configure, did you specify any arguments, if so,
you will need the same arguments on this install. Also, I typically start
'fresh' by issuing a git clean -x -f -d after git pull and before
./configure.
Ricky
--
you will need the same arguments on this install. Also, I typically start
'fresh' by issuing a git clean -x -f -d after git pull and before
./configure.
Ricky
Graeme Porter
Apr 3, 2013, 12:46:49 PM4/3/13
to
Hi Ricky,
Thanks for replying.
The original build was just run with the arguments on the HOWTO:
./configure --enable-debug --enable-selftest
With the latest build, I thought I'd try adding Avahi on there as a means of "announcing" the Pi to domain members; as I understand it, Samba4 currently has no means of appearing under the "Network Neighborhood", but previous versions did, and that Avahi is capable of providing that. I'd forgotten about adding Avahi in until your reply, oops :(
The same arguments I previously used were still part of the ./configure command I ran - i.e. I didn't remove either of them:
./configure --enable-avahi --enable-debug --enable-selftest
Could adding this have caused the problem?
Kind regards,
Graeme
________________________________
From: Ricky Nance <ricky...@weaubleau.k12.mo.us>
To: Graeme Porter <graeme...@yahoo.co.uk>
Cc: "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 3 April 2013, 17:21
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
Thanks for replying.
The original build was just run with the arguments on the HOWTO:
./configure --enable-debug --enable-selftest
With the latest build, I thought I'd try adding Avahi on there as a means of "announcing" the Pi to domain members; as I understand it, Samba4 currently has no means of appearing under the "Network Neighborhood", but previous versions did, and that Avahi is capable of providing that. I'd forgotten about adding Avahi in until your reply, oops :(
The same arguments I previously used were still part of the ./configure command I ran - i.e. I didn't remove either of them:
./configure --enable-avahi --enable-debug --enable-selftest
Could adding this have caused the problem?
Kind regards,
Graeme
________________________________
From: Ricky Nance <ricky...@weaubleau.k12.mo.us>
To: Graeme Porter <graeme...@yahoo.co.uk>
Cc: "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 3 April 2013, 17:21
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
Graeme Porter
Apr 5, 2013, 6:22:44 AM4/5/13
to
I have just finished recompiling and still get the same problem:
./configure --enable-debug --enable-selftest
make
make install
Once it had finished, I checked the version again and :
root@raspberrypi:/usr/local/samba/sbin# samba -V
cd /usr/local/
mv samba samba-old
cd /usr/local/samba4
make install
The /usr/local/samba folder structure was recreated, but even after completion, when I type "samba -V" I still get the list of errors above.
Help! :(
Kind regards
Graeme
________________________________
From: Graeme Porter
To: Ricky Nance
Cc: "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 3 April 2013, 17:46
./configure --enable-debug --enable-selftest
make
make install
Once it had finished, I checked the version again and :
root@raspberrypi:/usr/local/samba/sbin# samba -V
samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
So I just tried:
samba: /usr/local/samba/lib/private/libauth4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libevents.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libcluster.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libprocess_model.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamdb-common.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libsamba-modules.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libndr-samba4.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/liberrors.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libservice.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libldbsamba.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libMESSAGING.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
samba: /usr/local/samba/lib/private/libntvfs.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
cd /usr/local/
mv samba samba-old
cd /usr/local/samba4
make install
The /usr/local/samba folder structure was recreated, but even after completion, when I type "samba -V" I still get the list of errors above.
Help! :(
Kind regards
Graeme
________________________________
From: Graeme Porter
To: Ricky Nance
Cc: "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 3 April 2013, 17:46
Michael Wood
Apr 5, 2013, 10:54:58 AM4/5/13
to
Hi
On 5 April 2013 12:22, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> I have just finished recompiling and still get the same problem:
>
> ./configure --enable-debug --enable-selftest
> make
> make install
>
> Once it had finished, I checked the version again and :
>
> root@raspberrypi:/usr/local/samba/sbin# samba -V
> samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
[...]
What does the following print:
$ which samba
Does it work if you use the full path name:
# /usr/local/samba/bin/samba -V
--
Michael Wood <esio...@gmail.com>
On 5 April 2013 12:22, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> I have just finished recompiling and still get the same problem:
>
> ./configure --enable-debug --enable-selftest
> make
> make install
>
> Once it had finished, I checked the version again and :
>
> root@raspberrypi:/usr/local/samba/sbin# samba -V
> samba: /usr/local/samba/lib/private/libcliauth.so: version `SAMBA_4.1.0PRE1_GIT_FD8B258' not found (required by samba)
>
> So I just tried:
>
> cd /usr/local/
> mv samba samba-old
> cd /usr/local/samba4
>
> make install
>
> The /usr/local/samba folder structure was recreated, but even after completion, when I type "samba -V" I still get the list of errors above.
>
> Help! :(
It sounds like the "samba" binary on your PATH is the old version.
> So I just tried:
>
> cd /usr/local/
> mv samba samba-old
> cd /usr/local/samba4
>
> make install
>
> The /usr/local/samba folder structure was recreated, but even after completion, when I type "samba -V" I still get the list of errors above.
>
> Help! :(
What does the following print:
$ which samba
Does it work if you use the full path name:
# /usr/local/samba/bin/samba -V
--
Michael Wood <esio...@gmail.com>
Graeme Porter
Apr 5, 2013, 11:19:12 AM4/5/13
to
Thanks Michael, I've got my domain controller back!
I'm now rather distinctly annoyed. I *was* using a symbolic link in /usr/bin called "samba" that was pointing to /usr/local/samba/sbin/samba - this was the only way I found so far that I could avoid typing the whole command path every time - probably because I still can't see a way to persistently and globally add entries to the path variable (every time I tried this previously, if I logged out and logged in as a different user, my changes to the path were missing, and wouldn't even reappear when I logged back in as myself).
My symbolic link appears to have been replaced at some point with an actual version of Samba. I don't know when or as part of what process (I am still a Linux newbie, so probably something I've done wrong again).
Also, thanks for introducing me to the "which" command - every day is an education!
Another build of Samba is in order - once again with the --enable-avahi flag, to see if that works out.
Many thanks again!
Kind regards
Graeme
________________________________
From: Michael Wood <esio...@gmail.com>
Sent: Friday, 5 April 2013, 15:54
I'm now rather distinctly annoyed. I *was* using a symbolic link in /usr/bin called "samba" that was pointing to /usr/local/samba/sbin/samba - this was the only way I found so far that I could avoid typing the whole command path every time - probably because I still can't see a way to persistently and globally add entries to the path variable (every time I tried this previously, if I logged out and logged in as a different user, my changes to the path were missing, and wouldn't even reappear when I logged back in as myself).
My symbolic link appears to have been replaced at some point with an actual version of Samba. I don't know when or as part of what process (I am still a Linux newbie, so probably something I've done wrong again).
Also, thanks for introducing me to the "which" command - every day is an education!
Another build of Samba is in order - once again with the --enable-avahi flag, to see if that works out.
Many thanks again!
Kind regards
Graeme
________________________________
From: Michael Wood <esio...@gmail.com>
Sent: Friday, 5 April 2013, 15:54
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
Rowland Penny
Apr 5, 2013, 11:31:51 AM4/5/13
to
# Set the path in /etc/profile.d/samba4.sh
echo "PATH=\$PATH:/usr/local/samba/bin:/usr/local/samba/sbin" >
/etc/profile.d/samba4.sh
export PATH=$PATH:/usr/local/samba/bin:/usr/local/samba/sbin
Rowland
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Andrew Bartlett
Apr 6, 2013, 5:49:09 AM4/6/13
to
On Fri, 2013-04-05 at 16:54 +0200, Michael Wood wrote:
> Hi
> It sounds like the "samba" binary on your PATH is the old version.
Well spotted Michael, this one really had me stumped!
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
> Hi
> It sounds like the "samba" binary on your PATH is the old version.
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Ricky Nance
Apr 6, 2013, 12:46:49 PM4/6/13
to
Rowland, while that MAY work, in his case it still would have failed, you
need /usr/local/samba/bin and sbin BEFORE $PATH (eg, export
PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH) otherwise the search
will be done on /bin (or sbin) before it hits the correct binary.
Personally, I add the line export
PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH on the last line of
/root/.bashrc and any users .bashrc that I need to be able to use those
paths.
Ricky
need /usr/local/samba/bin and sbin BEFORE $PATH (eg, export
PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH) otherwise the search
will be done on /bin (or sbin) before it hits the correct binary.
Personally, I add the line export
PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH on the last line of
/root/.bashrc and any users .bashrc that I need to be able to use those
paths.
Ricky
Rowland Penny
Apr 6, 2013, 1:02:56 PM4/6/13
to
On 06/04/13 17:46, Ricky Nance wrote:
> Rowland, while that MAY work, in his case it still would have failed, you
> need /usr/local/samba/bin and sbin BEFORE $PATH (eg, export
> PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH) otherwise the search
> will be done on /bin (or sbin) before it hits the correct binary.
> Personally, I add the line export
> PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH on the last line of
> /root/.bashrc and any users .bashrc that I need to be able to use those
> paths.
>
> Ricky
>
>
> On Sat, Apr 6, 2013 at 4:49 AM, Andrew Bartlett <abar...@samba.org> wrote:
>
>> On Fri, 2013-04-05 at 16:54 +0200, Michael Wood wrote:
>>> Hi
>>> It sounds like the "samba" binary on your PATH is the old version.
>> Well spotted Michael, this one really had me stumped!
>>
>> Andrew Bartlett
>>
>> --
>> Andrew Bartlett http://samba.org/~abartlet/
>> Authentication Developer, Samba Team http://samba.org
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
>>
Ah, but it sounded like he had removed the old samba binary from
> Rowland, while that MAY work, in his case it still would have failed, you
> need /usr/local/samba/bin and sbin BEFORE $PATH (eg, export
> PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH) otherwise the search
> will be done on /bin (or sbin) before it hits the correct binary.
> Personally, I add the line export
> PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH on the last line of
> /root/.bashrc and any users .bashrc that I need to be able to use those
> paths.
>
> Ricky
>
>
> On Sat, Apr 6, 2013 at 4:49 AM, Andrew Bartlett <abar...@samba.org> wrote:
>
>> On Fri, 2013-04-05 at 16:54 +0200, Michael Wood wrote:
>>> Hi
>>> It sounds like the "samba" binary on your PATH is the old version.
>> Well spotted Michael, this one really had me stumped!
>>
>> Andrew Bartlett
>>
>> --
>> Andrew Bartlett http://samba.org/~abartlet/
>> Authentication Developer, Samba Team http://samba.org
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
>>
/usr/sbin and I doubt that he had installed samba4 from the debian repo,
so either way round will work, but I take your point.
Rowland
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Graeme Porter
Apr 17, 2013, 6:01:48 AM4/17/13
to
Hi Andrew,
I performed another upgrade yesterday
First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
The correct file path for samba and smbclient is /usr/local/samba/sbin - the installation process correctly installs the current version of those commands into that path.
Is there something in the configure/make/make install process that copies files into /usr/bin/, or is something else happening? I'd look for it myself and contribute to the project if I only knew what I was doing :)
Kind regards
Graeme
________________________________
From: Andrew Bartlett <abar...@samba.org>
To: Michael Wood <esio...@gmail.com>
Cc: Graeme Porter <graeme...@yahoo.co.uk>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Saturday, 6 April 2013, 10:49
I performed another upgrade yesterday
First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
The correct file path for samba and smbclient is /usr/local/samba/sbin - the installation process correctly installs the current version of those commands into that path.
Is there something in the configure/make/make install process that copies files into /usr/bin/, or is something else happening? I'd look for it myself and contribute to the project if I only knew what I was doing :)
Kind regards
Graeme
________________________________
From: Andrew Bartlett <abar...@samba.org>
To: Michael Wood <esio...@gmail.com>
Cc: Graeme Porter <graeme...@yahoo.co.uk>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Saturday, 6 April 2013, 10:49
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
Michael Wood
Apr 17, 2013, 7:12:04 AM4/17/13
to
Hi
On 17 April 2013 12:01, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Hi Andrew,
>
> I performed another upgrade yesterday
>
> First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
>
> After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
The samba build system does not copy things to /usr/bin (unless you
fiddle with things like --prefix etc.)
How exactly did you make the symlinks?
--
Michael Wood <esio...@gmail.com>
On 17 April 2013 12:01, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Hi Andrew,
>
> I performed another upgrade yesterday
>
> First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
>
> After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
fiddle with things like --prefix etc.)
How exactly did you make the symlinks?
--
Michael Wood <esio...@gmail.com>
Michael Wood
Apr 17, 2013, 7:30:03 AM4/17/13
to
Hi
On 5 April 2013 17:19, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Thanks Michael, I've got my domain controller back!
>
> I'm now rather distinctly annoyed. I *was* using a symbolic link in /usr/bin called "samba" that was pointing to /usr/local/samba/sbin/samba - this was the only way I found so far that I could avoid typing the whole command path every time - probably because I still can't see a way to persistently and globally add entries to the path variable (every time I tried this previously, if I logged out and logged in as a different user, my changes to the path were missing, and wouldn't even reappear when I logged back in as myself).
Changing environment variables by typing something like this at the
shell prompt will only affect the shell you are currently running the
command in and other processes started by that shell (and processes
started by those processes etc.):
$ export PATH="/usr/local/samba/bin:/usr/local/samba/sbin:$PATH"
e.g. if you open two terminal windows and you type the above command
into one and then type "echo $PATH" into the other, you will see that
the second window doesn't see the updated PATH. This is because when
each process starts it gets its own copy of the environment from its
parent. Updating the environment of a process can only affect that
process and its children.
So if you want to affect the environment for all processes you have to
change file that will be read by the shell when it starts. e.g.
/etc/environment or /home/user/.profile.
See also the "System-wide environment variables" section here:
https://help.ubuntu.com/community/EnvironmentVariables
On 5 April 2013 17:19, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Thanks Michael, I've got my domain controller back!
>
> I'm now rather distinctly annoyed. I *was* using a symbolic link in /usr/bin called "samba" that was pointing to /usr/local/samba/sbin/samba - this was the only way I found so far that I could avoid typing the whole command path every time - probably because I still can't see a way to persistently and globally add entries to the path variable (every time I tried this previously, if I logged out and logged in as a different user, my changes to the path were missing, and wouldn't even reappear when I logged back in as myself).
shell prompt will only affect the shell you are currently running the
command in and other processes started by that shell (and processes
started by those processes etc.):
$ export PATH="/usr/local/samba/bin:/usr/local/samba/sbin:$PATH"
e.g. if you open two terminal windows and you type the above command
into one and then type "echo $PATH" into the other, you will see that
the second window doesn't see the updated PATH. This is because when
each process starts it gets its own copy of the environment from its
parent. Updating the environment of a process can only affect that
process and its children.
So if you want to affect the environment for all processes you have to
change file that will be read by the shell when it starts. e.g.
/etc/environment or /home/user/.profile.
See also the "System-wide environment variables" section here:
https://help.ubuntu.com/community/EnvironmentVariables
Graeme Porter
Apr 17, 2013, 7:41:45 AM4/17/13
to
The symlinks were made by entering:
ln /usr/local/samba/sbin/samba /usr/bin/samba
ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient
I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea. Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered?
Kind regards
Graeme
________________________________
Cc: Andrew Bartlett <abar...@samba.org>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 17 April 2013, 12:12
ln /usr/local/samba/sbin/samba /usr/bin/samba
ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient
I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea. Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered?
Kind regards
Graeme
________________________________
Cc: Andrew Bartlett <abar...@samba.org>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 17 April 2013, 12:12
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
Hi
On 17 April 2013 12:01, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Hi Andrew,
>
> I performed another upgrade yesterday
>
> First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
>
> After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
The samba build system does not copy things to /usr/bin (unless you
fiddle with things like --prefix etc.)
How exactly did you make the symlinks?
On 17 April 2013 12:01, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> Hi Andrew,
>
> I performed another upgrade yesterday
>
> First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
>
> After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.
The samba build system does not copy things to /usr/bin (unless you
fiddle with things like --prefix etc.)
How exactly did you make the symlinks?
Michael Wood
Apr 17, 2013, 7:54:16 AM4/17/13
to
On 17 April 2013 13:41, Graeme Porter <graeme...@yahoo.co.uk> wrote:
> The symlinks were made by entering:
>
> ln /usr/local/samba/sbin/samba /usr/bin/samba
> ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient
That's what I suspected :)
> The symlinks were made by entering:
>
> ln /usr/local/samba/sbin/samba /usr/bin/samba
> ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient
Those are hard links, not symbolic/soft links.
You need to use "ln -s source destination" to create symlinks.
> I realise this isn't the correct way of doing things (obviously the correct
> way would be to update the system PATH environment variable), but at the
> same time I can't see why it's a bad idea. Unless something happens to the
> symlink that I wasn't expecting when the file it is linking to is removed or
> altered?
new hard link are indistinguishable from each other. They are both
names that point to the actual file. If you remove one of them (e.g.
by running "make install") the other one will still be there, pointing
to the original file on disk.
i.e. hard links point to the actual file. Symbolic links are names
that point to other names.
Graeme Porter
Apr 17, 2013, 8:34:22 AM4/17/13
to
Whoops :(
Well, every day's a school day - pretty much the reason why I got the Raspberry Pi in the first place was to learn Linux, so thanks for the tip!
Also love the Roald Dahl reference in your e-mail address.
Kind regards
Graeme
________________________________
From: Michael Wood <esio...@gmail.com>
To: Graeme Porter <graeme...@yahoo.co.uk>
Cc: Andrew Bartlett <abar...@samba.org>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Sent: Wednesday, 17 April 2013, 12:54
Well, every day's a school day - pretty much the reason why I got the Raspberry Pi in the first place was to learn Linux, so thanks for the tip!
Also love the Roald Dahl reference in your e-mail address.
Kind regards
Graeme
________________________________
From: Michael Wood <esio...@gmail.com>
To: Graeme Porter <graeme...@yahoo.co.uk>
Cc: Andrew Bartlett <abar...@samba.org>; "sa...@lists.samba.org" <sa...@lists.samba.org>
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors
0 new messages