Jump to content
justwondering

ANSWERED Emby Server on Raspberry Pi crashing

Recommended Posts

Luke

Thanks for the info.

Share this post


Link to post
Share on other sites
widget100

Ok, I have some good news. Your previous DLNA theory looks like it's correct.

 

I disabled Enable DLNA server  and Blast alive messages and got no Abrt/6 overnight and no hangs during today at all.  Been up since 21.44 last night. Hopefully the OP on this thread can try the same test?

 

i also tried to disable Enable automatic port mapping but every time I uncheck it, save and change screens it re-checks the box, so you still have that bug.

 

Also my logs are flooded with the following. I saw in another thread that this had been previously fixed - any ideas on how to supress it?

2018-07-19 17:15:16.814 Error Dlna: Error in BeginListeningForBroadcasts	*** Error Report ***	Version: 3.5.0.0

Share this post


Link to post
Share on other sites
Luke

Thanks but what bug about port mapping? the config screen seems to work fine in my testing.

Share this post


Link to post
Share on other sites
Luke

When you uncheck that setting you get a dialog box. It sounds like you didn't click the button in the dialog box.

Share this post


Link to post
Share on other sites
widget100

Just tried again on both FF and Chrome.  Uncheck the box, no dialog, just the unchecked box with a green shaded circle. Hit Save, screen pops up saying Hosting Settings - Changing these values may cause instability or connectivity failures, (URL is http://192.168.1.21:8096/web/index.html#!#dlg1532025674799)  Hit Got It, second screen pops up saying Hosting Settings, To enable HTTPS for external connections etc, hit Got It.

 

Box appears unchecked. switch to another menu item, back to advanced and the box is checked again.

Share this post


Link to post
Share on other sites
Luke

You need to disable secure connections if you haven't provided an SSL cert. that's why your settings aren't saving.

Share this post


Link to post
Share on other sites
widget100

Well that's not exactly obvious is it :rolleyes: 

 

Was set to Preferred but not required,  set disabled and it saves as you say. It's not clear that those settings are in any way related.

 

Just the logs flooding with this every min or so now and we'll be set and I'll go and leave you in peace :P

2018-07-19 18:49:16.812 Error Dlna: Error in BeginListeningForBroadcasts	*** Error Report ***	Version: 3.5.0.0	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb	Operating system: Unix 4.14.52.7	64-Bit OS: False	64-Bit Process: False	User Interactive: True	Processor count: 4	Program data path: /var/lib/emby	Application directory: /opt/emby-server/system	System.Net.Sockets.SocketException (98): Address already in use

Share this post


Link to post
Share on other sites
justwondering

Sorry I've been missing. Still getting the same crashes, when idle and during playback. I missed the theory about DLNA and I don't see that in the thread. Was that discussed somewhere else?

 

I've gone ahead and disabled "Enable Dlna server" and "Blast alive messages" from the "DLNA" pane under "Devices".  I don't see "Enable DLNA Play To" mentioned, and it is checked by default, so I'm leaving that. Please let me know if it would be useful to check "Enable DLNA debug logging" too.

 

I also set "Secure connection mode" to "Disabled" in the "Advance" pane under "Expert", and unchecked "Enable automatic port mapping".

 

Let me know if I missed anything, or if there's anything else I should try. Thanks!

Share this post


Link to post
Share on other sites
Luke

It was a defect in the last release which is now resolved and won't happen anymore for new users.

Share this post


Link to post
Share on other sites
widget100

Sorry I've been missing. Still getting the same crashes, when idle and during playback. I missed the theory about DLNA and I don't see that in the thread. Was that discussed somewhere else?

 

I've gone ahead and disabled "Enable Dlna server" and "Blast alive messages" from the "DLNA" pane under "Devices".  I don't see "Enable DLNA Play To" mentioned, and it is checked by default, so I'm leaving that. Please let me know if it would be useful to check "Enable DLNA debug logging" too.

 

I also set "Secure connection mode" to "Disabled" in the "Advance" pane under "Expert", and unchecked "Enable automatic port mapping".

 

Let me know if I missed anything, or if there's anything else I should try. Thanks!

 

 

 

The DLNA theory was something Luke suggested to me on my original thread about crashes during scanning of libraries (which goes away if you mount the folder and scan it rather than just using SMB paths as \\192.168.1.x.\media\music)

 

I've got Enable Play To still checked as well, and it's been rock solid all day. Don't think you need to uncheck the Enable Auto Part Mapping, that was a hangover from a previous thread.

 

I'm going to add TVH and a couple of other plugins back now and hope it all hangs together.

 

Thanks again Luke.

Edited by widget100

Share this post


Link to post
Share on other sites
Luke

if all you've disabled is the dlna server then that's going to eliminate some periodic broadcasts advertising the server on your network, and will eliminate some communications from other devices on your network. we should give it more time to be sure it's not a fluke.

Share this post


Link to post
Share on other sites
Luke

The issue could also be that our blast alive interval is just way too aggressive. What you could try is turning the dlna server back on, but then set the blast interval to 1800 (30 minutes). Then restart the server.

 

I'm going to make some changes here and make that our default anyway, it will be in the next beta.

Share this post


Link to post
Share on other sites
widget100

I'll run as I am overnight and if nothing crashes I'll set the blast interval on and 30 mins as you suggest. As I am at the moment I've not had a crash or hang in 23 hours.

 

I'm not sure if you answered about the Error Dlna: Error in BeginListeningForBroadcasts/System.Net.Sockets.SocketException (98): Address already in use.

Was your response that it was a defect in a previous release and doesn't happen to new users? It's certainly happening to me and I'm new :)

 

Should i reinstall from scratch or is there something else I can do to nuke that error.

Share this post


Link to post
Share on other sites
Luke

No i meant that about the config page. I am not yet sure about the dlna error. Sometimes there are certain things that are device specific and they take a little longer to chase down.

Share this post


Link to post
Share on other sites
widget100

Crashed with abrt/6 within an hour of re-adding TVH and Playback reporting plugins. Tried to enable Blast interval of 30 mins but max in the field is 300 seconds.

 

Removed plugins again and rebooted. I'll see how it goes.

Share this post


Link to post
Share on other sites
justwondering

Disabling the DLNA server, blast alive, and automatic port mapping seems to have done the trick. Since then I've had no crashes or hiccups of any kind, during playback or while idle.

 

I don't need DLNA, so for the moment my problem is solved. If you'd like me to check anything else, please let me know. Thank you for your help, and for making a great media player!

Share this post


Link to post
Share on other sites
Luke

Thanks for the feedback.

Share this post


Link to post
Share on other sites
widget100

Same here. Added the TVH plugin back yesterdaya and it's still rock solid running 3.6.0.2.

 

I'm going to try switching the DLNA stuff back on now with blast at 1800 seconds and see how I fare.

Share this post


Link to post
Share on other sites
Luke

Glad to hear it.

Share this post


Link to post
Share on other sites
widget100

Fell over 7am with 11/segv whilst idle. Turned on debug logging now as there was nothing in the logs to show why. I'll come back with more info next time.

Share this post


Link to post
Share on other sites
Luke

Thanks for the info.

Share this post


Link to post
Share on other sites
widget100

Ok been running 3 days with debug logging on and I've had one glitch where it hung whilst playing to the TV across DLNA but since the SSH session I had open to the Pi dropped at the same time I cant level  that at Emby. so I think we can call it fixed with the new blast setting.

 

The only issue I still have is the following

2018-07-26 00:01:07.520 Error Dlna: Error in BeginListeningForBroadcasts	*** Error Report ***	Version: 3.6.0.2	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb	Operating system: Unix 4.14.52.7	64-Bit OS: False	64-Bit Process: False	User Interactive: True	Processor count: 4	Program data path: /var/lib/emby	Application directory: /opt/emby-server/system	System.Net.Sockets.SocketException (98): Address already in use

If you could put some code in there to report on exactly what is conflicting we'd be golden :)

Share this post


Link to post
Share on other sites
Luke

Thanks for the info.

Share this post


Link to post
Share on other sites
widget100

Unfortunately it was short lived and had a hang and a crash in the past 24 hours.

 

Good news though is I have logs which actually show something this time - this from syslog and the attached.

 

Jul 31 01:52:06 raspberrypi emby-server[30957]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0x74902330 ***

Jul 31 01:52:07 raspberrypi tvheadend[643]: htsp: 127.0.0.1 [ widget100 | TVHclient4Emby-3.6.0.2 ]: Disconnected

Jul 31 01:52:07 raspberrypi systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT

Jul 31 01:52:07 raspberrypi systemd[1]: emby-server.service: Unit entered failed state.

Jul 31 01:52:07 raspberrypi systemd[1]: emby-server.service: Failed with result 'signal'.

 

 

Log.txt

Share this post


Link to post
Share on other sites
Luke

Try removing the tvheadend plugin.

Share this post


Link to post
Share on other sites

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...