papoo
Avril 28, 2022, 12:26
1
Mise à jour non fonctionnelle sur certaines configs. Pour plus de sureté, attendre la correction.
opened 11:52PM - 27 Apr 22 UTC
closed 03:46PM - 29 Apr 22 UTC
unsupported
### Describe the issue you are experiencing
Samba no longer working after upgra… ding from 9.5.1 to 9.6
### What type of installation are you running?
Home Assistant Supervised
### Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
### Which add-on are you reporting an issue with?
Samba share
### What is the version of the add-on?
9.6
### Steps to reproduce the issue
1. Upgrade to 9.6
### Anything in the Supervisor logs that might be useful for us?
_No response_
### Anything in the add-on logs that might be useful for us?
```txt
[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
```
### Additional information
Running IP ADDR on 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.55/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
```
I'm no expert, but seems it should be using eno1 and NOT wlp1s0
Lastly, I've never used the `interface: ` configuration option in the add-on setup
j’ai moi aussi subi cela
2 « J'aime »
mcp
Avril 28, 2022, 12:39
2
Bonjour,
Je ne sais pas sur quelle type d’environnement vous avez rencontré ce problème, mais cette mise à jour semble pleinement fonctionnelle sur mon installation (Home Assistant OS, OS 7.6, core-2022.4.7, supervisor-2022.04.0).
mcp
1 « J'aime »
même config
1 « J'aime »
papoo
Avril 28, 2022, 7:19
4
sur ubuntu 20.04 lts pour ma part
Aucun soucis sur Raspberry PI 3 B avec Home Assistant OS 7.6, core-2022.4.7, supervisor-2022.04.0 et windows 10.
papoo
Avril 29, 2022, 7:41
6
pour ceux qui comme moi utilisent un OS non pris en charge, un fork de l’integration samba share permet de continuer à utiliser cette fonctionnalité