Error doing job: Task was destroyed but it is pending! 0.66.0.b2 #13494
Labels
Comments
|
Turn your log level to |
|
|
With english language (translation disabled):
and zwave disabled: |
|
I'm getting this too - no idea how to recreate. |
|
Since the other messages was during startup, I have logged for a couple of days now, and this is what I got (not at startup these messages). I can confirm that v0.65.6 does not have this problem. I have xxx on the ip and mac adresses for asuswrt, and *** for "highlighting" the errors. |
|
The logs are not going to help that much. Please list the platforms that you are using |
|
expecting the same sinst beta/rc of 0.66. even in the final release this error is regularly seen. running HA on Synology docker. last version without this error was 0.65.5 |
|
I am seeing this error as well after upgrading to the stable release. Looks like there is a thread going on the forum. https://community.home-assistant.io/t/error-in-log-on-restart/48471/4 |
|
I am running th following platforms: Cloud Then just random switches, timers, etc. I have a second HASS install running the latest code that is not seeing the error. It is only running ZWave & MQTT. My entire config can be found at: https://github.com/dancwilliams/homeassistant-config If you need any other details to help out just let me know. |
|
I am using the following platforms:
Sensors:
Lights:
Switches:
Does anyone know what`s necessary to this error to be excecuted? |
|
I am using the following platforms: panel_custom for dominos mqtt pip list output (run as homeassistant user): aiohttp (3.0.9) if you need me to upload my config to github please let me know. running Home-Assistant in a VENV on proxmox as a VM running it on ubuntu 17.10 with python 3.6. link to configuration file backup: https://github.com/tdbellgit/homeassistantconfig HA version 65.6 does not produce any errors in my log but .66 spams my log with the above errors. |
|
Im having this issue too after upgrading to the stable version of 0.66.0 on hassio :-( |
|
On a seriously quick and completely unscientific look at the components listed by the guys above, the common denominators for them and me are mqtt and Zwave. |
|
But, I have an install in my shop that is only running MQTT and zwave that is not seeing the error. It has been running clean since the update to 0.66. |
|
^ that's the bit that made me say 'unscientific' - I'm going to have to sit down and go through my config, yours and everyone else's with a fine-tooth comb looking for duplicates I think :/ |
|
I dont use these two modules, so this could not be the reason ;) |
|
^ argh, would the two of you please stop ruining my theories with facts 😆 |
|
Can you try running Home Assistant with the environtment variable |
|
@balloob - sorry to be thick - where do we put this and I'll give it a go later? |
|
Depends on how you run Home Assistant. If you run from the command line, do exactly like I put up there. Otherwise, you can add a custom component like described here |
|
^ adding now, and just goiing to upgrade to 0.66 stable whilst I'm at it - Will report back shortly. |
|
OK - so I upgraded and I'm now on 0.66.1b0 , which I didn't even know was a thing 😆 Anywho... Hope that makes some sens to you @balloob |
|
This is what I got during startup: |
|
figured I should post my output from you command as well, this was all logged on 66.1.
|
|
Getting this too. On don't have Zwave but have MQTT. HA running on Docker. Will try and get the extra logs |
|
same problem on hassio 066.1 |
|
I started receiving this error tonight in 066.1 after I added a self signed certificate to my http config (from openssl) I commented out ssl_certificate and ssl_key from my config yaml, restarted, no more error. |
|
Like @anthonym21 posted, It seems to be a SSL error. Comment out the ssl_certificate & ssl_key, and pull the power (or restart) and It should come back online. I'm Not sure what caused the issue but I know this fixed mine! |
|
Can you re-include ssl after the restart of the system? |
|
Thanks @ChicBrother. Partial success. I got access to my HA from my iPhone using https://yourdomain. I wish that more attention was given to what I consider are the core functions of HA. |
|
According to this video, referenced in the Home Assistant developer section:
Clearly, more work is required to make the use of asyncio more robust. |
|
Hey, same thing happened to me. After some time looking into it I figured the problem was just Let's Encrypt certificate has expired. So if you're facing this just check your SSL certificate date. I just had to review the certificate and everything went back to normal. |
|
Sorry to say, I think that your SSL certificate expiry was just a coincidence. Certificates are good for about 90 days and I see a burst of 7 of this error messages (same timestamp) about once a day. I stopped HA and copied home-assistant_v2.db to Windows 10 PC and used "DB Browser for SQLite" with the following SQL command to see what events were happening. (I used UTC for the db enquiry) The result did not show any events near the error log time. In my configuration.yaml I have set the recorder not to record several entities and the entire zwave domain. Maybe I need to record everything and wait for the next error burst? Maybe unrelated but I got a burst of these error yesterday after updating to HA 0.71.0: From all of the other posts, I think the error is from the Frontend SSL processing but I have not been able to pinpoint the event. |
|
I have updated to hassio 0.72.0, DNSmasq 1.1, DuckDNS 1.5, MQTT 1.0, SSH 3.7 Still getting a burst (7) of error messages as before but there are some new error messages that occur 3 minutes before that may be a clue as to what is going on. Perhaps related to SSL processing. |
|
@gb53smith startet also getting these new errors. |
|
As first proposed by @ChicBrother, I can confirm that installing the NGINX add-on is a valid workaround for this a other error messages. I am now at hassio 0.72.1 and having been running for 4 days without any error messages. |
|
I'm running nginx on my HA instance for more than month, and since HA is not ussing internal https there is now any https errors. |
|
I just updated from Python 3.5 to 3.6.6 and am now getting these errors. Running HA 0.74 and LetsEncrypt. This issue is now four months old. Has the cause still not been figured out? Are people just living with their logs being filled with these messages? |
|
@joe248 I was also frustrated by the lack of progress on this issue. Have you tried the NGINX add on? Works for me. |
|
Yes, all seems it's related to let's encrypt. Since you just got the error message when you upgraded python, let's encrypt maybe needs to be updated to work correctly with 3.6.6? |
|
The HA https core creates several different error messages. The NGINX add
on bypasses these failing functions with its https reverse proxy. Seemed
like overkill to me but my HA instance has been running totally quiet for
several weeks since it started to use NGINX. I use hassio on a rasp PI 3.
See my previous posts in this topic for NGINX installation steps.
I made no changes to let's encrypt. I just works as part of the hassio
duckdns add on.
A side benefit is you can access the HA instance without using a port
number like 8123 in the URL. (443 is a default)
…On Mon, Jul 23, 2018 at 3:52 PM zepixir ***@***.***> wrote:
Yes, all seems it's related to let's encrypt. Since you just got the error
message when you upgraded python, let's encrypt maybe needs to be updated
to work correctly with 3.6.6?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13494 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZnWmZAJmrG1CdmxRaGaGTT3QPMJFmzcks5uJlOhgaJpZM4S9hE2>
.
|
|
@gb53smith I haven't tried the NGINX add-on since I'm not running hass.io, and installing it manually seemed like a lot of work just to work around this bug. @zepixir since I'm not running hass.io, it's my understanding that LetsEncrypt is just a set of scripts that periodically renew my SSL certificate, not code that's running in or alongside Home Assistant, so I don't think that's the issue. Someone can correct me if that's not the case. |
|
If it helps anyone with debugging (@balloob asked about it on March 31st), here are a few of the lines from my log showing multiple components affected: If I remove ssl_certificate and ssl_key from my http config settings, I don't see the "Task was destroyed" errors anymore, but instead get tons of the following: |
|
This has potentially been fixed in #15577 |
|
Using 0.75.0 and still getting these errors. Using Ubuntu16.04.5 LTS at the moment. Am just going to bite the bullet and upgrade either to 18.04 LTS or use another OS altogether. |
|
I'm running 0.75.0 on Debian and also still getting these messages. |
|
Running 0.75.1 issue still there, debian and hass.io |
|
0.75.3 also |
|
For all incidents reported on 0.75.0 and above, please post your error log along with the list of your components used, whether used SSL (particular if used Let's Encrypt), and your python/docker/os environment. A simple message such as 'I have same error' does not help anyone. |
|
Using Docker on Ubuntu 16.04, with SSL via LetsEncrypt, 0.75.3 and issue still present for me too. |
|
To get more detail debug information, please do following steps
logger:
default: warning
logs:
asyncio: debug
PYTHONASYNCIODEBUG=1 hass |
|
Seeing the same pop up occasionally on my system. Enabled asyncio debug logging and saw the following, so atleast one of them appears to be related to I'll run my system a bit longer tomorrow with asyncio debugging on and see if I can get any other details. I'm on Ubuntu with a Python3.6 venv install. LetsEncrypt SSL cert with nginx reverse proxy. |
I'm running HassOS-HassIO v0.76.1 on a Raspberry Pi 3B+. Add-Ons:
Components:
|
|
hassbian 0.76.1 in docker, using Let's Encrypt SSL. Everything still works though I've noticed that every so often when I try to access the front end it just prompts me for my password (no activated new auth system) . A page refresh lets me in and I get no alert for incorrect password... |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Home Assistant release with the issue:
0.66.0.b2
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
HassIO
Component/platform:
homeassistant.core (SyncWorker)
Description of problem:
Got this error after upgrading to 0.66.0.b2 from 0.65.6:
ERROR (SyncWorker_0) [homeassistant.core] Error doing job: Task was destroyed but it is pending!Additional information:
Also started using the beta channel, and upgraded Host System from 1.1 to 1.3 at the same time.
Is there anyway of debugging this problem?
The text was updated successfully, but these errors were encountered: