Need help - many issues, probably related to each other

Installation Home Assistant OS
17

To add to the above, I have been checking all logs and that’s what I have that may be helpful to whoever might help me:

Supervisor log:
23-08-20 16:20:56 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:20:57 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:21:02 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:21:02 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:21:02 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:21:03 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:21:07 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-825’ coro=<PluginDns.watchdog_container() done, defined at /usr/src/supervisor/supervisor/plugins/dns.py:264> exception=CoreDNSJobError(‘Rate limit exceeded, more then 10 calls in 0:30:00’)>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/plugins/dns.py”, line 269, in watchdog_container
return await super().watchdog_container(event)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/plugins/base.py”, line 113, in watchdog_container
await self._restart_after_problem(event.state)
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 144, in wrapper
raise on_condition(
supervisor.exceptions.CoreDNSJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-08-20 16:23:09 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
23-08-20 16:23:09 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_ssh
23-08-20 16:23:09 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_ssh
23-08-20 16:23:09 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from core_ssh
23-08-20 16:23:11 INFO (MainThread) [supervisor.api.middleware.security] /dns/update access from core_ssh
23-08-20 16:24:02 INFO (MainThread) [supervisor.api.middleware.security] /dns/options access from core_ssh
23-08-20 16:24:02 INFO (MainThread) [supervisor.plugins.dns] Restarting CoreDNS plugin
23-08-20 16:24:03 INFO (SyncWorker_3) [supervisor.docker.manager] Restarting hassio_dns
23-08-20 16:24:08 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-988’ coro=<PluginDns.watchdog_container() done, defined at /usr/src/supervisor/supervisor/plugins/dns.py:264> exception=CoreDNSJobError(‘Rate limit exceeded, more then 10 calls in 0:30:00’)>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/plugins/dns.py”, line 269, in watchdog_container
return await super().watchdog_container(event)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/plugins/base.py”, line 113, in watchdog_container
await self._restart_after_problem(event.state)
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 144, in wrapper
raise on_condition(
supervisor.exceptions.CoreDNSJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-08-20 16:24:08 INFO (MainThread) [supervisor.api.middleware.security] /dns/restart access from core_ssh
23-08-20 16:24:08 INFO (MainThread) [supervisor.plugins.dns] Restarting CoreDNS plugin
23-08-20 16:24:08 INFO (SyncWorker_3) [supervisor.docker.manager] Restarting hassio_dns
23-08-20 16:24:14 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-1035’ coro=<PluginDns.watchdog_container() done, defined at /usr/src/supervisor/supervisor/plugins/dns.py:264> exception=CoreDNSJobError(‘Rate limit exceeded, more then 10 calls in 0:30:00’)>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/plugins/dns.py”, line 269, in watchdog_container
return await super().watchdog_container(event)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/plugins/base.py”, line 113, in watchdog_container
await self._restart_after_problem(event.state)
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 144, in wrapper
raise on_condition(
supervisor.exceptions.CoreDNSJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-08-20 16:24:22 INFO (MainThread) [supervisor.ingress] Update Ingress as panel for core_ssh
23-08-20 16:25:17 INFO (MainThread) [supervisor.host.network] Updating local network information
23-08-20 16:25:30 INFO (MainThread) [supervisor.api.middleware.security] /dns/restart access from core_ssh
23-08-20 16:25:30 INFO (MainThread) [supervisor.plugins.dns] Restarting CoreDNS plugin
23-08-20 16:25:30 INFO (SyncWorker_1) [supervisor.docker.manager] Restarting hassio_dns
23-08-20 16:25:36 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-1332’ coro=<PluginDns.watchdog_container() done, defined at /usr/src/supervisor/supervisor/plugins/dns.py:264> exception=CoreDNSJobError(‘Rate limit exceeded, more then 10 calls in 0:30:00’)>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/plugins/dns.py”, line 269, in watchdog_container
return await super().watchdog_container(event)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/plugins/base.py”, line 113, in watchdog_container
await self._restart_after_problem(event.state)
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 144, in wrapper
raise on_condition(
supervisor.exceptions.CoreDNSJobError: Rate limit exceeded, more then 10 calls in 0:30:00
23-08-20 16:50:51 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-08-20 16:53:04 INFO (MainThread) [supervisor.api.middleware.security] /dns/restart access from core_ssh
23-08-20 16:53:05 INFO (MainThread) [supervisor.plugins.dns] Restarting CoreDNS plugin
23-08-20 16:53:05 INFO (SyncWorker_2) [supervisor.docker.manager] Restarting hassio_dns
23-08-20 16:53:10 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:10 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:10 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:11 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:53:16 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:16 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:16 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:16 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:53:21 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:21 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:21 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:22 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:53:27 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:27 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:27 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:28 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:53:32 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:32 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:32 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:33 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
23-08-20 16:53:38 WARNING (MainThread) [supervisor.plugins.base] Watchdog found dns plugin failed, restarting

23-08-20 16:53:38 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning hassio_dns application
23-08-20 16:53:38 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-08-20 16:53:39 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
"

I hope this may help figuring out what’s the issue. In the meantime, I spent hours googling every single sentence in the log, but nothing tried seems to help my case!

Help please :slight_smile:

18

Not necessary yet.

tl;dr.
I didn’t see this in my scan of the thread, but is the working HAOS box still online? If so, then you may have two devices with the hostname “homeassistant” on the same network. Strange things will happen in that case.

Unplug the old Home Assistant box. Then from a PC, “ping homeassistant.local”. Do you get the expected IP?

19

I really don’t understand why people(some) recommend this, maybe because i want the less amount of “interference” From Google, as possible, they “track” one enough and feed you with the same bullock, which they “assume” you want to see, unfortunately it demands constant “verification” to secure Google haven’t “wiped” ones account settings, beside i can’t even remember when i had “resolve” issues latest, i expect my Internet provider takes care of this, On the Wan side, And internally i use IP, not hostnames, and as HA is “Local” so I don’t need ssl, and definitely not an external DNS-Service

Also i have absolutely 0 experience from Watchdog, guess i never needed this, and disable such if it comes with some hardware/software/os, no need for other software to check the other softwares, beside in HA’s case the builtin system-check functionality

EDIT: in HA Console try to type " net inf ", just to verify that you actually have “default” settings

20

We should be way past this point, but yes initially he had, when he started installing ha( on the new device), and his weekend got ruined :slight_smile:

21

Yes we are :slight_smile:

and indeed, week-end got ruined but it should be worthwhile in the long run if I can get this to work


22

!Important

Yes, and after a reinstall/new install of HA, with a resetted Router and a working LAN, there is no need to flush HA dns
So after you have your HA up and “running” you check the logsfiles (BEFORE you start to pump-in/add plugins(add-ons) and Integrations)

Structured way means 1 by 1, with restarts and logfile checks in between

23

no its not since I fully reinstalled HAOS.

However, the DCHP name is « homeassistant-1 » on my router webpage instead of « homeassistant », although in HA settings, the name is « homeassistant » . Could this be an issue ?

Done - It returns information matching the « default » HA network settings. I however dont recognize the first part, the docker address, dns, etc
 don’t match what is shown below after « ipv4: »

24

I installed absolutely nothing yet (beside terminal addons). The log is still showing exactly the same as previously. As long as I havent resolved this, I won’t go further into the setup process.

25

Are you joking ?, or don’t you really not understand the importance of names in a network ?
RESET your Router, sorry i can’t recommend other vice, as you just might mess up your Router setting.

  1. turn of HA and other PC’s laptops, phones, ipads, what ever( after you clered their DNS caches )
  2. RESET your Router
  3. Start up HA (AFTER your Router is “online again”, make sure it( HA) has the correct name and IP in Router, corresponding to what you see under ipv4 in the console, AND that the gateway and DNS is the same as your Routers LAN IP

PS: a screenshot of your “net inf” would have been more appropriate than your word that it is

26

Sorry to sound dumb !

Will do as you suggested and will keep you posted! (Finger crossed this is the explanation!)

27

It’s ok, your logfile tells that ha dns is default"

28

OK - So I turned off my main computers/ipad/phone and HA thinclient. I then fully factory reset my router, waited for it to fully come back online, then turned on the HA thinclient.
Now the DHCP name for HA is indeed “homeassistant” and no longer “homeassistant-1”.
Unfortunately, nothing changed and the issues remain

Here : Upload and share screenshots and images - print screen online | Snipboard.io

I confirm

It seems to be the case - cf printscreen linked above.

29

Yes looks ok, thou i would disable ipv6, ALSO in your Router( or in specific there), as you both have 2 nameservers(dns) there and a gateway in your HA interface-config ( i doubt that you need ipv6 )

type
" net update -h" and go on from there to disable it
and
" net reload" to apply it

In your Router, i obviously don’t know where you disable it ( But i assume you by now have resetted it, so login disable ipv6, and restart router, so you get rid of these setting, they are only there if one actually need this, which im pretty sure you dont, they can create alot mess in a local (mixed) network )mixed= Linux, Apple, Microsoft, Android

30

Seems that i am not the only one having the exact same issue after suffering from a strange HAOS flashing process : Flashing hard drive get stuck at 31% (balena fetcher) - #33 by Damos

As I commented there, I will acquire a sata-USB connector and try flashing from my main PC directly.

Will keep everyone posted.

Cheer

31

What I wonder if the crapware balena etcher messes with the image like manipulating it on the fly while writing trying to inject some custom code/trackers etc. :put_litter_in_its_place:

I just wonder if the badware etcher is not used but instead a program that comes without trackers and ads :man_shrugging:

USBmager

USBImager is a really really simple GUI application that writes compressed disk images to USB drives and creates backups. Available platforms: Windows, MacOS and Linux. Its interface is as simple as it gets, totally bloat-free.

32

Does it?
I have checked github and its source code is there to have a look at.
Looks like an open book to me.
Have you seen this?

I have not used the imager you linked to. I will definitely have a look. The licenses are similar (MIT vs Apache) but there are some differences.

1 Like
33

Good finding @pcwii !!

so just make sure you do NOT download from
https://balena-etcher-io.c0m!!

but use https://etcher.balena.io/
or Releases · balena-io/etcher · GitHub

34

Yes. Balena etcher can be consider as adware (only works with ads enabled) and includes trackers which are always on by default and can be only opt-out after the data leakage happend already. :man_facepalming:

The github issues are full of people complaining about that topics but balena also does heavy censoring on this particular issues and removes comments and maybe even issues they don’t like :man_shrugging:

Github issues from other projects also spread the word about the badware called etcher and ether stopping recommending it with their projects or even get rid of it for (for example don’t provide it anymore for their linux package manager anymore) :point_down:

Yes - but it doesn’t solve the issue that the “official” etcher can be already classified as bad/ad/spy/
ware and is build on EOL software (old, vulnerable electron) and contain trackers and ads itself already. Also I checked one (fake) site at it looks like they actually distributing the original balena etcher spyware by linking to the official github releases. :man_shrugging:

Might be because etcher is build as adware people can easily use it and just distribute their on ads with etcher (just like a modified adware with full functionality)? :joy:

1 Like
35

Or better don’t use this badware which comes with ads and trackers included and uses a EOL browser as base (:man_facepalming:) at all :put_litter_in_its_place:

The alternative is 20.000 (yes twenty thousand!) times :warning: smaller and doesn’t need ads or trackers to work. It’s also more performand and works without any dependencies on virtually all platforms.

36

Thanks for your insight. You definitely seem to be informed and not just complaining. I have used etcher in the past but am always open and looking for new open products for various uses. Thanks for the links.