Issues with SMB shares

Ive had issues in the passed with samba, uninstalling, reinstalling etc. so Im not sure if this issue is a result of the passed and old files or entries haven’t been deleted or cleaned up.

This is my config:

{
  "workgroup": "WORKGROUP",
  "username": "denver",
  "password": "password",
  "interface": "enp0s18",
  "allow_hosts": [
    "192.168.1.0/16"
  ],
  "veto_files": [
    "._*",
    ".DS_Store",
    "Thumbs.db",
    "icon?",
    ".Trashes"
  ]
}

and the logs show:

[10:45:52] INFO: 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 denver.
nmbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface enp0s18 ip=192.168.1.63 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.63 Broadcast address:192.168.1.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
load_lmhosts_file: Cant open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
smbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
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 enp0s18 ip=192.168.1.63 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
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 192.168.1.63
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.63
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.63
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.63
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.63
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.1.63
run_elections: >>> Won election for workgroup WORKGROUP on subnet 192.168.1.63 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 192.168.1.63
*****
Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.63
*****

When I start my Mac, Finder shows a SMB share for ‘hassio’ but clicking on the fails to open up the samba share.

If I select ‘connect to server’ and type in smb://hassio.local a new share is displayed in finder labelled ‘hassio.local’ and this works if I click on it, enter my username and password etc.

Ive uninstalling the samba add-on and then both ‘hassio’ and ‘hassio.local’ shares are removed from finder on the Mac.

As soon as the samba add-on is reinstalled the ‘hassio’ share shows up again, I have to go through the ‘connect to sever’ again to get hassio.local to show.

The logs seem to show files unavailable but don’t want to start deleting things until Ive asked here.

I posted this during Christmas but Im still having issues with the samba share, I can use it but its constantly updating the logs which Im not sure if thats correct. Below is just a sample that I copied from the samba logs after a refresh.

root opened file groups.yaml read=No write=No (numopen=3)
root closed file groups.yaml (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db-wal read=No write=No (numopen=3)
root closed file home-assistant_v2.db-wal (numopen=2) NT_STATUS_OK
root opened file lox_token.cfg read=No write=No (numopen=3)
root closed file lox_token.cfg (numopen=2) NT_STATUS_OK
root opened file home-panel-config.json read=No write=No (numopen=3)
root closed file home-panel-config.json (numopen=2) NT_STATUS_OK
root opened file secrets.yaml read=No write=No (numopen=3)
root closed file secrets.yaml (numopen=2) NT_STATUS_OK
root opened file binary_sensors.yaml read=No write=No (numopen=3)
root closed file binary_sensors.yaml (numopen=2) NT_STATUS_OK
root opened file sensors.yaml read=No write=No (numopen=3)
root closed file sensors.yaml (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db read=No write=No (numopen=3)
root closed file home-assistant_v2.db (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db read=No write=No (numopen=3)
root closed file home-assistant_v2.db (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db-shm read=No write=No (numopen=3)
root closed file home-assistant_v2.db-shm (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db-wal read=No write=No (numopen=3)
root closed file home-assistant_v2.db-wal (numopen=2) NT_STATUS_OK
root opened file zwcfg_0xf94f1cf0.xml read=No write=No (numopen=3)
root closed file zwcfg_0xf94f1cf0.xml (numopen=2) NT_STATUS_OK
root opened file ui-lovelace.yaml read=No write=No (numopen=3)
root closed file ui-lovelace.yaml (numopen=2) NT_STATUS_OK
root opened file options.xml read=No write=No (numopen=3)
root closed file options.xml (numopen=2) NT_STATUS_OK
root opened file harmony_harmony_hub.conf read=No write=No (numopen=3)
root closed file harmony_harmony_hub.conf (numopen=2) NT_STATUS_OK
root opened file .uuid read=No write=No (numopen=3)
root closed file .uuid (numopen=2) NT_STATUS_OK
root opened file .homekit.state read=No write=No (numopen=3)
root closed file .homekit.state (numopen=2) NT_STATUS_OK
root opened file scripts.yaml read=No write=No (numopen=3)
root closed file scripts.yaml (numopen=2) NT_STATUS_OK
root opened file configuration.yaml read=No write=No (numopen=3)
root closed file configuration.yaml (numopen=2) NT_STATUS_OK
root opened file home-assistant_v2.db read=No write=No (numopen=3)

the system is up to date running the latest versions etc. But this just doesn’t look right.

I notice in the config directory in file manager (Finder as Im using Mac) there are 2 files that are constantly being created and deleted within seconds called

home-assistant_v2.db-shm
home-assistant_v2.db-wal

Is this the correct behaviour for these files or a sign there’s issues?

Any help or advise would be appreciated.