First - congrats to the hassio guys - can’t believe how easy it was to move my (long standing) config from a mac to a hassio Pi3.
However a couple of problems since I upgrade HA - and trying to dig in to the problem.
HA still works - and I can still SSH into hassio - so most stuff is working fine.
I have two problems
First samba stopped connecting, I’m using wired ethernet - and what I think is the standard config.
{
"workgroup": "WORKGROUP",
"name": "hassio",
"guest": true,
"map": {
"config": true,
"addons": true,
"ssl": false,
"share": true,
"backup": true
},
"username": "",
"password": "",
"interface": "eth0"
}
But the mac that could connect when I shipped my config - can no longer connect sadly the Connection Failed error isn’t very helpful! Here are the logs:-
starting version 3.2.2
nmbd version 4.6.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface eth0 ip=fd00::1:fba2:af9c:9cf3:7422 bcast= netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.1.59 bcast=192.168.1.255 netmask=255.255.255.0
making subnet name:192.168.1.59 Broadcast address:192.168.1.255 Subnet mask:255.255.255.0
create_subnets: ignoring non IPv4 interface.
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
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.59 for name WORKGROUP<1d>.
This response was from IP 192.168.1.58, reporting an IP address of 192.168.1.58.
smbd version 4.6.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[share]"
Processing section "[backup]"
added interface eth0 ip=fd00::1:fba2:af9c:9cf3:7422 bcast= netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.1.59 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
Module 'tdbsam' loaded
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.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
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
STATUS=daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
Only recent changes were moving my mqtt server across to hassio (using the standard plugin), and enabling lets_encrypt via the plugin.
I also have a problem with loop_energy which is a component I maintain (although hasn’t changed for ages) Still works fine on the mac. It uses web sockets - so don’t know if they issues could be related.
Any suggestions?