PDA

View Full Version : [VU+ Ultimo4K] Samba not working after 5.2.001 flash - SAMBA_4.4.16' not found



Timmo65
14-10-18, 14:57
Hello,
I flashed from image manager with restore settings and plugins to 5.2 from 5.1.033 on ultimo4k.
Samba no longer starts for me. I flashed back to 5.1.033 and it works fine. Then back to 5.2.001 again and it will not start. I uninstalled and re-installed from the network/utilities option but it will not start .

I have read various posts about adding user/password details but not sure. When displaying version and also trying a restart i get a page full of these....

root@vuultimo4k:/etc/samba# smbd -V
smbd: /usr/lib/samba/libpopt-samba3-samba4.so: version `SAMBA_4.4.16' not found (required by smbd)
smbd: /usr/lib/samba/libsamba-cluster-support-samba4.so: version `SAMBA_4.4.16' not found (required by smbd)
smbd: /usr/lib/samba/libsamba-sockets-samba4.so: version `SAMBA_4.4.16' not found (required by smbd)
smbd: /usr/lib/samba/libsmbd-shim-samba4.so: version `SAMBA_4.4.16' not found (required by smbd)

Any advice please ?
Thanks Martin

tappari
14-10-18, 15:09
Try with telnet: opkg install packagegroup-base-samba

Timmo65
14-10-18, 15:49
Hi,
thanks. I tried that and rebooted but no good. It looked like it was installing ok - some msgs at the start about breaking dependencies....then what looks like good msgs - but same end result - will not start and same error msgs. -
root@vuultimo4k:~# opkg install packagegroup-base-samba
cifs-utils: unsatisfied recommendation for kernel-module-cifs
packagegroup-base-smbfs: unsatisfied recommendation for kernel-module-cifs
packagegroup-base-smbfs: unsatisfied recommendation for kernel-module-smbfs
Not selecting libc6 2.25 as installing it would break existing dependencies.
Not selecting libaddns-samba4 4.4.16 as installing it would break existing depen
........snip...........

Installing cifs-utils (6.6) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/5.1/vuultimo4k/cortex a15hf-neon-vfpv4/cifs-utils_6.6-r0_cortexa15hf-neon-vfpv4.ipk.
Installing packagegroup-base-smbfs (1.0) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/5.1/vuultimo4k/vuulti mo4k/packagegroup-base-smbfs_1.0-r83.6_vuultimo4k.ipk.
Installing packagegroup-base-smbfs-client (1.0) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/5.1/vuultimo4k/vuulti mo4k/packagegroup-base-smbfs-client_1.0-r83.6_vuultimo4k.ipk.
Installing libaio1 (0.3.110) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/5.1/vuultimo4k/cortex
.....snip...

Configuring libaio1.
Configuring libxattr-tdb-samba4.
Configuring libgpo-samba4.
Configuring libnet-keytab-samba4.
Configuring libhttp-samba4.
Configuring libdcerpc0.
Configuring libregistry-samba4.
Configuring samba.
Configuring packagegroup-base-smbfs-utils.
Configuring cifs-utils.
Configuring packagegroup-base-smbfs.
Configuring packagegroup-base-smbfs-client.
Configuring packagegroup-base-samba.

bbbuk
14-10-18, 16:14
Could you fresh flash 5.2.001 with no restore of plugins and telnet "opkg install samba" and post the results if you can. It maybe little difficult capturing the entire text as I suspect it will display a lot of information. This will hopefully give us more clue of where/what it fails on.

Ensure you make a backup of current image first.

If there is too much text to capture you could try redirecting output to a file (again after you do a fresh flash again i'm afraid). You can do this via "opkg install samba > /tmp/samba.txt". This will send normal output messages to a text file named samba.txt in /tmp folder.

The following is a list of samba dependencies (based on mips processor - I haven't actually installed this as box is in use currently) but as you can see it installs/requires a lot....


Depends: libaddns-samba4 (>= 4.6.7), libads-samba4 (>= 4.6.7), libaio1 (>= 0.3.110), libattr1 (>= 2.4.47), libauth-samba4 (>= 4.6.7), libbsd0 (>= 0.8.6), libc6 (>= 2.26), libcharset3-samba4 (>= 4.6.7), libcli-smb-common-samba4 (>= 4.6.7), libcli-spoolss-samba4 (>= 4.6.7), libcliauth-samba4 (>= 4.6.7), libcom-err2 (>= 1.43.7), libdbus-1-3 (>= 1.12.2), libdbwrap-samba4 (>= 4.6.7), libdcerpc-binding0 (>= 4.6.7), libdcerpc-samba-samba4 (>= 4.6.7), libflag-mapping-samba4 (>= 4.6.7), libform5 (>= 6.0+20170715), libgenrand-samba4 (>= 4.6.7), libgensec-samba4 (>= 4.6.7), libgpo-samba4 (>= 4.6.7), libgse-samba4 (>= 4.6.7), libgssapi-krb5-2 (>= 1.15.1), libiov-buf-samba4 (>= 4.6.7), libkrb5-3 (>= 1.15.1), libkrb5samba-samba4 (>= 4.6.7), libldap-2.4-2 (>= 2.4.45), libldb (>= 1.1.29), libldbsamba-samba4 (>= 4.6.7), liblibcli-lsa3-samba4 (>= 4.6.7), liblibsmb-samba4 (>= 4.6.7), libmsghdr-samba4 (>= 4.6.7), libmsrpc3-samba4 (>= 4.6.7), libncurses5 (>= 6.0+20170715), libndr-krb5pac0 (>= 4.6.7), libndr-samba-samba4 (>= 4.6.7), libndr-standard0 (>= 4.6.7), libndr0 (>= 4.6.7), libnet-keytab-samba4 (>= 4.6.7), libnetapi0 (>= 4.6.7), libpanel5 (>= 6.0+20170715), libpopt-samba3-samba4 (>= 4.6.7), libpopt0 (>= 1.16), libprinting-migrate-samba4 (>= 4.6.7), libreadline7 (>= 7.0), libregistry-samba4 (>= 4.6.7), libsamba-credentials0 (>= 4.6.7), libsamba-debug-samba4 (>= 4.6.7), libsamba-errors1 (>= 4.6.7), libsamba-hostconfig0 (>= 4.6.7), libsamba-passdb0 (>= 4.6.7), libsamba-security-samba4 (>= 4.6.7), libsamba-sockets-samba4 (>= 4.6.7), libsamba-util0 (>= 4.6.7), libsamba3-util-samba4 (>= 4.6.7), libsamdb-common-samba4 (>= 4.6.7), libsamdb0 (>= 4.6.7), libsecrets3-samba4 (>= 4.6.7), libserver-id-db-samba4 (>= 4.6.7), libsmb-transport-samba4 (>= 4.6.7), libsmbconf0 (>= 4.6.7), libsmbd-base-samba4 (>= 4.6.7), libsmbd-shim-samba4 (>= 4.6.7), libsmbldap0 (>= 4.6.7), libsocket-blocking-samba4 (>= 4.6.7), libsys-rw-samba4 (>= 4.6.7), libtalloc (>= 2.1.9), libtalloc-report-samba4 (>= 4.6.7), libtdb-wrap-samba4 (>= 4.6.7), libtdb1 (>= 1.3.14), libtevent-util0 (>= 4.6.7), libtevent0 (>= 0.9.31), libtime-basic-samba4 (>= 4.6.7), libtinfo5 (>= 6.0+20170715), libtrusts-util-samba4 (>= 4.6.7), libutil-reg-samba4 (>= 4.6.7), libutil-tdb-samba4 (>= 4.6.7), libwbclient0 (>= 4.6.7), libxattr-tdb-samba4 (>= 4.6.7), samba-base, samba-dsdb-modules, samba-python

Timmo65
14-10-18, 16:24
Hi,
Thanks for your help.
Family are on the box now so,will try tomorrow. Is it still ok to flash using image manager or should I use usb?

bbbuk
14-10-18, 20:30
Either way shouldn't make a difference but I personally use USB most of time when flashing.

bbbuk
15-10-18, 10:05
I've just installed samba using the above telnet command I mentioned on my solo2 and no errors at all were returned.

Timmo65
15-10-18, 19:03
Hi,
It was me of course. Restore with no plugins did not work but restore with no settings and no plugins did. It appears somewhere along the way in the file selection of the backup manager I had selected the whole etc folder so I assume something in there was getting restored that the samba install didn't like. At least I think that was it, all good now thanks for your time.

bbbuk
15-10-18, 19:40
If Samba installs some settings files in /etc then it's likely it was Samba itself because Samba (https://www.world-of-satellite.com/showthread.php?60078-OpenViX-5-2-released!) was listed as having changed as part of OE-A core changes in 5.2.x

birdman
15-10-18, 19:51
At least I think that was it, all good now thanks for your time.Have you corrected your backup configuration too?

abu baniaz
15-10-18, 21:43
restore with no settings and no plugins did....

Isn't that "no restore"?

Timmo65
15-10-18, 22:42
Isn't that "no restore"?

yes, just an image flash

Timmo65
16-10-18, 13:07
Hi,
Yes I did. Unchecked etc dir in backup manager then did a new backup, then flashed and restored settings (without, most likely, the backup of /etc/samba) - samba installed fine.

The only thing I am not sure of now is what backup manager will back up as default as I have checked/unchecked so many options along the way and I guess I might hit similar problems going forward.

ccs
16-10-18, 13:24
The easiest (well, one) way would be flash the latest image without a settings/plugin restore and take a copy of /etc/enigma2/settings.

The entry in that file for config.backupmanager.backupdirs will tell you the defaults.

Or maybe someone already has a clean copy of settings to share.