This is re-producible. When using the latest PMS 1.25.6.5577 on Nvidia Shield. Using hauppauge TV tuner which supports two streams at once, if you then start a third stream, it crashes PMS rather than displaying a dialog box which asks if you’d like to stop a certain stream and continue the new one. Anyone able to re-produce?
Is this video streams or audio streams ? and what are the steps to reproduce
Would like debug server logs to see what is going on. Please indicate times / channels / streams selected
Will grab logs next time I can but it happens every time.
Using the hauppauge TV tuner start a TV stream of a channel, let’s say BBC1, channel 101.
On a laptop, in Plex web, signed into the same account, start BBC2, channel 102, so you now have two streams of the same channel. This is the maximum my particular hauppauge tuner supports.
On another laptop, in Plex web, try and start a third stream of ITV, channel 103, and PMS crashes on the shield and on all devices playing. It quickly restarts, but no message shows asking to stop one particular channel.
Logs will be grabbed next time but can you produce this on your side as well?
@sa2000 please find attached logs.
14:27 is the time and this is the sequence started:
Nvidia Shield - Starting Channel 101
Plex Web - Starting Channel 102
Android Phone - Starting Channel 103
As soon as the android phone started Channel 103 (which exceeds number of tuners) PMS crashes and all devices stop playing. If there was a recording, all recordings fail as PMS crashes.
Please also see this thread with the same issue. Plex server crashing with live tv
I can’t see a crash as such but it is obvious the server was restarted - so probably the shield force closed the PMS process and restarted it
I have tried to reproduce the problem but encountered other issues relating to multiple DVR sources (i have several servers running with DVRs) and I have referred these issues to the android app development team - I am not sure if related to your issue
Is the problem reproducible ?
Are you able to enable developer options on the Shield and use adb to get a logcat ?
That would show if we have memory issues on the Shield forcing the server to be closed
If it is reproducible and even if we do not get the logcat, could you repeat it and have network logging enabled on the app and then fetch the network log from the app - through
http://192.168.1.11:32500/logging
and copy it to text file and provide it with the server logs again and the steps
Attached logs. Same sequence as before:
Nvidia Shield - Starting Channel 101
Plex Web - Starting Channel 102
Android Phone - Starting Channel 103
Sequence started at 13:14. Network logs grabbed straight away. Server logs grabbed after a restart of the Shield to get PMS back. Let me know if you need anything else. Don’t think logcat will be possible.
Plex Media Server Logs_2022-03-14_13-17-46.zip (1.8 MB)
PMS crash network logs.txt (4.3 MB)
@sa2000 did these logs help?
I am sorry - I only work on Plex part time. Will have a look today
Logs are showing the /tune requests for
101 BBC One HD (England)
102 BBC Two HD
and then
103 ITV1 HD (Meridian, Anglia)
This 3rd request was logged at Mar 14, 2022 13:15:09.636
and whilst it was being handled by Plex Media Server - the Plex Media Server seems to have got restarted at Mar 14, 2022 13:15:15.729
Not sure why - there is no log lines to show the process being killed
If memory usage gets high, the Shield may shutdown the process and restart it
I have repeated my test on the Shield with the beta release 1.25.8.5621-7a6fed0cf
And after having both channel 1 and 2 streaming on the shield and plex web - i started ITV on an android phone and it failed as expected with “All Tuners are currently in use” error screen
There were some strange logging in your logs which i cannot explain
It shows Plex Media Server was active from 28th February but dormant - and then coming to life on the 14th March - but the way the logs were updated suggests that may be at some point there were two instances of Plex Media Server running
So try to see if update to the beta and reboot the shield itself to clear old dormant processes and see if the issue remains
Edited: Removed references to LogMemoryUse - it appears that it is not available for the Shield. Sorry.
I have compared your logs with mine after the 3rd request to tune comes in and the logs are similar with failure to allocate a tuner - the only difference is that in your case the server process got restarted - so could be memory use was high.
I will follow up the memory use logging - it appears not to be available for the SHIELD
If it is memory issues - it could be to do with the number of scheduled recordings as for each tune request we go through all the schedule
Thank you @sa2000. I’m not at home so tried to start three channels all through Plex web. On the 3rd channel the correct message popped up. This is running the beta. So maybe something in there changed and now all works as normal.
Thanks for the feedback - hope it has gone away - but if the issue is memory usage related and the PMS proceess killed by nVidia Shield OS then we will need logcat and Android ADB access to the shield to get the logcat with the server and android app logs
Hope it won’t come to that
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
