Zeroconf: bad file descriptor

[chemelli74]

The problem

Error recorded in log

Environment

• Home Assistant Core release with the issue: 0.112.4
• Last working Home Assistant Core release (if known): 0.112.2
• Operating environment (OS/Container/Supervised/Core): Core
• Integration causing this issue: zeroconf
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

-

Traceback/Error logs

2020-07-12 19:36:51 WARNING (zeroconf-Engine-140076120746784) [zeroconf] Error reading from socket -1
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/zeroconf/__init__.py", line 1358, in handle_read
    data, (addr, port, *_v6) = socket_.recvfrom(_MAX_MSG_ABSOLUTE)
OSError: [Errno 9] Bad file descriptor

Additional information

[probot-home-assistant]

Hey there @Kane610, mind taking a look at this issue as its been labeled with an integration (zeroconf) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bdraco]

Do you have ipv6 disabled?

[chemelli74]

Yeah, my docker doesn’t have ipv6 currently Simone Il giorno lun 13 lug 2020 alle 22:41 J. Nick Koston < notifications@github.com> ha scritto:

…

Do you have ipv6 disabled? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#37791 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANVSQUDQD2J5NAXCN5OWYCLR3NWPRANCNFSM4OX52WQQ> .

[bdraco]

Is this causing any problems or just an error in the log ?

[chemelli74]

Is this causing any problems or just an error in the log ?

Seems just an error in the log.

Simone

[bdraco]

@chemelli74

zeroconf:
   default_interface: true
   ipv6: false

Once #37887 is in a release you can disable ipv6

[chemelli74]

@chemelli74

zeroconf:
   default_interface: true
   ipv6: false

Once #37887 is in a release you can disable ipv6

@bdraco, thx for the info.

May I ask to go with autodetect of ipv6 ? So if you find a interface with it, you use it; if not you disable.
Would make it more flexible and error prone ( someone can have 2 interfaces, one with ipv6 and one without ).

Just my 2 cents,

Simone

[bdraco]

May I ask to go with autodetect of ipv6 ? So if you find a interface with it, you use it; if not you disable.

This would be something python-zeroconf would need to implement outside of Home Assistant.

Would make it more flexible and error prone ( someone can have 2 interfaces, one with ipv6 and one without ).

Just my 2 cents,

Simone

[sermayoral]

Hi Everyone.

I had this problem after upgrading to 0.113. I solved putting

zeroconf:
   default_interface: true
   ipv6: false

The warning log disappeared, but after upgrading to 0.113.3 it seems the warning log has reappeared again :-(