Samba 9.6 Upgrade Killed Samba

Markus99 · April 27, 2022, 11:03pm

Just upgraded to Samba 9.6, unfortunately. Now it no longer works.

Seeing this log file error:

interpret_interface: Can't find address for wlp1s0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0

Nothing else changed on my configuration. Running Supervised on a NUC.

Config for Samba:

allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - fe80::/10
compatibility_mode: false
password: *pass*
username: *user*
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
workgroup: MSHOME

Full LOG:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] samba.sh: executing... 
[18:02:25] INFO: Hostname: xxx-nuc
[18:02:25] INFO: Interfaces: wlp1s0 lo 
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user *user*.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Registered MSG_REQ_POOL_USAGE
smbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
Processing section "[media]"
interpret_interface: Can't find address for wlp1s0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
interpret_interface: Can't find address for wlp1s0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
INFO: Profiling support unavailable in this build.
Registered MSG_REQ_POOL_USAGE
No builtin backend found, trying to load plugin
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
interpret_interface: Can't find address for wlp1s0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0

Markus99 · April 27, 2022, 11:44pm

Running ip addr after Putty’ing into my NUC shows:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul                                 t qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP grou                                 p default qlen 1000
    link/ether b8:ae:ed:e9:90:23 brd ff:ff:ff:ff:ff:ff
    inet 192.168.86.54/24 brd 192.168.86.255 scope global dynamic eno1
       valid_lft 83610sec preferred_lft 83610sec
    inet6 fe80::baae:edff:fee9:9023/64 scope link
       valid_lft forever preferred_lft forever
3: wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN                                  group default qlen 1000
    link/ether 00:c2:c6:b4:29:40 brd ff:ff:ff:ff:ff:ff
4: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP gro                                 up default
    link/ether 02:42:1e:e2:f9:ce brd ff:ff:ff:ff:ff:ff
    inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio
       valid_lft forever preferred_lft forever
    inet6 fe80::42:1eff:fee2:f9ce/64 scope link
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP gr                                 oup default
    link/ether 02:42:85:79:96:ef brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:85ff:fe79:96ef/64 scope link
       valid_lft forever preferred_lft forever

james28909 · April 28, 2022, 12:19am

i dunno but i have been having problems since the last update 9.5.1. something obliterated my network config and i sure as hell do not feel like reinstalling from scratch. there must be an easier way just to completely reset the network configuration back to factory but i have not found anything.

sorry i cant help you any with your problem but if its any consideration here is my lg output from samba

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] samba.sh: executing... 
[00:12:37] INFO: Hostname: homeassistant
[00:12:37] INFO: Interfaces: eth0 lo 
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user homeassistant.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Registered MSG_REQ_POOL_USAGE
added interface eth0 ip=192.168.254.33 bcast=192.168.254.255 netmask=255.255.255.0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
create_subnets: Ignoring loopback interface.
create_subnets: ignoring non IPv4 interface.
making subnet name:192.168.254.33 Broadcast address:192.168.254.255 Subnet mask:255.255.255.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
queue_query_name: interface 1 has NULL IP address !
smbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
Processing section "[media]"
added interface eth0 ip=192.168.254.33 bcast=192.168.254.255 netmask=255.255.255.0
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
INFO: Profiling support unavailable in this build.
Registered MSG_REQ_POOL_USAGE
No builtin backend found, trying to load plugin
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
queue_query_name: interface 1 has NULL IP address !

if anyone knows anything please for the love of god help… my wall cannot take much more head bashing

whats even funnier is… there is no way to downgrade to a different version without a backup. and stupid me did not create any backups except for the first few days i had it up and running. but something to do with samba has completely broken my hyperv install of hass

tom_l · April 28, 2022, 12:26am

Markus99:

wlp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
                                                                         ^^^^
                                                                         ||||

That interface is not connected.

Markus99 · April 28, 2022, 12:29am

Agree with you on this @tom_l. The Samba add-on should be using the eno1 interface (and was successfully for years now thru Samba 9.5.1), now w/ upgrade to 9.6 it ignores eno1 and tries using wlp1s0, with no success.

Markus99 · April 28, 2022, 1:11am

Also worth noting I’ve tried both with and without the:

interface: eno1

option in the configuration settings. (Also tried with interface: "" which some previous poster[s] found success with). Each yielded the exact same failed result / log output as posted above. (Historically, this option was not included in my config settings for this addon.)

I created this forum thread in case it was a user-error or something I overlooked, but also created an issue on GitHub here: Samba 9.6 Broke Samba · Issue #2447 · home-assistant/addons · GitHub

Lastly, someone on Discord asked about my HA network settings, they appear like this:

configuration.yaml has #default_config: commented out, and does not contain network: This have had no adverse affect on my setup to date and has not changed in years.

Thx in advance for any help!

Tamsy · April 28, 2022, 1:34am

what is:
sudo nmcli connection show --active
telling?

If wlp1s0 is not used anyway have you tried Samba when the wifi chip is deactivated at the OS level?

sudo nmcli radio wifi off

(sudo nmcli radio wifi on to activate it again)

rontaylor · April 28, 2022, 1:45am

I have the same problem. The 9.6.0 upgrade killed my samba s well. 9.5.1 was working fine.
I have added my logs to the Samba 9.6 Broke Samba · Issue #2447 · home-assistant/addons · GitHub

Tamsy · April 28, 2022, 1:50am

Looking at your posted logs at Github I see exactly the same behavior as with Mark’s Samba failure to start: Samba is trying to build-up a connection through WiFi (wlp-xxx) instead through the default NIC.

rontaylor · April 28, 2022, 2:22am

I am using a NUC i3 running Ubuntu and I just checked ( to be sure as I only ever use the RJ45 Ethernet port) the WiFi and the WiFi adapter is not enabled.

joem · April 28, 2022, 8:45am

Similar problem here.
Tried manual and auto configure in HA config.
My adapter is eth0, see image.

SAMBA does detect only Io, but the rest of the log is similar.

[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] samba.sh: executing... 
[20:10:42] INFO: Hostname: homeassistant
[20:10:42] INFO: Interfaces: lo 
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user zsolt.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Registered MSG_REQ_POOL_USAGE
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
smbd version 4.13.17 started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
Processing section "[media]"
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
INFO: Profiling support unavailable in this build.
Registered MSG_REQ_POOL_USAGE
No builtin backend found, trying to load plugin
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_POOL_USAGE
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
added interface lo ip=::1 bcast= netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0

My SAMBA config:

  - 192.168.0.0/16
  - 10.0.0.0/8
  - 172.16.0.0/12
compatibility_mode: false
username: zsolt
password: *redacted*
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes
workgroup: WORKGROUP

tom_l · April 28, 2022, 8:47am

One of you should open an issue:

joem · April 28, 2022, 8:55am

@Markus99 already did.

nickrout · April 28, 2022, 10:25am

Pretty sure the changelog said something about samba now listening on all interfaces.

CentralCommand · April 28, 2022, 12:40pm

On all supported interfaces. I notice in the issue the author says they are running supervised on an unsupported os (put “other”). And above in the posts is mention of Ubuntu (also not supported).

I’ll talk it over with the supervisor team but I’m not going to immediately revert this change without a report of something breaking for a user on a supported system as there was a lot of requests to support multiple interfaces in the samba addon.

EDIT: btw if anyone is seeing issues with this update on a supported system please make a new issue with those details.

Markus99 · April 28, 2022, 1:16pm

Forgive my lack of technical expertise. I’m not trying to have this ‘rolled back’, simply prefer to not adversely affect my current setup. My ip addr shows the wlp1s0 interface as down, yet this is the one post-upgrade the new code is trying to have Samba use? Again, not an expert, but can’t this simply be filtered out and the eno1 interface be used? Clearly this interface has worked for years now before this upgrade, so seems it should be able to be included and used after the upgrade?

CentralCommand · April 28, 2022, 2:56pm

Sure I get it. But HA doesn’t support your system given the installation method you’ve chosen, you do. If you switch to a supported installation method and this change still causes issues then we will make sure to fix them. If you run on an unsupported OS though then you should prepare to face unexpected breaking changes at any time with any update. There is no testing done on unsupported OS’s so its very likely there will be no warning at all. And you’ll need to be prepared to fix what broke yourself.

007DJ · April 28, 2022, 6:37pm

Thanks for the pointer… I use Samba daily and would be crippled without.
Obviously I am holding out on that upgrade and will watch this thread for updates.
As it been reported to the maker(s)

lmagyar1973 · April 28, 2022, 10:01pm

Until it is resolved somebody wants to configure interfaces: and run samba on unsupported interfaces, give this fork a try: GitHub - lmagyar/homeassistant-addon-samba-interface: Restores interfaces configuration for Samba add-on

This is identical with the official 9.6.0 but contains the optional interfaces: parameter (note the plural, interfaces, not interface).

nickrout · April 28, 2022, 10:02pm

Samba is not broken on supported supervised. Debian 11.

EDIT: mind you, I have no wireless interfaces, so I don’t get am interface starting wl

Perhaps a good idea might be to force the wireless interface to not load.