Skip to content
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

Recorder thread dies after exception from long query #15984

Closed
packetinspector opened this issue Aug 14, 2018 · 6 comments
Closed

Recorder thread dies after exception from long query #15984

packetinspector opened this issue Aug 14, 2018 · 6 comments

Comments

@packetinspector
Copy link

Home Assistant release with the issue:

.75.3

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

rasbian, python virtual env
external MariaDB

Component/platform:

https://www.home-assistant.io/components/recorder/

Description of problem:
A service call returned a very large payload, exceeding the TEXT length in mariadb. Upon insert it throws an exception and the recorder functionality stops.

The recorder component exclude feature doesn't appear granular enough to block logging of this specific event.

Ultimately I altered the column to LONGTEXT to fix the issue.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):


Additional information:
Logs
Aug 12 19:45:03 hass hass[30657]: #33[31m2018-08-12 19:45:03 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.DataError) (1406, "Data too long for column 'event_data' at row 1") [SQL: 'INSERT INTO events (event_type, event_data, origin, time_fired, created) VALUES (%s, %s, %s, %s, %s)'] [parameters: ('kodi_call_method_result', '{"result_ok": true, "entity_id": "media_player.kodi", "input": {"method": "PVR.GetRecordings", "params": {"properties": ["file", "playcount", "star ... (111460 characters truncated) ... 0Dog%20Day%20Afternoon, TV%20(99.1%20DFDF-DT), 20180306_030000, 999877844.pvr", "playcount": 0}], "limits": {"start": 0, "end": 425, "total": 425}}}', 'LOCAL', datetime.datetime(2018, 8, 12, 23, 45, 3, 289274, tzinfo=), datetime.datetime(2018, 8, 12, 23, 45, 3, 349243))] (Background on this error at: http://sqlalche.me/e/9h9h)#33[0m
Aug 12 19:45:03 ultrahouse hass[30657]: Exception in thread Recorder:

@sagilo
Copy link

sagilo commented Sep 12, 2018

see #16074

sagilo added a commit to sagilo/home-assistant-1 that referenced this issue Sep 12, 2018
@balloobbot
Copy link

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 👍

@balloobbot
Copy link

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@basnijholt
Copy link
Contributor

This is still a problem with v0.102.0.

People are experiencing this problem when using the iOS Dark Mode theme in combination with an SQL db and recorder.

See basnijholt/lovelace-ios-dark-mode-theme#6.

@balloob, can you please reopen this issue?

@recklessnl
Copy link

Can confirm I'm having this issue as well...

@home-assistant home-assistant locked as resolved and limited conversation to collaborators Feb 9, 2020
@balloob
Copy link
Member

balloob commented Feb 9, 2020

Please open a new issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants