14.1_&_Samba_4.19

Greetings Ladies & Gents,

I have a box booting both BSD 13.2 & 14.1 (ufs2)
All is fine on the 13.2, but the 14.1 install will not run Samba 4.19 – or 4.16.
I’ve tested both against a single Win10 unit.
I’ve used the same drive partitions as samba shares on both -- (different share names per OS)

The installation seemed fine; I believe the smb4.conf & the /etc/rc.conf are set correctly.
When I run /etc/rc.d/sshd restart its status is fine.
But, when I run either smbstatus or testparm -s I receive this file-type error:

d-elf.so.1: /usr/local/lib/libpopt.so.0: invalid file format


Anyone seen this and/or offer a possible solution?

Thanks, S
 
freebsd-version -kru ; uname -aKU

pkg -vv | grep -B 1 -e url -e priority

– what are the details?

d-elf.so.1: /usr/local/lib/libpopt.so.0: invalid file format

Something might be missing from the beginning of that line.



For reference:

Code:
root@fourteen-pkgbase:~ # pkg provides /usr/local/lib/libpopt.so.0
Name    : popt-1.19_1
Comment : Getopt(3) like library with a number of enhancements, from Redhat
Repo    : FreeBSD-ports
Filename: usr/local/lib/libpopt.so.0.0.2
          usr/local/lib/libpopt.so.0
root@fourteen-pkgbase:~ # freebsd-version -kru ; uname -aKU
14.1-RELEASE-p5
14.1-RELEASE-p5
14.1-RELEASE-p5
FreeBSD fourteen-pkgbase 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 releng/14.1-n267718-524a425d30fc GENERIC amd64 1401000 1401000
root@fourteen-pkgbase:~ # pkg -vv | grep -B 1 -e url -e enabled
  FreeBSD-ports: {
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/quarterly",
    enabled         : yes,
--
  FreeBSD-base: {
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/base_release_1",
    enabled         : yes,
root@fourteen-pkgbase:~ # pkg rquery %o popt
devel/popt
root@fourteen-pkgbase:~ #
 
Well.
The last thing I tried was to remove passdb backend = tdbsam from smb4.conf.
I restarted the sshd, and once more, from win typed in the server address – bingo!
For the 1st time it asked for my smb password and I was in! -- all three shares are connected.

[That shouldn’t have happened because I had that in & out with several previous combinations, but there you gol]

Thank you, Cath O'Deray for looking in.
 
The ld-elf.so.1 message indicates you've may have some sort of dependancy issue (with libpopt), so think you might still have problems down the track.
 
Back
Top