Bug 12163 – Unable to communicate with player (unknown error)

Bug 12163 - Unable to communicate with player (unknown error)

Summary:

Unable to communicate with player (unknown error)

Status:	RESOLVED DUPLICATE of bug 11984

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Commercial
Version:	Prod
Platform:	Macintosh MacOS X 10.5

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:	http://commercial.squeezenetwork.com/...
Keywords:	Support-Important

Depends on:	11984
Blocks:
	Show dependency tree / graph

Reported:	2009-05-26 05:05 UTC by Pete Simons
Modified:	2009-06-11 13:25 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Pete Simons 2009-05-26 05:05:27 UTC

Hey Guys,

I have found that lately I am getting the subjected error withing the player "Status" field in the commercial portal. This has usually happened with an account in the field, but this weekend I noticed the error on my personal player at home. When the "Unable to communicate with player (unknown error)" comes up I am unable to change streams. This error also makes it impossible to view the buffer and "now playing". If I make a change to the stream the action shows up in the "Stream Events" but does not actually engage the player to the specified change.

The player is STILL playing when this error comes up and channels can be changed manually with the remote, which is a GOOD thing.

The only action I have taken to try and remedy the problem is to reboot the player, which does not correct the error.

Pete Simons
io4business.com

Comment 1 Andy Grundman 2009-05-26 06:05:48 UTC

This isn't really a bug, the message means the player is on a different datacenter from the one your browser is connected to, and there is a bit of database replication lag between those 2 datacenters.

Comment 2 Pete Simons 2009-05-26 06:11:36 UTC

Ok Andy. The database lag must be a very long one as the portal has shown the unable to connect to player for 3 days now....

Comment 3 James Richardson 2009-06-11 13:25:12 UTC

This is a Symptom of bug 11984, OPEN DNS removal and DB optimizations may solve this issue.  Marking as a duplicate for now, if you feel it's not, or you still experience this issue after 11984 if is fixed, please reopen this bug.

*** This bug has been marked as a duplicate of bug 11984 ***