[DLNA] Many log messages from Media Renderers trying to see old events #1683

Closed
opened 2026-02-06 21:15:10 +03:00 by OVERLORD · 3 comments
Owner

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):

  • OS: Fedora 32
  • Virtualization: None
  • Clients: Browser, DLNA
  • Browser: Firefox 76
  • Jellyfin Version: 10.5.5
  • Playback: DLNA
  • Installed Plugins: Playback Reporting
  • Reverse Proxy: apache
  • Base URL: none
  • Networking: Host
  • Storage: local

To Reproduce

  1. Start Jellyfin
  2. Plug in receiver into power outlet
  3. No log output
  4. Restart Jellyfin
  5. Logs start showing DLNA errors.

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...)

[15:30:19] [ERR] [61] Emby.Server.Implementations.HttpServer.HttpListenerHost: Error processing request. URL: http://10.0.x.x:8096/dlna/<UUID redacted>/contentdirectory/events
 System.NullReferenceException: Object reference not set to an instance of an object.
    at Emby.Dlna.Eventing.EventManager.RenewEventSubscription(String subscriptionId, String notificationType, String requestedTimeoutString, String callbackUrl)
    at Emby.Dlna.Api.DlnaServerService.ProcessEventRequest(IEventManager eventManager)
    at Emby.Server.Implementations.Services.ServiceExecGeneral.Execute(Type serviceType, IRequest request, Object instance, Object requestDto, String requestName)
    at Emby.Server.Implementations.Services.ServiceController.Execute(HttpListenerHost httpHost, Object requestDto, IRequest req)
    at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IRequest httpReq, HttpResponse httpRes, ILogger logger, CancellationToken cancellationToken)
    at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken)

Screenshots

Additional context

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):** - OS: Fedora 32 - Virtualization: None - Clients: Browser, DLNA - Browser: Firefox 76 - Jellyfin Version: 10.5.5 - Playback: DLNA - Installed Plugins: Playback Reporting - Reverse Proxy: apache - Base URL: none - Networking: Host - Storage: local **To Reproduce** <!-- Steps to reproduce the behavior: --> 1. Start Jellyfin 2. Plug in receiver into power outlet 3. No log output 4. Restart Jellyfin 5. Logs start showing DLNA errors. 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** <!-- A clear and concise description of what you expected to happen. --> No log output. **Logs** <!-- Please paste any log errors. --> (repeated every 3 seconds...) ``` [15:30:19] [ERR] [61] Emby.Server.Implementations.HttpServer.HttpListenerHost: Error processing request. URL: http://10.0.x.x:8096/dlna/<UUID redacted>/contentdirectory/events System.NullReferenceException: Object reference not set to an instance of an object. at Emby.Dlna.Eventing.EventManager.RenewEventSubscription(String subscriptionId, String notificationType, String requestedTimeoutString, String callbackUrl) at Emby.Dlna.Api.DlnaServerService.ProcessEventRequest(IEventManager eventManager) at Emby.Server.Implementations.Services.ServiceExecGeneral.Execute(Type serviceType, IRequest request, Object instance, Object requestDto, String requestName) at Emby.Server.Implementations.Services.ServiceController.Execute(HttpListenerHost httpHost, Object requestDto, IRequest req) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost httpHost, IRequest httpReq, HttpResponse httpRes, ILogger logger, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken) ``` **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Additional context** <!-- Add any other context about the problem here. -->
OVERLORD added the bugstale labels 2026-02-06 21:15:10 +03:00
Author
Owner

@PrplHaz4 commented on GitHub (May 14, 2020):

at the very least this should be handled by not throwing an exception i think

@PrplHaz4 commented on GitHub (May 14, 2020): at the very least this should be handled by not throwing an exception i think
Author
Owner

@BaronGreenback commented on GitHub (Jun 14, 2020):

Null pointer operation. Fixed in #3337.

@BaronGreenback commented on GitHub (Jun 14, 2020): Null pointer operation. Fixed in #3337.
Author
Owner

@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.

@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](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#1683