84 replies to this topic

[Luke]

Can you please attach the emby server log? thanks.

 

@softworkz

[gruni]

Hi Luke,

I had to restart my QNAP in other reasons, so Emby server restarts as well. Now Emby server alive signal is working. Pioneer takes some seconds until Emby DLNA appears. 

It seems that alive signal needs a server restart and pioneer N-50a needs the DLNA alive signal.

I think you can close my pioneer/DLNA topic.

[Luke]

Thanks for the info.

[JAAlperin]

Been running Emby as a Warden plugin in FreeNAS for years.  Version 3.3.1.0 on FN 11.2 runs flawlessly on my OPPO BD-93 at home, but recently I tried to access my server from a remote ROKU.  Sorry, server version is too old.  So, installed 3.6.0.80 in an iocage jail.  Used Backup & Restore Plugin to configure as before.  OPPO no longer sees Emby without Blast Alive of 10 seconds, and then displays "Loading" forever.

 

2018-12-25 15:08:40.770 Info HttpServer: HTTP GET http://192.168.0.234...description.xml. UserAgent: OPPO PLAYER

2018-12-25 15:08:40.772 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 2ms. http://192.168.0.234...description.xml

2018-12-25 15:08:40.820 Info HttpServer: HTTP SUBSCRIBE http://192.168.0.234...irectory/events. UserAgent: 

2018-12-25 15:08:40.820 Info HttpServer: HTTP SUBSCRIBE http://192.168.0.234...nmanager/events. UserAgent: 

2018-12-25 15:08:40.821 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234...irectory/events

2018-12-25 15:08:40.821 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234...nmanager/events

2018-12-25 15:09:01.724 Info HttpServer: HTTP GET http://192.168.0.234...ons/logo240.png. UserAgent: 

2018-12-25 15:09:01.725 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234...ons/logo240.png

2018-12-25 15:09:03.020 Info HttpServer: HTTP POST http://192.168.0.234...rectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.076 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 56ms. http://192.168.0.234...rectory/control

2018-12-25 15:09:03.226 Info HttpServer: HTTP POST http://192.168.0.234...rectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.237 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 11ms. http://192.168.0.234...rectory/control

2018-12-25 15:09:03.357 Info HttpServer: HTTP POST http://192.168.0.234...rectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.379 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 22ms. http://192.168.0.234...rectory/control

 

The Post and response sequence repeats until cancelled.

 

I've checked that the OPPO profile is the same on both systems.

 

Any suggestions would greatly appreciated.

[softworkz]

The problem is most likely due to another DLNA service running on your NAS device.

 

Normally co-existence wouldn't be a problem, a you've seen with Emby 3.3.

 

But there's been a regression in the .net core framework since .net core version 2.1 and it persists in version 2.2. 

Emby 3.3 used .net core 2.0 (or maybe MONO) where this problem didn't exist.

Unfortunately there's nothing we can do about it. MS has already fixed this for .net core 3.0, but it's not yet released.

 

Your only option at this time is to disable the other DLNA service on your device.

Edited by softworkz, 25 December 2018 - 09:22 PM.

[JAAlperin]

Thank you softworkz.

 

However, Emby is the only DLNA server running on FreeNAS or anywhere else on my network.  I've searched from the OPPO and other devices for media servers and only see Emby.

[softworkz]

So you are seeing Emby. 

 

Which Emby are you seeing? The 3,3 version? Or the 3.6.80 version? Are you running both at the same time?

 

BTW, what is an "iocage jail" ?

[JAAlperin]

Jails are a FreeNAS mechanism for encapsulated virtual machines.  FreeNAS is transitioning from warden jails to iocage jails.  The technical differences would require more conversation than I think worthwhile here.  The latest version, FreeNAS 11.2, supports both, but future versions may not.

 

I have had Emby 3.3.1.0 installed in a warden jail for many months, and 3.6.0.80 installed in an iocage jail for two days.  I run one or the other, but not both at the same time.

 

3.3 supports my OPPO BD-93 flawlessly.  On 3.6 the OPPO reports "Loading" forever.

 

Thank you for your continued interest and help.

[softworkz]

Thanks for the explanation. I don't know the virtualization techniques on FreeNAS, but there's a chance that the binding from one 'cage' remains active on the host even when after the guest has stopped.

 

As mentioned before, this shouldn't be a problem normally, but it is with the current .net core runtimes.

If there's some way to make 100% sure that there's no leftover binding - I can't tell.

Maybe you could try to fully disable the 'cage' containing Emby 3.3, restart the system and start the 3.6 version then.

 

Please also post a log from the 3.6 version so we can be sure that it's not some other problem.

[JAAlperin]

No chance that there is still a binding.  I have also rebooted FreeNAS in between uses of 3.3 and 3.6.

 

A Roku and a WD TV Live can browse 3.6  Only the OPPO has been disturbed.

 

Regarding posting log, I sort of did so in my initial post.  Note that the OPPO seems to make the same request (and receive the same data) to eternity.  Posting another log will just give you more entries like the last two pasted in.

[softworkz]

Regarding posting log, I sort of did so in my initial post.  Note that the OPPO seems to make the same request (and receive the same data) to eternity.  Posting another log will just give you more entries like the last two pasted in.

 

I don't want to see more of those entries, I want to see the full log from startup until the problem occurs.

[JAAlperin]

Restarted Emby 3.6.0.80.  On OPPO selected My Network - got "Loading" for maybe 30 seconds, then Emby showed up.  That sequence is instantaneous on 3.3.  Next, clicked on Emby (to browse) - got "Loading" for a minute or two, then I cancelled (would never end).  That sequence takes one or so seconds on 3.3.  Three logs are below.

 

Thanks again for your help.

Attached Files

•  embyserver-63681437368 20181226 1609.txt   422.42KB   3 downloads
•  hardware_detection-63681437377 20181226 1609.txt   92.5KB   0 downloads
•  embyserver 20181226 1612.txt   1.72MB   2 downloads

Edited by JAAlperin, 26 December 2018 - 05:33 PM.

[softworkz]

Thanks for positing the logs.

 

This seems to be a different problem than the one I suspected.

 

@Luke - any idea regarding the dlna communication?

[Luke]

I'm not sure. There's probably some issue with older devices. I'll have to test on all the devices i have available to see if i can reproduce. Thanks.

[JAAlperin]

I'll be happy to test (if you suggest something).

 

Would my custom profile information be of use?

 

By any chance can you make available the old Roku Emby app that used to work with 3.3.1.1 (the new app tells me that my server version is too old)?

[JAAlperin]

Anything further gentlemen?

 

If I stay on 3.3 my friends and family can no longer access my Emby server (Roku Emby app reports server is too old).

 

If I go to 3.6 I can not access Emby from my OPPO BDP-93 (an old, but otherwise excellent device).

 

I've experimented with changes to the user profile for the OPPO, but have still not successfully connected BDP-93 to 3.6.0.80.

[Luke]

Not yet. I don't think the profiles will matter.

[DenysR]

I still have the same problem on my roku. Sony TV
Host name or URL

[Luke]

I still have the same problem on my roku. Sony TV
Host name or URL

 

Please see my response elsewhere to you:

https://emby.media/c...erver/?p=669776

[DenysR]

So what kind of service?? do I need to get emby on my roku.
Thnks for your help