[PROBLEM] Samba: No shares available after bullseye update

[jakenl]

(15th Sep, 2021 03:16 AM)Nachteule Wrote:  @jakenl

Usually smbd service is not necessary because smb process will lauched via inetd daemon

See /etc/default/samba

Terminal

cat /etc/default/samba
#
# Run mode of Samba (smbd) process. If set to 'inetd', smbd is
# being spawned by inetd daemon on request, otherwise smbd is
# started as daemon via smbd upstart job. After changing this
# variable, you have to run 'sudo xbian-config services select'
# or reboot system
#
RUN_MODE=daemon

I have just the last few days again intensively busy with Samba (integration of the wsdd daemon so that win10 clients XBian also finally see), I can not find any problem with Samba.
Currently I have samba as a service in use

Maybe it is a good idea to get rid of elogind
see my post here:
http://forum.xbian.org/thread-4129-post-37157.html#pid37157

But I can't imagine that this is the reason for your samba problems

If you can't change to a directory, it sounds to me like a filesystem problem, maybe the sd-card is broken.

What says sudo btrfs scrub start /
and then watch btrfs scrub status /

For me it was RUN_MODE=inetd. I changed to daemon and Samba can be seen running as a service now. No shares

I removed the elogind according your other posts. Rebooted: Samba running, no shares.

I did the scrub commands with this as a result:

Terminal

Every 2.0s: btrfs scrub status / xbian: Tue Sep 14 23:29:39 2021

ERROR: getting dev info for scrub failed: Operation not permitted

Well, I ran the watch command as sudo, that gives more information:

Terminal

UUID: e0d9ab5f-0fcc-43a2-a254-25b4dc3824c5
Scrub started: Tue Sep 14 23:32:57 2021
Status: running
Duration: 0:00:35
Time left: 0:02:13
ETA: Tue Sep 14 23:35:46 2021
Total to scrub: 4.06GiB
Bytes scrubbed: 861.62MiB (120.73)
Rate: 24.62MiB/s
Error summary: no errors found

I realized that it is a live 'watch', so I ran the watch command again and waited until finish:

Terminal

UUID: e0d9ab5f-0fcc-43a2-a254-25b4dc3824c5
Scrub started: Tue Sep 14 23:32:57 2021
Status: finished
Duration: 0:02:44
Total to scrub: 4.06GiB
Rate: 25.34MiB/s
Error summary: no errors found

---

(15th Sep, 2021 06:53 AM)Nachteule Wrote:  

(15th Sep, 2021 05:09 AM)Zarquon Wrote:  

(14th Sep, 2021 05:05 PM)jakenl Wrote:  

(14th Sep, 2021 04:59 PM)Zarquon Wrote:  

(14th Sep, 2021 06:17 AM)jakenl Wrote:  After the bullseye update, I have no samba shares available anymore.

I had the same problem and noticed that in the following error

Terminal

Error loading module '/usr/lib/arm-linux-gnueabihf/samba/vfs/widelinks.so': /usr/lib/arm-linux-gnueabihf/samba/vfs/widelinks.so: cannot open shared object file: No such file or directory

in the /var/logs/samba/[<CLIENTNAME> logfile.

I commented out the "wide links = yes" in the smb.conf file and it started working. Not the best fix but it worked.

Thanks. However, I followed your tip and removed this line in smb.conf, but to no avail.

Have you tried turning logging on? Any errors?

He can't get into /var/log/samba, How should he be able to look at logfiles there?

in /var/log there are 2 folders with root:adm rights and both are not accessible (the second is named 'unattended upgrades'). I deleted the samba folder and recreated as root.
After restart of the smbd service, this is the llog file:

Terminal

xbian@xbian /var/log/samba $ cat log.smbd
[2021/09/14 23:39:05.247526, 0] ../../source3/smbd/server.c:1784(main)
smbd version 4.13.5-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2021/09/14 23:39:05.312899, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2021/09/14 23:39:05.331094, 0] ../../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2021/09/14 23:39:05.331394, 0] ../../source3/smbd/server.c:1076(smbd_open_one_socket)
smbd_open_one_socket: open_socket_in: Address family not supported by protocol
[2021/09/14 23:39:05.343131, 0] ../../source3/lib/util_sock.c:334(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2021/09/14 23:39:05.343423, 0] ../../source3/smbd/server.c:1076(smbd_open_one_socket)
smbd_open_one_socket: open_socket_in: Address family not supported by protocol

OK, this seems to be related to ipv-6, nothing to worry about.