SageTV, SqueezeBox Server and WHS

[rlvogel322]

I use SqueezeBox Server and SageTV on my WHS system. When I installed the beta SageTV version 7.0.9 everything was working fine including SqueezBox Server since it was already installed as an add-in before SageTV. I tried to install the latest SqueezeBox Server by removing the current add-in and installing the new one with SageTV installed and running. I also tried the normal RDP install but it would always fail to start the squeezesvr service. What I discovered in the MySql error logs was that SqueezeBox Server was attempting to start mysqld on port 9092. I ran fport and discovered an instance of SageTVService on port 9092. I stopped the SageTV service and was able to complete the install of SqueezeBox Server.

I am not sure if this is a SageTV or SqueezeBox Server issue. I have submitted a bug report to SageTV making them aware of what was found. SqueezeBox and SageTV seem to run OK when both are using the same port but to me that seems like a bad idea.

I am not sure of the feasability, but it would make sense for the installs to check for port availability prior to installing the service on a used port. Anyone else see anything like this?

[briands]

Hmmm... I did notice a similar problem. I managed to get SqueezeBox Server to run by doing a manual install of the latest version 7.5.1 (non WHS version) in an RDP session. Both seem to be working OK now... wonder what will happen when I update to the latest Sage beta.

[rlvogel322]

I tried the manual install with a RDP session and even though the install finishes the service would never start. It would hang on starting after the install.

I had to stop the SageTV Service before it would work.

Sage mentioned they do not start any service on that port and it is possible a plugin is using it. I have not had time to diagnose further to narrow it down to which plugin it may be.

[jm9843]

I had the exact same problem. And Sage had the exact same response to my bug report: that a plugin must be the culprit...

[rlvogel322]

Originally Posted by jm9843

I had the exact same problem. And Sage had the exact same response to my bug report: that a plugin must be the culprit...

I am planning on working on this tonight. Hopefully I'll be able to determine if it is a plugin and which one it might be. What plugins do you have installed?

[robogeek]

I found the culprit. It's the SageTV H2 Database plugin, which is a dependency of the Phoenix API plugin, which is a dependency of the Metadata Tools for SageTV plugin. You can go to Setup->SageTV Plugins->Installed Plugins, scroll down and select the SageTV H2 Database plugin, select Configure Plugin from the options popup, and then you can change the TCP port it uses from 9092 to something else.

[Peter_h]

Might want to alert the plugin author of the conflict.

[rlvogel322]

Originally Posted by robogeek

I found the culprit. It's the SageTV H2 Database plugin, which is a dependency of the Phoenix API plugin, which is a dependency of the Metadata Tools for SageTV plugin. You can go to Setup->SageTV Plugins->Installed Plugins, scroll down and select the SageTV H2 Database plugin, select Configure Plugin from the options popup, and then you can change the TCP port it uses from 9092 to something else.

Thanks for the heads up! I just got a chance to sit down and start looking at this.

[heatvent]

Originally Posted by robogeek

I found the culprit. It's the SageTV H2 Database plugin, which is a dependency of the Phoenix API plugin, which is a dependency of the Metadata Tools for SageTV plugin. You can go to Setup->SageTV Plugins->Installed Plugins, scroll down and select the SageTV H2 Database plugin, select Configure Plugin from the options popup, and then you can change the TCP port it uses from 9092 to something else.

Sorry for being naive but does SB Server use port 9092?

[robogeek]

Originally Posted by heatvent

Sorry for being naive but does SB Server use port 9092?

Yes, it uses port 9092.

[jarredduq]

Originally Posted by robogeek

I found the culprit. It's the SageTV H2 Database plugin, which is a dependency of the Phoenix API plugin, which is a dependency of the Metadata Tools for SageTV plugin. You can go to Setup->SageTV Plugins->Installed Plugins, scroll down and select the SageTV H2 Database plugin, select Configure Plugin from the options popup, and then you can change the TCP port it uses from 9092 to something else.

Is there anything else that needs to be done other than changing the port? I changed mine to 9093. Squeezebox server now runs okay. I just want to make sure I'm not breaking anything else.

[gplasky]

That's usually all you need to do. And it is working for you.

Gerry