Jump to content

Plugin shutting my server down...


Go to solution Solved by ebr,

Recommended Posts

Posted

I'm not sure what the limit for amount of characters in the filename is, but when it reaches a certain length, the Emby server process is killed, and just the Electron process remains active, so I have to force quit that one to start up the server again. 

 

It is happening when I click to open the overview for the specific episodes. 

 

Is this a known issue? 

Posted (edited)

Ok, I've attached logs in this post. 

 

I did this to replicate the problem: 

1. open a random episode that doesn't crash the server, to show that the server is working fine. 

2. open the series/episodes that have long filenames, which kills the Emby process. 

embyserver-63676187369.txt

Edited by dnanielsen
Posted

This looks like a normal shutdown. A shutdown request came in from somewhere:

2018-10-26 21:49:28.902 Info HttpServer: HTTP POST http://localhost:8096/system/shutdown. UserAgent: 
Posted

The shutdown request is not from me, so there is definitely something going in with too long filenames. It's happened in the past also, so I have to rename the file to a shorter name for it to work, but I would prefer if the filename could just stay as it originally is. 

 

I can also reproduce the shutdown when I open my TV shows library and click the episodes tab to view all shows episodes, when those episodes with long filenames are loaded in the list, the server shuts down. 

Posted

What, exactly, is leading you to believe this has anything to do with the file names?

 

Also try removing the playback reporting and statistics plug-ins.

Spaceboy
Posted

I have also had problems with too long file names crashing the server. For me it seems to be related to the trailer plugin, for some reason sometimes it keeps downloading additional versions of the trailer appending -trailer to each new download. Over a period of time the filenames grow too long and the item crashes the server. I have posted about it before, the log didn’t show any errors, it just died. Obviously a different cause but same outcome. I posted within the last 2 months about it

Posted

I could not see anything in his log leading me to conclude anything about file names.

Posted

What, exactly, is leading you to believe this has anything to do with the file names?

 

Also try removing the playback reporting and statistics plug-ins.

 

Because it has happened multiple times in the past, and it's always been with media that has long filenames. What I've had to do is rename them to shorter names, and after doing a library scan, I can access those episodes just fine. 

Posted

There's nothing here that suggests any problem with long file names. A normal shutdown command is coming in that is telling your Emby Server to shutdown.

 

The user agent is blank so that means it's not the web app. Do you have other software that connects to Emby?

Posted

I am running Emby for Android app and LG Smart TV app, if that is what you're asking? 

 

Not sure if it could be related, but the media files are on a NAS network drive, still it's only happening with those files with long filenames - they are less than 1% of my library so it isn't often, but it would be good if I can let those files stay with the filenames they originally have. 

Posted

Ok, what we should be focusing on is that shutdown request.

Posted

How many characters in the path for the long file names? I've seen some issues before but usually only if it exceeds 260 characters.

I am running Emby for Android app and LG Smart TV app, if that is what you're asking?

 

Not sure if it could be related, but the media files are on a NAS network drive, still it's only happening with those files with long filenames - they are less than 1% of my library so it isn't often, but it would be good if I can let those files stay with the filenames they originally have.

Sent from my ONEPLUS A6003 using Tapatalk

Posted

The filename for one of the episodes if 112 characters. 

The complete path for the folder is 123 characters, this is counting from root of the network drive letter. 

  • Solution
Posted

Also try removing the playback reporting and statistics plug-ins.

  • Like 1
Posted

Great, that fixed it. Thanks! 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...