Cannot remove server & Roku reboots on playback

[xaneth 5]

Good morning,

 

I'm having an issue with my Roku with Emby running on Arch.  My Arch server is running on a virtual machine, but it's enterprise class running on an HP server with 2 quad core CPU's (8 cores), and 32GB RAM running VMWare ESXi 4.1.  Server specs are:  4GB RAM, 4 CPU, 20GB HDD.

 

I'm pretty sure I'm dealing with a problem on the Roku mostly.  Two part question here.  When I go into 'Change Server', I see my Emby server listed twice.  When I try to 'Remove server' and confirm, it kicks me to the screen where it asks to login as one of my users.  The server will not delete.  Here is a log I captured from the Roku using the Roku telnet app:

 

Top of stack is once again: roListScreen ChangeServer
Not sure what to do with breadcrumbs on screen type: Invalid
Pushing screen 7 onto view controller stack - Dialog: Confirm Action
Creating new dialog
Button pressed: 1
Popping screen 7 and cleaning up 0 breadcrumbs
Top of stack is once again: roListScreen ChangeServer
Remove Server
Using broadcast address 192.168.1.255
Send To Address: 192.168.1.255:7359 / 192.168.1.255:7359
Received Message: {"Address":"http://192.168.1.35:8096","Id":"4ea0a0aff11f4c3f81ab33a672fb9896","Name":"Jason's Emby Server"}
Found 1 servers
Connect returned 0 servers
connectionManagerGetServers returning 1 servers
connectToServers called with 1 servers
Attempting to connect to http://192.168.1.35:8096/emby/system/info/public?format=json
connectInitial returned State of ServerSignIn
connectInitial returned ConnectionMode of Local
Processing ConnectionResult State of ServerSignIn
ServerSignIn Id: 4ea0a0aff11f4c3f81ab33a672fb9896
ServerSignIn Name: Jason's Emby Server
ServerSignIn LocalAddress: http://192.168.1.35:8096
ServerSignIn RemoteAddress: http://myinternetdnsserver.net:80
ServerSignIn ManualAddress: 
Pushing screen 8 onto view controller stack - Login
getPublicUserProfiles url: http://192.168.1.35:8096
Showing screen with 17 elements

Second question is, after I log in and try starting a movie, it tries to load the movie, and at around 5-10% the Roku reboots.  About the only log I can get when this happens is:

 

Starting to play transcoded video
Playback url: http://192.168.1.35:8096/emby/videos/0dc218a699a9e1312053b9b2605c0c94/master.m3u8?DeviceId=4E652G004983&MediaSourceId=0dc218a699a9e1312053b9b2605c0c94&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=1&VideoBitrate=3072000&AudioBitrate=128000&MaxAudioChannels=2&MaxFramerate=30&MaxWidth=1920&MaxHeight=1080&Level=41&ClientTime=635831768463270800&MaxRefFrames=12&MaxVideoBitDepth=8&Profile=high&PlaySessionId=8a21e6dba6f047a9a61e47a9a39b6b45&api_key=37e0af29b08f443e86aac4aba6d5509a
Connection closed by foreign host.

To note, I have a second Emby server that I was using previously, running on CentOS 6.7 with the same VM specs.  The experience is much faster, and CPU usage is much lower during playback, usually around 40-50% with even a couple users streaming at once.  The Arch server was pegging the CPU at 100% with even one client, and response from the Emby menus was very slow.  Some channels could not even load on the Arch server, such as Jupiter Broadcasting.

 

So I know this is a two part problem, Emby server or Roku?  And it looks like most it points to the Roku itself, especially the reboots, because it happens on both servers, CentOS or Arch.  Thanks in advance for any help!

Edited November 15, 2015 by xaneth

[xaneth 5]

OK, got done building out an Ubuntu 14.04 server with all the same specs, and when playing back 3 streams from different locations, I'm seeing around 200% CPU usage, which breaks down to around 50% for each core.  That's what I was seeing before, and it's acceptable resource usage.  The menus are much faster, etc.  So I think I'll stick with Ubuntu or CentOS rather than Arch.  I like Arch as I use it on my main desktop here.

 

Another note, I'm configuring all these VM's with the same hostname and IP address, shutting down the others during use of course.

 

I think my Roku problems are local no the Roku itself.  Going to try and find a way to factory reset it and start over.

[xaneth 5]

Reset to factory defaults on the Roku and it's still having the same issues.  After factory reset, however, it already had my previous channels on it, including the Emby channel, so the problem I'm having may have migrated with it.  Wish there was a way to FULLY reset it.  I'm just going to have to live with Plex on my Roku.  However Emby works find over a browser as well as my Android tablet, so I'll stick with it there.

 

Think I'll stick with Ubuntu 14.04 LTS for the server as it's relatively low CPU usage.  Plex on the other hand will max out at the 200% (50% per core) when the streaming starts, and then falls back to a nice 1-2% usage.  Using the 'top' command in Linux to see usage stats.

[Luke 42077]

A couple people have reported this after the roku os7 update but we're unable to reproduce. We'll keep testing

[xaneth 5]

Thanks.  I don't recall updating my Roku except when I got it out of the box around a month ago.  Emby has been working fine on it up until the server change.