-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime Error #12832
Comments
Still experiencing the same error repeatedly, which is blowing up the log. Log size is 1,793 KB in just under 3 hours, can anyone guide me as to how I may be able to troubleshoot or correct this error? First error below:
Then repeated almost every second, below are some error's with different descriptor numbers:
|
I have the same error
I'm not sure if it is related to #13129 |
me too
|
@manuel-jrs @oldfart101 |
don't understand the question |
Are you sending messages/images from HA to somewhere? |
@Coolie1101 I'm using telegram platform. |
@manuel-jrs |
only MQTT, errors still there after upgrade to 0.66.0 |
@oldfart101 Did you upgrade to 0.66.0 and still seeing the same errors? |
yes, P.S. does Alexa via cloud count? |
@Coolie1101 I upgraded it to 0.66 and still the same errors. |
Same problem here, pretty barebones install. Just a single zwave USB stick and a few zwave PIR sensors set up. no automation, no triggers/events. Running hassbian on a RPi-2b. Version: 0.66.1 It started after about 24 hours total uptime. Apr 10 20:08:30 hassbian hass[426]: INFO:homeassistant.core:Bus:Handling , entity_id=sun.sun, new_state=> Apr 10 20:09:30 hassbian hass[426]: INFO:homeassistant.core:Bus:Handling , entity_id=sun.sun, new_state=> Apr 10 20:10:19 hassbian hass[426]: ERROR:homeassistant.core:Error doing job: Exception in callback SendfileStreamWriter._sendfile_cb(, 16, 15, 59860, 12367, <_UnixSelecto...e debug=False>, True) Apr 10 20:10:19 hassbian hass[426]: Traceback (most recent call last): Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/events.py", line 126, in _run Apr 10 20:10:19 hassbian hass[426]: self._callback(*self._args) Apr 10 20:10:19 hassbian hass[426]: File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_fileresponse.py", line 36, in _sendfile_cb Apr 10 20:10:19 hassbian hass[426]: loop.remove_writer(out_fd) Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/selector_events.py", line 351, in remove_writer Apr 10 20:10:19 hassbian hass[426]: self._ensure_fd_no_transport(fd) Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/selector_events.py", line 258, in _ensure_fd_no_transport Apr 10 20:10:19 hassbian hass[426]: fd, transport)) Apr 10 20:10:19 hassbian hass[426]: RuntimeError: File descriptor 16 is used by transport <_SelectorSocketTransport fd=16 read=polling write=> Apr 10 20:10:19 hassbian hass[426]: INFO:homeassistant.components.http.view:Serving /api/websocket to 192.168.0.69 (auth: True) Apr 10 20:10:19 hassbian hass[426]: INFO:homeassistant.core:Bus:Handling , 16, 15, 59860, 12367, <_UnixSelecto...e debug=False>, True), timestamp=1523391019.5628154, source=/srv/homeassistant/lib/python3.5/site-packages/homeassistant/core.py, exception=Traceback (most recent call last): Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/events.py", line 126, in _run Apr 10 20:10:19 hassbian hass[426]: self._callback(*self._args) Apr 10 20:10:19 hassbian hass[426]: File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_fileresponse.py", line 36, in _sendfile_cb Apr 10 20:10:19 hassbian hass[426]: loop.remove_writer(out_fd) Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/selector_events.py", line 351, in remove_writer Apr 10 20:10:19 hassbian hass[426]: self._ensure_fd_no_transport(fd) Apr 10 20:10:19 hassbian hass[426]: File "/usr/lib/python3.5/asyncio/selector_events.py", line 258, in _ensure_fd_no_transport Apr 10 20:10:19 hassbian hass[426]: fd, transport)) Apr 10 20:10:19 hassbian hass[426]: RuntimeError: File descriptor 16 is used by transport <_SelectorSocketTransport fd=16 read=polling write=> Apr 10 20:10:19 hassbian hass[426]: > Apr 10 20:10:19 hassbian hass[426]: ERROR:homeassistant.core:Error doing job: Exception in callback SendfileStreamWriter._sendfile_cb(, 16, 15, 59860, 12367, <_UnixSelecto...e debug=False>, True) |
Still going. Anyone know what "RuntimeError: File descriptor ##" means or refers to?
|
Same problem. No Telegram. Version: 0.67.1 |
Upgrade to 0.67.1
|
Same problem after a fresh installation. Version is 0.68.1. No Telegram running. Anyone an idea. |
same issue after updating to 0.68.1 After stop, disabling influxdb, start, no more error. |
Did anyone solve this i'm getting the same |
Ver. 0.70.0 |
I am getting the same error. i went 48 hours with out it last time, but then it hit hard. the only way i could stop it was to reboot my RPI. Log got almost 700MB in 15 minutes.
|
I just noticed this for the first time today. It doesn't appear to have happened prior to 0.73.2. Other versions I was on recently: 0.73.1 - I was on briefly. |
I see the same error filling a nearly 10MB log file in 0.71.0 |
I have the same error Home Assistant - 0.78.0 |
Same issue happens in HA 0.79. Apparently I get this outburst of errors when logging into HA Web UI. HA tries to load additional components, as per this thread:
|
Hass.io 0.79.3
I think this is happening when i restart my router. I will try to reproduce it later. |
I get the same issue on 0.79.1, followed by a full HA crash, along with:
Googling that particular Edit: I do have the |
@deviant-studio what camera are you using? |
@awarecan i have several, but suspect this one https://ru.aliexpress.com/item/BESDER-Yoosee-IP-Camera-Wifi-1080P-960P-720P-ONVIF-Wireless-Wired-P2P-CCTV-Bullet-Outdoor-Camera/32793309300.html |
I mean what HA camera platform are you using? https://www.home-assistant.io/components/camera.generic/? |
@awarecan yes, all my cameras are upd: sorry for misinformation. the problematic camera is running under
|
It did change the code no error so far. However, I do not know what did trigger the error. So I have to wait for a couple of days |
@signaleleven could you please try to apply my patch? |
Does this issue only occur for people with cameras in the HASS GUI? I have a few cameras, but I almost never click the Tab in the GUI where they are located which might be why this issue has only appeared for me once (that I have noticed anyway). |
In my case, yes, I have some cameras in the gui, and one is not working (for other reasons). I will try to reproduce it. If I manage to reproduce it reliably, I will apply the patch. |
@awarecan It happened again (good thing I set up an alarm on protracted high CPU usage :) ) and I applied your patch. I use hassio and I had to edit the file within the container. A simple container restart preserved the change. It will not survive a container recreation but until the next upgrade it should hold. |
@awarecan just wanted to confirm that your patch has worked perfectly for me. Thanks much! |
I dont have any camera's and still have the same error. Didnt saw it before, cant think of anything that triggered it (only tried some light automations today). I will try the patch |
This worked for my new installation. I had the same errors, probably related to how I have pages open on my ipad and iphone. None since applying this change. |
@mstovenour what do I remove or add? this is what I have
|
On 81.1 i don't have errors in the log so far. but still got spontaneous cpu full loads, and the only cure is to restart. Can't say for sure if it's same issue since my log is empty. |
I also don't have the flood of logging anymore (I think already in 0.8), but I noticed that when the CPU jumps to 100% it INVARIABLY goes back to normal after exactly 2 hours. I applied the patch but of course I lost it at every upgrade, so I am living with the problem for now (this made me jump from a Rpi to an Intel NUC so I can survive) (I just noticed that in my screenshot above the CPU usage goes down after more than 2 hours. But I must have retriggered the problem by browsing the UI while the problem was present. If I leave the UI alone, it's always going back to nominal in about 2 hours) |
You have to invert the two blocks
and
|
Having this same issue since I added 2 onvif camera's (which aren't working) Relevant configuration.yaml
|
Similar error here:
I use one foscam camera and this error seems to have started after I implemented a snapshot automation to email a picture from the camera. I'm on 0.81.6, RPi3 / Hassbian. |
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 👍 |
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. |
Home Assistant release (
hass --version
):0.64.2
Python release (
python3 --version
):3.5.3
Component/platform:
Unsure, maybe Telegram?
Description of problem:
Repeat error in log.
Expected:
No Error's
Traceback (if applicable):
EDIT: Seems to have been resolved since 0.65
The text was updated successfully, but these errors were encountered: