mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[ERR] Error sending socket message #672
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 @gerroon on GitHub (May 5, 2019).
Hi
My systemd logs are littered with these messages, I am not sure if this is important or not but literally Jellyfin throws this error every couple seconds.
I am just worried that it is unnecessarily keeping the server and the network busy.
I am on Debian x64 using Jellyfin 10.3.2-1
@dougppaz commented on GitHub (Jun 3, 2019):
Same problem here using latest Jellyfin docker image + Alpine Linux OS (server) + Docker Swarm
@anthonylavado commented on GitHub (Jun 5, 2019):
So reading this, this is the keep alive broadcast for DLNA. It’s advertising itself as available. If you don’t plan on using DLNA, you can disable it in the dashboard. If you do plan on it, check that nothing else on the same machine is using port 1900 (like Spotify, for example).
@gerroon commented on GitHub (Jun 5, 2019):
Yes it is dlna, and I am using it and I have many other dlna/upnp servers and receivers on the server.
You generally are not allowed to change dlna port, as far as I understand that is a multicast thing so it is not about ports.
This issue was not about disabling Dlna, I am asking a way to make the logs less chatty.
@nonplusnl commented on GitHub (Jun 10, 2019):
Have the same issue logged, however I have DLNA server and DLNA blast msgs disabled. Moreover, the errors are using an originating IP address which Jellyfin is instructed not to bind to (one belonging to a local VPN server).
@NoxInmortus commented on GitHub (Jul 9, 2019):
Hello, same error here, with DLNA disabled.
@oddstr13 commented on GitHub (Jul 9, 2019):
The error for port in use is a different one (explicitly states that that's the issue)
This may be related to dotnet/corefx#35445
There are plenty of mentions of this error when searching for
0xFFFFFFFF socket exception, none of which seem solved.Here's another one; https://stackoverflow.com/a/55806183
When this error occurs, can you verify that the IP address mentioned in the log is indeed assigned to one of the interfaces on the server? That's the only thing I can think of checking right now.
@NoxInmortus commented on GitHub (Jul 9, 2019):
In my case, jellyfin listen on all interfaces (0.0.0.0). As for the log, I may have things like this if the machine is connected to my vpn :
Error sending socket message from "10.190.190.2" to "239.255.255.250:1900"Otherwise, my main ipv4 is displayed instead of
10.190.190.2@oddstr13 commented on GitHub (Jul 9, 2019):
Listening would be on all interfaces, yes.
But the patched version of the DLNA library is explicitly transmiting every message on every interface iirc.
I can imagine weird errors like this could be thrown if the IP addresses are cached on application start, and change while jf is running.
@stale[bot] commented on GitHub (Oct 7, 2019):
Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.
@gerroon commented on GitHub (Jan 12, 2020):
Hi It would be very nice if these messages are disabled, it makes reading logs quite painful, because it is littering the logs.
@axelsimon commented on GitHub (Nov 10, 2020):
I think this should be re-opened, as in my case this message seems to prevent Jellyfin from actually fully loading:
i was never able to reach localhost:8096 while it appeared, but after shutting down my wireguard interface, Jellyfin started fine.
Also, it appears that restarting the wireguard interface after Jellyfin has loaded is not a problem for Jellyfin.
@ggogel commented on GitHub (Jan 1, 2021):
I'm trying to migrate my single host docker setup to docker swarm and have the same issue. It prevents Jellyfin from loading properly at the moment, though it did load a few hours ago. I never published this port before and didn't have this issue on my single host docker setup.