Samba share stopped wroking

Configuration
1

Hi all, after the last update of Hassio my samba share stopped working,
i went back in and it was stopped and all the settings where gone, i reset it up and now i cant get back in no matter what i do, i get this error at the bottom

[INFO] Read hostname: hassio Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED 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. tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory 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 Adby. nmbd version 4.8.4 started. Copyright Andrew Tridgell and the Samba Team 1992-2018 Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0 added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0 added interface eth0 ip=192.168.1.163 bcast=192.168.1.255 netmask=255.255.255.0 making subnet name:192.168.1.163 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0 making subnet name:172.30.32.1 Broadcast address:172.30.33.255 Subnet mask:255.255.254.0 making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.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 load_lmhosts_file: Can’t open lmhosts file /etc/samba/lmhosts. Error was No such file or directory daemon_ready: STATUS=daemon ‘nmbd’ finished starting up and ready to serve connections query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.163 for name WORKGROUP<1d>. This response was from IP 192.168.1.166, reporting an IP address of 192.168.1.166. smbd version 4.8.4 started. Copyright Andrew Tridgell and the Samba Team 1992-2018 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]” added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0 added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0 added interface eth0 ip=192.168.1.163 bcast=192.168.1.255 netmask=255.255.255.0 INFO: Profiling support unavailable in this build. No builtin backend found, trying to load plugin tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.17.0.1 check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.30.32.1 daemon_ready: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections waiting for connections send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1 run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.17.0.1 <<< become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.17.0.1 send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1 run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.30.32.1 <<< become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.30.32.1 ***** Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 ***** ***** Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1 ***** query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.163 for name WORKGROUP<1d>. This response was from IP 192.168.1.166, reporting an IP address of 192.168.1.166.

1 Like
2

I, too, have lost the ability to run Samba Share on HassIO. The add-on will not start. I have the default config settings (and even clicked Reset to Defaults). When I click Save on the config window, I get the following error message (again, with DEFAULT settings):

not a valid value for dictionary value @ data['options']. Got {'workgroup': 'WORKGROUP', 'username': 'hassio', 'password': None, 'interface': '', 'allow_hosts': ['10.0.0.0/8', '172.16.0.0/12', '192.168.0.0/16']}
For reference, this is what the default config is:

{
  "workgroup": "WORKGROUP",
  "username": "hassio",
  "password": null,
  "interface": "",
  "allow_hosts": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/16"
  ]
}

There is nothing in the Log for the addon because it refuses to even start.

3

did anybody solve this?

I have a virgin installation and my first plugin was the Samba - which is not working.
Nice start,…

1 Like
4

Yeap still not working.

5

Posting the details of your configuration with proper formatting and any error logs goes a long way in getting help.

6

The configuration is the simple stock one. Worked fine up until version .91 Hass.io. Used to map to the WORKGROUP but now I have to physically map a drive on Win10 to my PI.

Now I get this in the logs.

Could not find child 42 – ignoring query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.121 for name WORKGROUP<1d>.