PMS Constantly Crashing

Hi, please Help.

Few month ago my PMS crasing very times for weeks…

I have contacted plex support… I Have contacted @sa2000 , but nothing has been able to help me…
I have learned to check the logs, and then i have this erros:
ERROR - [Transcoder] [mp4 @ 062ee940] Application provided duration: -16 / timestamp: 21267896 is out of range for mov/mp4 format
The only way is rebooting my PMS for fix the problem.
Please, anybody can help me??
Sorry for my english I from Chile…

hello,
The Gracenote crash will be fixed in the next release.
thankyou!
regards
jayesh

@“batmanisback987@gmail.com” said:
hello,
The Gracenote crash will be fixed in the next release.
thankyou!
regards
jayesh

Hi, thank you… Mi question is … what is Gracenote?

@wpcorgan said:
Hi, please Help.

Few month ago my PMS crasing very times for weeks…

I have contacted plex support… I Have contacted @sa2000 , but nothing has been able to help me…
I have learned to check the logs, and then i have this erros:
ERROR - [Transcoder] [mp4 @ 062ee940] Application provided duration: -16 / timestamp: 21267896 is out of range for mov/mp4 format
The only way is rebooting my PMS for fix the problem.
Please, anybody can help me??
Sorry for my english I from Chile…

Sorry I did not respond to your earlier message.

The support route is through the forums where logs zip can be attached.

I will have a look at what you sent

@wpcorgan said:
Hi, please Help.

Few month ago my PMS crasing very times for weeks…

I have contacted plex support… I Have contacted @sa2000 , but nothing has been able to help me…
I have learned to check the logs, and then i have this erros:
ERROR - [Transcoder] [mp4 @ 062ee940] Application provided duration: -16 / timestamp: 21267896 is out of range for mov/mp4 format
The only way is rebooting my PMS for fix the problem.
Please, anybody can help me??
Sorry for my english I from Chile…

I cannot see any issue in the logs you provided

The logs cover time period 01:19 am to 09:03 am
You said the server was not available at 20:50
The logs do not go back to that time

Please make sure you collect the logs zip when you restart the server when you notice the issue. Taking the logs 12 hours later would not be any good

You could update to latest beta - 1.13.1.5063 - available from https://plex.tv/downloads

and if the problem occurs, restart the server and collect the logs zip and attach the zip here

@wpcorgan its a plugin Gracenote, Inc., previously called CDDB (Compact Disc statistics Base), is a business enterprise that keeps and licenses an internet-reachable database containing statistics about the contents of audio compact discs and vinyl facts. It offers software program and metadata to businesses that allow their clients to control and seek digital media. Gracenote provides its media management era and worldwide media database of digital enjoyment information to the mobile, vehicle, transportable, domestic, and laptop markets. numerous laptop software applications that are able to gambling CDs, such as Small Winamp iconWinamp, Small Sony Media cross iconSony Media cross, and Small iTunes iconiTunes, use Gracenote’s CDDB era. Gracenote’s database turned into originally created from and maintains to receive voluntary contributions from users. This brought about a licensing controversy while Gracenote have become commercialized.

@sa2000 said:

@wpcorgan said:
Hi, please Help.

Few month ago my PMS crasing very times for weeks…

I have contacted plex support… I Have contacted @sa2000 , but nothing has been able to help me…
I have learned to check the logs, and then i have this erros:
ERROR - [Transcoder] [mp4 @ 062ee940] Application provided duration: -16 / timestamp: 21267896 is out of range for mov/mp4 format
The only way is rebooting my PMS for fix the problem.
Please, anybody can help me??
Sorry for my english I from Chile…

I cannot see any issue in the logs you provided

The logs cover time period 01:19 am to 09:03 am
You said the server was not available at 20:50
The logs do not go back to that time

Please make sure you collect the logs zip when you restart the server when you notice the issue. Taking the logs 12 hours later would not be any good

You could update to latest beta - 1.13.1.5063 - available from https://plex.tv/downloads

and if the problem occurs, restart the server and collect the logs zip and attach the zip here

Thank you very much @sa2000 … The next time when i restart PMS i will download the log files and then send you…
thanks again…

@wpcorgan said:
Thank you very much @sa2000 … The next time when i restart PMS i will download the log files and then send you…
thanks again…

No - not send to me but attach in a post here. The support route is through the forums. Only send by Private Message if specifically requested to do so

@sa2000 said:

@wpcorgan said:
Thank you very much @sa2000 … The next time when i restart PMS i will download the log files and then send you…
thanks again…

No - not send to me but attach in a post here. The support route is through the forums. Only send by Private Message if specifically requested to do so

Hi @sa2000 , my PMS crash this week 3 times, but today i can get the logs…

can you check please, and tell me what is the problem??? please im very sad for this…

thank you thabk you very much… this error was between 10:20 AM and 11:20 AM today…

thanks thanks thanks

Hi again @sa2000 . Again my PMS crash… 14:55 PM
here send you log files again… please help

@wpcorgan said:

@sa2000 said:

@wpcorgan said:
Thank you very much @sa2000 … The next time when i restart PMS i will download the log files and then send you…
thanks again…

No - not send to me but attach in a post here. The support route is through the forums. Only send by Private Message if specifically requested to do so

Hi @sa2000 , my PMS crash this week 3 times, but today i can get the logs…

can you check please, and tell me what is the problem??? please im very sad for this…

thank you thabk you very much… this error was between 10:20 AM and 11:20 AM today…

thanks thanks thanks

@wpcorgan said:
Hi again @sa2000 . Again my PMS crash… 14:55 PM
here send you log files again… please help

Thanks for the logs. They are not crashes as such but deadlocks causing a lockout for requests processing.

For deadlocks to be investigated we need process dumps as well as the logs adn also diagnostic request to get active connections

The steps i give below should be fairly easy to follow - if not please ask

The lockouts happened at 10:24 for the first one and 14:52 for the second.
It may be an idea to upgrade to the latest beta beforehand - version 1.13.2.5102

Diagnostics for a deadlock / lockout (Windows)

  1. Prepare yourself by finding the server security token string as it will be needed for the connections list request. To find the token string, see this support article https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
  2. When the problem occurs (and please wait for sufficient time before capturing diagnostics eg 10 minutes of requests to the server not getting through) , get the output from a specific browser request on the server. In a browser, go to this url http://localhost:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxx where you put the server token string instead of the xxxxxxxxxxxxxxxx. Copy the displayed output to a text file and save
  3. Next is to force a process dump for the Plex Media Server.exe process. We can do this with Windows Task Manager - but on a 64-bit windows and with Plex Media Server.exe being a 32-bit application, you would need to load the 32-bit x86 version of windows task manager. So load this program instead of the default task manager C:\Windows\SysWow64\Taskmgr.exe
  4. Using this 32-bit Taskmgr.exe find the Plex Media Server.exe process, select it and right click on it and choose Create Dump
  5. Check that the dmp file has been created
  6. Adding a new step because of recent deadlock investigations into one recent case, wait another 2 minutes and confirm that requests to the server home page (http://127.0.0.1:32400/web) do not get through and then repeat steps 2 to 5 (so we have 2 sets to compare)
  7. Restart the server and capture the zipped logs
  8. Zip the dmp files and upload to dropbox or similar service
  9. send me by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs

Thanks

@sa2000 said:

@wpcorgan said:

@sa2000 said:

@wpcorgan said:
Thank you very much @sa2000 … The next time when i restart PMS i will download the log files and then send you…
thanks again…

No - not send to me but attach in a post here. The support route is through the forums. Only send by Private Message if specifically requested to do so

Hi @sa2000 , my PMS crash this week 3 times, but today i can get the logs…

can you check please, and tell me what is the problem??? please im very sad for this…

thank you thabk you very much… this error was between 10:20 AM and 11:20 AM today…

thanks thanks thanks

@wpcorgan said:
Hi again @sa2000 . Again my PMS crash… 14:55 PM
here send you log files again… please help

Thanks for the logs. They are not crashes as such but deadlocks causing a lockout for requests processing.

For deadlocks to be investigated we need process dumps as well as the logs adn also diagnostic request to get active connections

The steps i give below should be fairly easy to follow - if not please ask

The lockouts happened at 10:24 for the first one and 14:52 for the second.
It may be an idea to upgrade to the latest beta beforehand - version 1.13.2.5102

Diagnostics for a deadlock / lockout (Windows)

  1. Prepare yourself by finding the server security token string as it will be needed for the connections list request. To find the token string, see this support article https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
  2. When the problem occurs (and please wait for sufficient time before capturing diagnostics eg 10 minutes of requests to the server not getting through) , get the output from a specific browser request on the server. In a browser, go to this url http://localhost:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxx where you put the server token string instead of the xxxxxxxxxxxxxxxx. Copy the displayed output to a text file and save
  3. Next is to force a process dump for the Plex Media Server.exe process. We can do this with Windows Task Manager - but on a 64-bit windows and with Plex Media Server.exe being a 32-bit application, you would need to load the 32-bit x86 version of windows task manager. So load this program instead of the default task manager C:\Windows\SysWow64\Taskmgr.exe
  4. Using this 32-bit Taskmgr.exe find the Plex Media Server.exe process, select it and right click on it and choose Create Dump
  5. Check that the dmp file has been created
  6. Adding a new step because of recent deadlock investigations into one recent case, wait another 2 minutes and confirm that requests to the server home page (http://127.0.0.1:32400/web) do not get through and then repeat steps 2 to 5 (so we have 2 sets to compare)
  7. Restart the server and capture the zipped logs
  8. Zip the dmp files and upload to dropbox or similar service
  9. send me by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs

Thanks

@sa2000 Thank you very much for responding … Tomorrow I will install the latest version, if the problem persists, I will make the second option.

THANKS!!!

@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

@wpcorgan said:
@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

Not necessary

@sa2000 said:

@wpcorgan said:
@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

Not necessary

HI @sa2000 , its me again…

1 week ago, exactly Sundat 27 May… i have installed the last PMS version…(1.13.2.5102)

All this week PMS works very very fine…i was very happy , and then I thought that the problem had been solved.

But few minutes ago apparently there was another deadlock, but im a not sure, because i cant see it in the logs files… can you tell me if the problem is the exactly same before (deadlock), because if it is the same error, , I will follow the second option (Diagnostics for a deadlock / lockout (Windows)

Thank you very much, i have attached log files… and thanks again.

@wpcorgan said:

@sa2000 said:

@wpcorgan said:
@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

Not necessary

HI @sa2000 , its me again…

1 week ago, exactly Sundat 27 May… i have installed the last PMS version…(1.13.2.5102)

All this week PMS works very very fine…i was very happy , and then I thought that the problem had been solved.

But few minutes ago apparently there was another deadlock, but im a not sure, because i cant see it in the logs files… can you tell me if the problem is the exactly same before (deadlock), because if it is the same error, , I will follow the second option (Diagnostics for a deadlock / lockout (Windows)

Thank you very much, i have attached log files… and thanks again.

Yes there was a deadlock starting about 12:18 but it is too late to collect any diagnostics as you restarted the server at 12:29

So next time please follow the steps for diagnostics for a deadlock

@sa2000 said:

@wpcorgan said:

@sa2000 said:

@wpcorgan said:
@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

Not necessary

HI @sa2000 , its me again…

1 week ago, exactly Sundat 27 May… i have installed the last PMS version…(1.13.2.5102)

All this week PMS works very very fine…i was very happy , and then I thought that the problem had been solved.

But few minutes ago apparently there was another deadlock, but im a not sure, because i cant see it in the logs files… can you tell me if the problem is the exactly same before (deadlock), because if it is the same error, , I will follow the second option (Diagnostics for a deadlock / lockout (Windows)

Thank you very much, i have attached log files… and thanks again.

Yes there was a deadlock starting about 12:18 but it is too late to collect any diagnostics as you restarted the server at 12:29

So next time please follow the steps for diagnostics for a dt

Thanks again @sa2000 , the last question… where in the log you can see (12:18 pm) that there was a deadlock???

here?? Jun 03, 2018 12:18:58.509 [9692] DEBUG - Stopping transcode session dafljy028k8r16ja7iwlvllu

thanks

@wpcorgan said:

@sa2000 said:

@wpcorgan said:

@sa2000 said:

@wpcorgan said:
@sa2000 thanks again, few minutes ago i have installed the last PMS version, and then i will tell you the PMS behaviour…

By the WAY… Need i have the all last windows 10 Update?

thanks again!

Not necessary

HI @sa2000 , its me again…

1 week ago, exactly Sundat 27 May… i have installed the last PMS version…(1.13.2.5102)

All this week PMS works very very fine…i was very happy , and then I thought that the problem had been solved.

But few minutes ago apparently there was another deadlock, but im a not sure, because i cant see it in the logs files… can you tell me if the problem is the exactly same before (deadlock), because if it is the same error, , I will follow the second option (Diagnostics for a deadlock / lockout (Windows)

Thank you very much, i have attached log files… and thanks again.

Yes there was a deadlock starting about 12:18 but it is too late to collect any diagnostics as you restarted the server at 12:29

So next time please follow the steps for diagnostics for a dt

Thanks again @sa2000 , the last question… where in the log you can see (12:18 pm) that there was a deadlock???

here?? Jun 03, 2018 12:18:58.509 [9692] DEBUG - Stopping transcode session dafljy028k8r16ja7iwlvllu

thanks

It is not just a log entry - but a build up of authenticated requests but requests not processed. Or requests logged but not completed.

Looking at the log file at this time shows a build up of an issue

Jun 03, 2018 12:17:50.337 [9788] DEBUG - Auth: authenticated user 1 as wpcorgan

The last successful completion of a request was at

Jun 03, 2018 12:17:45.413 [10184] DEBUG - Completed: [190.164.53.121:56612] 200 GET /photo/:/transcode?url=http%3A%2F%2F127.0.0.1%3A32400%2Flibrary%2Fmetadata%2F11401%2Fthumb%2F1526653421&width=298&height=439&upscale=1 (73 live) GZIP 138ms 8300 bytes (pipelined: 15)

and the (xx live) figure started to build up

Jun 03, 2018 12:15:36.598 [1652] DEBUG - Request: [190.164.53.121:56602 (WAN)] GET /library/sections/8/recentlyAdded?stack=1 (28 live) Page 0-19 GZIP Signed-in Token (eduandres1984)

28 only at this time - getting much higher later

So it is looking at the log file as a whole and getting a picture of what is happening over time

HI @sa2000 Today I woke up and then i can see in my PMS a new deadlock… then I followed all the steps and i have send you the request files… can you check please… (i have send you a private message)

thanks again !!!

@wpcorgan said:
HI @sa2000 Today I woke up and then i can see in my PMS a new deadlock… then I followed all the steps and i have send you the request files… can you check please… (i have send you a private message)

thanks again !!!

Thank you. Excellent diagnostics - thank you
I am referring it to the development team

The lockout occurred at around 02:56 am when and the load started to build up