FAQ  •  Register  •  Login

Serviio not working on Mac OS X Mountain Lion 10.8.4

<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Fri Dec 27, 2013 8:57 pm

Serviio not working on Mac OS X Mountain Lion 10.8.4

I have a desktop Macintosh Pro 4,1 (early 2009). Previously I was running OS X Lion 10.7.5.
Both Serviio 1.3.1 and Serviio 1.4 work properly with my Toshiba REGZA 55SL500U.

I have now transitioned to OS X Mountain Lion 10.8.4. I can launch either version of Serviio server and console.
But now the TV does not seem to be able to connect to the server. When I use the TV controller to select the media player
it does display the name of the device: LAN-S: Serviio (Gandalf.local).

Previously on Lion this did not happen; instead I got to select the media player and then Photos, Movies, Music, etc

The Toshiba TV software installed as of 2011/09/16 is version 9.2.48.0 11 Jan 2011 15:19:55
The IP address for the TV is correct and has not changed from the prior OS X Lion release.
My Java version 1.6.0_35. SE Runtime Environment (build 1.6.0_35-b10-4.28-11M384, HotSpot 64-bit Server VM build 20-10=bo1-428, mixed mode.)

This smells to me like a DLNA problem in Mountain Lion - what do you think?

What should I do to try and help track this down?
Has anyone else run into this?

Thanks...

Peter
Mac Pro OS X Lion, Toshiba 55SL500U
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Sat Dec 28, 2013 2:10 am

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

Previously I said this:
"This smells to me like a DLNA problem in Mountain Lion - what do you think?"

Actually on reflection I'm not sure that's the issue. The DLNA protocol must in fact be implemented by Serviio server and the Toshiba TV.
And the packets are sent over the Ethernet cable from the Mac to the TV.

What's puzzling to me is why things work on OS X Lion 10.7.5 but not on OS X Mountain Lion 10.8.5.
The only thing that's changed is the Mac OS X version.

Is there some way we can log the dialog between the two devices to examine what's going on?
Then I could run both 1.3.1 and 1.4 on Lion and Mountain Lion to see if there's a difference.
Or am I going to have to learn Wire Shark? I sure hope not.

respect

Peter
Mac Pro OS X Lion, Toshiba 55SL500U
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Sat Dec 28, 2013 10:34 pm

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

One difference that I've found out is in the versions of Java.
Lion
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)

Mountain Lion
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

Why would thus make a difference?
Mac Pro OS X Lion, Toshiba 55SL500U
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Sun Dec 29, 2013 12:08 am

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

I turned on DEBUG in both the Server and the Console.
From my reading of the logs it's related to the UPNP device not being available. (copied from below log extracts)
2013-12-28 18:38:07,782 DEBUG [DiscoveryManager] UPNP device b417b37c-4030-3c89-bb6e-b5e8798e235b (192.168.2.10) is unavailable
But that device is my Mac at en0 IP 192.168.2.10 (a.k.a. Gandalf). The TV is at 192.168.2.15. Both of these are the same addresses as before.

What to do next? Log extracts follow.

Peter

There are 3 server logs listed in date/time created and named serviio.log.2, serviio.log.1, and serviio.log.
If I understand them correctly the issue is the related to these extracts from the logs:
From log 2
2013-12-28 18:32:41,978 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-12-28 18:32:41,982 INFO [RendererExpirationChecker] Starting RendererExpirationChecker
2013-12-28 18:32:41,982 INFO [RendererSearchSender] Searching for Renderer devices
2013-12-28 18:32:41,983 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,984 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,995 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2013-12-28 18:32:41,995 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,996 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:32:43,818 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:08 (advertisement duration is 1800 sec.)
2013-12-28 18:32:47,997 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2013-12-28 18:32:51,998 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:51,999 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:32:53,818 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:08 (advertisement duration is 1800 sec.)
2013-12-28 18:33:01,999 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:33:02,000 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:33:03,820 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:03:24 (advertisement duration is 1800 sec.)

and from the last log
2013-12-28 18:32:41,978 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-12-28 18:32:41,982 INFO [RendererExpirationChecker] Starting RendererExpirationChecker
2013-12-28 18:32:41,982 INFO [RendererSearchSender] Searching for Renderer devices
2013-12-28 18:32:41,983 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,984 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,995 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2013-12-28 18:32:41,995 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:41,996 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:32:43,818 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:08 (advertisement duration is 1800 sec.)
2013-12-28 18:32:47,997 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2013-12-28 18:32:51,998 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:32:51,999 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:32:53,818 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:08 (advertisement duration is 1800 sec.)
2013-12-28 18:33:01,999 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-28 18:33:02,000 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-28 18:33:03,820 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:03:24 (advertisement duration is 1800 sec.)

also
2013-12-28 18:38:07,782 DEBUG [WebServer] Socket closed
2013-12-28 18:38:07,782 DEBUG [DiscoveryManager] UPNP device b417b37c-4030-3c89-bb6e-b5e8798e235b (192.168.2.10) is unavailable
2013-12-28 18:38:07,783 INFO [WebServer] WebServer shutting down
2013-12-28 18:38:07,783 INFO [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier

and finally
2013-12-28 18:38:07,784 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP byebye using interface en0 (en0) and address 192.168.2.10, timeout = 0
Mac Pro OS X Lion, Toshiba 55SL500U
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Sun Dec 29, 2013 8:38 pm

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

The problem is that Serviio is not able to find the Renderer (TV with DLNA) under Mountain Lion.
To discover this I ran version 1.4 on Lion (OS X 10.7.5) and Mountain Lion (OS X 10.8.4) with DEBUG set on the Serviio server.
I then searched the logs and on Lion followed the handshaking and founf this message:
2013-12-29 15:07:55,732 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.2.10:60176s
2013-12-29 15:07:55,748 DEBUG [RendererManager] Adding renderer Renderer [uuid=7728bbf4-a04d-11de-9850-e89d871c7e0e, ipAddress=192.168.2.15, name=55SL500U, profileId=13, manuallyAdded=false, forcedProfile=true, enabled=true, accessGroupId=1] to list of active renderers

but on Mountain Lion no such message. Instead got these:
2013-12-29 15:23:11,387 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-12-29 15:23:11,391 INFO [RendererExpirationChecker] Starting RendererExpirationChecker
2013-12-29 15:23:11,391 INFO [RendererSearchSender] Searching for Renderer devices
2013-12-29 15:23:11,393 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-29 15:23:11,393 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-29 15:23:11,406 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2013-12-29 15:23:11,452 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface en0 (en0) and address 192.168.2.10, timeout = 0
2013-12-29 15:23:11,453 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device b417b37c-4030-3c89-bb6e-b5e8798e235b
2013-12-29 15:23:13,274 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:08 (advertisement duration is 1800 sec.)
2013-12-29 15:23:17,408 DEBUG [RendererSearchSender] Finished searching for Renderer devices

So the problem is the Serviio server is not able to find the Renderer under Mountain Lion but is able to do so on Lion.

How to proceed?

Peter
Mac Pro OS X Lion, Toshiba 55SL500U
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 14395

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Fri Jan 03, 2014 11:30 am

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

Might be some firewall issue. Serviio advertises itself (m-search message), but the Renderers don't respond. So either the m-search message didn't get through or any response didn't get through.
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Sat Jan 04, 2014 9:34 pm

Re: Serviio not working on Mac OS X Mountain Lion 10. SOLVED

Bingo!! That was it. For the record:

To check things I booted into Lion.
In OS X Lion 10.7.5 the System Preferences Security Firewall Options settings DID HAVE a checkmark in the box to
"Automatically allow signed software to receive incoming connections"
and there was NO checkmark in the box to
"Enable stealth mode"

In OS X Mountain Lion 10.8.5 this is reversed.
I did not change these settings so they must be from the original install.

I have now explicitly allowed Serviio and Serviio Console to Accept incoming connections.
They did show up as items in the Firewall Options settings.

Out of curiosity is Serviio signed? I noticed Skype is allowed incoming connections and I sure didn't do anything to permit that.
Although it's OK with me as I have only used it twice in my lifetime the 2nd time last week.
Mac Pro OS X Lion, Toshiba 55SL500U
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 14395

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Mon Jan 06, 2014 8:23 am

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

Serviio is signed, but maybe they mean SW coming from their marketplace.
<<

pteeson

Streaming enthusiast

Posts: 26

Joined: Mon Sep 19, 2011 6:29 pm

Location: Toronto, Canada

Post Mon Jan 06, 2014 11:34 pm

Re: Serviio not working on Mac OS X Mountain Lion 10.8.4

ROFL.... Apple is quite a control freak. Sort of like a helicopter mother I guess. Oh well things are working now so I'll get back to playing. Thanks.
Mac Pro OS X Lion, Toshiba 55SL500U

Return to Toshiba

Who is online

Users browsing this forum: No registered users and 1 guest

cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.