Rejected connection

#1

Suddenly, while playing with audio files, mopidy stopped working. I am getting thousands of this messages in the log:

2019-03-17 17:29:48,959 WARNING [433:MainThread] mopidy.internal.network: Rejected connection from [::ffff:127.0.0.1]:6600

where should I start troubleshooting?

0 Likes

#2

Trying to drill down the issue, it seems it is happening when accessing my Radio Playlist (Dirble+Tunein). The playlist is not showing and the log starts filling up with those messages. I have then found this one:

2019-03-17 17:39:15,449 INFO [426:MainThread] mopidy.commands: GLib mainloop got SIGTERM. Exiting...
2019-03-17 17:39:15,451 INFO [426:MainThread] mopidy.commands: Stopping Mopidy frontends    
2019-03-17 17:39:33,996 WARNING [426:DirbleBackend-13] urllib3.connectionpool: Retrying (Retry(total
    =0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutErr
    or("HTTPConnectionPool(host='api.dirble.com', port=80): Read timed out. (read timeout=30.0)",)': /v2
    /station/58278?token=4fd2a3d9e68118a39ed868c3ea

Could this be the problem?

0 Likes

#3

Maybe it was a temporary problem with Dirble, as now it is working back. But this kind of network problems should not bring to a GLib sigterm!

0 Likes