Boredcat 34 Posted April 13, 2014 Share Posted April 13, 2014 Hi I having problems with the Mediabrowser server it crashes. This is happening that last couple of weeks mostly after I added some movies (scan started). It doesn't matter if it was running as a service of normal at startup. I added log files when the MBS was running at startup. Do you have any idea what is causing this ? server-63532985837.txt unhandled_32881a1a-b897-4e33-b6dc-9d9d585dfc0d.txt unhandled_bd3be208-59ae-4643-b66a-26e873dcf62b.txt Link to comment Share on other sites More sharing options...
Luke 37071 Posted April 13, 2014 Share Posted April 13, 2014 One of those is coming from the autoboxset plugin. the other i will look at. 1 Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 13, 2014 Author Share Posted April 13, 2014 Is it an idea of disableing the autoboxset and see if that solve something ? Link to comment Share on other sites More sharing options...
Luke 37071 Posted April 13, 2014 Share Posted April 13, 2014 sure. Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 13, 2014 Author Share Posted April 13, 2014 Autobox removed. and so far the server is still running, I am now moving some movies so the scan is started and see what happens. Link to comment Share on other sites More sharing options...
Jambercob 12 Posted April 14, 2014 Share Posted April 14, 2014 Let me know if removing the Autoboxset fixes this issue. We have been experiencing this issue also for the past week or so now. Running on the official release Version 3.0.5211.41935. Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 14, 2014 Author Share Posted April 14, 2014 Autobox removed and reinstalled using this instructions. It looks like upgrading from the old plugin (0.0.1.2 ) to the new one using the MBS upgrade procedure (automatic) causes something to crash. At this moment my MB Server is running without any crashes almost 24 hours. So I am very happy 1 Link to comment Share on other sites More sharing options...
Jambercob 12 Posted April 19, 2014 Share Posted April 19, 2014 Thank you Boredcat! Issue resolved here now Link to comment Share on other sites More sharing options...
ebr 14913 Posted April 19, 2014 Share Posted April 19, 2014 One of those is coming from the autoboxset plugin. the other i will look at. The logger is actually what is throwing. Can we make it so that it won't do that if one of the string replace parameters happens to be null? Link to comment Share on other sites More sharing options...
Solution ebr 14913 Posted April 19, 2014 Solution Share Posted April 19, 2014 As for the actual issue with the box sets. What I believe is happening is there is something in your library that is inside of a box set but with an invalid tmdb id. This item, in your case also appears to have a null name so it is bombing attempting to log the problem item. Please update to the version of AutoBoxsets I just put up (0.0.2.3) and the problem item should get identified in the log by its path. 1 Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 19, 2014 Author Share Posted April 19, 2014 Updated to version 2.3. Will check the log later this evening. Thnx for your help. Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 19, 2014 Author Share Posted April 19, 2014 Nothing strange in logs at this moment. (Restarted the service). Also no Unhandled logs anymore. Looks like everything works now as expected. Link to comment Share on other sites More sharing options...
Boredcat 34 Posted April 22, 2014 Author Share Posted April 22, 2014 Everything is still running fine. So Solved. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now