OS X Remote Communication Server Failed to start
#1
OSX Version: 10.7.3
Platform: iMac
Install Method: DMG
SVN Revision: XBMC 11.0 Git:20120321-14feb09
FULL Debug Log: http://pastebin.com/TKgreh8p

Ever since I upgraded to Eden, I've been seen this message with a big yellow exclamation mark every time I start up XBMC:

Remote Communication Server
Failed to start

Everything actually works fine, so I have just lived with this up to now. But it is annoying, so I'd really like to put an end to it.

I have tried searching for this problem (when I search for 'Remote Communication Server Failed to start' I get just 5 hits), but I haven't been able to find any helpful answers so far.

Basically this is a problem that began with XBMC 11... it never happened in XBMC 10.

So can anyone help? If so please be patient with a non-techie (and at least credit me with reading the READ THIS 1st BEFORE POSTING thread before posting, hence all stuff at the start of this message!)... Thanks.
Reply
#2
One of the ports XBMC is trying to use is in use by another process.

from your log:

18:50:58 T:2895528640 ERROR: JSONRPC Server: Failed to bind serversocket

If you are running sabnzb / Squeezebox they use port 9090 and will cause this error.

You need to change the port numbers on sabnzb or squeezebox to something other than 9090.




Reply
#3
Thanks for your help... but I'm afraid I have no idea what sabnzb or Squeezebox is. I don't think I have ever installed these things (at lest I don't remember doing so!) and I don't know how to change the port numbers on these things.

Is there a way to get a list of everything on my system that is using these port numbers?

It would also be great to know what it was about this line in the log that led you to this conclusion (I can't find any mention of port 9090 or anything else you have mentioned in the log file)... if I understood that I would be better able to sort things out myself next time!

XBMC is a great piece of software, but it has to be said that when it doesn't work right it's practically impossible for anyone without a PhD in Advanced Techicity to fix things!
Reply
#4
(2012-06-05, 17:40)Korey Wrote: One of the ports XBMC is trying to use is in use by another process.

from your log:

18:50:58 T:2895528640 ERROR: JSONRPC Server: Failed to bind serversocket

If you are running sabnzb / Squeezebox they use port 9090 and will cause this error.

You need to change the port numbers on sabnzb or squeezebox to something other than 9090.

I am getting this issue as well. Create a shell script and put the following in it:
Code:
#!/bin/sh

killall XBMC XBMCHelper
open "/Applications/XBMC.app"
sleep 5

Now using the program launcher, launch the shell script. The "sleep" statement causes XBMC to repport:

Remote Communication Server
Failed to start

Why? Besides that the Apple remote won't function. I understand why the Apple remote is not functional. But why is the communication error happening?

You can do the same thing in XBMC 10.1 and none of that happens. I need to use a shell script that requires the killing off of XBMC and then restarting it and I get the issue.
Kodi 17, Transparency Skin
PogoPlug v4 running Arm Linux 4.4.63 as MySQL (mariadb) server.
Mac OS 10.12.5
2015 27" iMac 3.3 GHz Quad, 16GB RAM, 1TB SSD
2015 13" Macbook Pro, 8GB RAM, 256GB SSD
AppleTV 4 TV OS 10
Reply
#5
(2012-06-05, 19:09)4square Wrote: Is there a way to get a list of everything on my system that is using these port numbers?

It would also be great to know what it was about this line in the log that led you to this conclusion (I can't find any mention of port 9090 or anything else you have mentioned in the log file)... if I understood that I would be better able to sort things out myself next time!

Paste this in terminal, it will show you what ports are in use.

sudo lsof -i -P | grep -i "listen"

it will ask you for your password.


As far as knowing that it is port 9090:

"third-party applications can access XBMC's JSON-RPC API by opening a TCP socket on port 9090 (this port can be configured in the advanced settings file) and sending raw JSON-RPC requests over that socket."

taken from this page: http://wiki.xbmc.org/index.php?title=JSON-RPC_API#TCP
Reply
#6
(2012-06-05, 17:40)Korey Wrote: If you are running sabnzb / Squeezebox they use port 9090 and will cause this error.

You need to change the port numbers on sabnzb or squeezebox to something other than 9090.
Some BitTorrent clients use 9090 as well. You can change the port number XBMC uses for this in the advanced settings.
Reply
#7
For me it was Mobile Mouse server
I'm a lurker, not a fighter!
Reply
#8
It was Mobile Mouse for me too!
Thanks
Reply
#9
I am having this same/but different problem. I currently have a Mac Mini (Mac OSX 10.8.2 w/Server) connected to my tv directly. I am using XBMC in conjunction with SickBeard and SABNZBD to automate my downloading process for all my weekly tv shows.

The problem is that when i go to XBMC-System-System-Input Devices-Allow Start of XBMC using remote, and select either the regular Apple Remote OR (Multi-remote Harmony) they only work Outside of XBMC. I can push the "menu" key on either of them from the Apple Desktop and XBMC opens up. However neither of the remotes work once inside of XBMC to control the menus.

I have tried the

sudo lsof -i -P | grep -i "listen"

....command to take a look at what services are using what ports but i dont know what port the "Remote Communication Server" is supposed to be using in the first place.

Here is the info i get back from terminal...

SABnzbd TCP localhost:9091 (LISTEN)
SABnzbd TCP localhost:9095 (LISTEN)
Python TCP *:8081 (LISTEN)
XBMCHelpe TCP *:1057 (LISTEN)
XBMCHelpe TCP *:8080 (LISTEN)
XBMCHelpe TCP localhost:9090 (LISTEN)
XBMC TCP *:8089 (LISTEN) (note:This one i manually changed to 8089 under the webserver option in xbmc)
XBMC TCP *:1913 (LISTEN)

Any help would be appreciated, I dont know all that much about port communication. Thanks
Reply
#10
(2012-06-05, 21:31)Korey Wrote: Paste this in terminal, it will show you what ports are in use.

sudo lsof -i -P | grep -i "listen"

it will ask you for your password.


As far as knowing that it is port 9090:

"third-party applications can access XBMC's JSON-RPC API by opening a TCP socket on port 9090 (this port can be configured in the advanced settings file) and sending raw JSON-RPC requests over that socket."

taken from this page: http://wiki.xbmc.org/index.php?title=JSON-RPC_API#TCP

Thank you, It was Mobile Mouse Server for me too

MacMini 2.3gHz i7, OS X 10.13.6
Running Kodi 18.9
Reply
#11
raising the dead with this post but I get the same error at startup. warnign disappears then all is good. can't seem to figure where the conflict for port is
jim@jim2 ~ $ sudo lsof -i -P | grep -i "listen"
[sudo] password for jim: 
dnsmasq    1005 nobody    5u  IPv4   19717      0t0  TCP jim-HP-Compaq-dc7900-Small-Form-Factor:53 (LISTEN)
smbd       1271   root   34u  IPv6   20881      0t0  TCP *:445 (LISTEN)
smbd       1271   root   35u  IPv6   20882      0t0  TCP *:139 (LISTEN)
smbd       1271   root   36u  IPv4   20883      0t0  TCP *:445 (LISTEN)
smbd       1271   root   37u  IPv4   20884      0t0  TCP *:139 (LISTEN)
dropbox    2225    jim   88u  IPv6   24817      0t0  TCP *:17500 (LISTEN)
dropbox    2225    jim   89u  IPv4   24818      0t0  TCP *:17500 (LISTEN)
dropbox    2225    jim  129u  IPv4   24810      0t0  TCP localhost:17600 (LISTEN)
dropbox    2225    jim  134u  IPv4   24813      0t0  TCP localhost:17603 (LISTEN)
kodi.bin   2447    jim   25u  IPv4   25063      0t0  TCP localhost:65007 (LISTEN)
kodi.bin   2447    jim   28u  IPv6   26341      0t0  TCP ip6-localhost:9090 (LISTEN)
kodi.bin   2447    jim   37u  IPv4   26382      0t0  TCP 127.1.2.3:45678 (LISTEN)
kodi.bin   2447    jim   39u  IPv4   25043      0t0  TCP *:1026 (LISTEN)
kodi.bin   2447    jim   54u  IPv4   25080      0t0  TCP localhost:8630 (LISTEN)
cupsd      6666   root   10u  IPv6 2854164      0t0  TCP ip6-localhost:631 (LISTEN)
cupsd      6666   root   11u  IPv4 2854165      0t0  TCP localhost:631 (LISTEN)
kodi.bin   7626    jim   38u  IPv4 2938861      0t0  TCP *:1582 (LISTEN)
kodi.bin  12378    jim   32u  IPv4  724572      0t0  TCP *:1914 (LISTEN)
kodi.bin  12378    jim   42u  IPv4  724580      0t0  TCP localhost:9090 (LISTEN)
kodi.bin  24502    jim   38u  IPv4 1677449      0t0  TCP *:1993 (LISTEN)
kodi.bin  25305    jim   38u  IPv4 1802586      0t0  TCP *:1410 (LISTEN)
kodi.bin  26962    jim   38u  IPv4 2007748      0t0  TCP *:1711 (LISTEN)
kodi.bin  31948    jim   40u  IPv4 4468516      0t0  TCP *:1096 (LISTEN)
kodi.bin  32360    jim   39u  IPv4 4546194      0t0  TCP *:1383 (LISTEN)
jim@jim2 ~
any eagle eye see a problem?

RESOLVED: Don't quite understand the competition but disabling dropbox at startup resolved the competition with KODI
Reply

Logout Mark Read Team Forum Stats Members Help
Remote Communication Server Failed to start0