mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[DLNA] Many log messages from Media Renderers trying to see old events #1683
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mooninite on GitHub (May 13, 2020).
Describe the bug
I have a Yamaha receiver that acts as a DLNA Media Render device and it is causing a lot of log output after I restart Jellyfin. The cause appears to be the receiver is looking for old events that no longer exist after restarting Jellyfin. Can we either stop logging these errors or is there a response that could be sent to the receiver so it stops looking?
System (please complete the following information):
To Reproduce
A "fix" is to unplug the receiver and plug it back in as the receiver is always "on" even when it is "off" as it is connected to Wi-fi listening for my controller events to remotely power it on/off. After that the log messages stop until I restart Jellyfin.
Expected behavior
No log output.
Logs
(repeated every 3 seconds...)
Screenshots
Additional context
@PrplHaz4 commented on GitHub (May 14, 2020):
at the very least this should be handled by not throwing an exception i think
@BaronGreenback commented on GitHub (Jun 14, 2020):
Null pointer operation. Fixed in #3337.
@stale[bot] commented on GitHub (Oct 12, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.