SqueezeCenter doesn't work??

[echols]

Hi, I need help figuring out what has happened. I can't access any radio stations with Squeezecenter on the vortexbox. I can listen to cds ripped on the box, but when I try slacker or paradise radio, nothing happens. It acts like it is going to play, the timer starts and then the timer resets to zero and nothing happens. Same with local radio stations, so it must be the SqueezeCenter. I don't understand how the vb talks to SC and SC to the vb. Or is this something to do with Logitech? When I access SC on my laptop with the vb as the player, who all is involved?


thanks


Steve

[echols]

Thinking some more.. Am I trying to use the vb for the wrong purpose? I like listening to internet radio thru it because I can access it wirelessly with my laptop. I don't have to plug the laptop into the stereo. But now I am having problems with squeezecenter. Would it be better to just have the vb as a windows computer and access it remotely? Can I do that with a macbook?


thanks again for the education.




Steve

[echols]

I'm having a conversation with myself.


When I try to access Slacker thru squeezecenter I get


"There was an error loading the remote feed for Slacker: (Couldn't resolve IP address for: http://www.squeezenetwork.com)"




Steve

[SubFuze]

I'm having the same issue with:


VortexBox Version 0.7


SqueezeCenter Version 7.3.3




I have no connectivity from SqueezeCenter. Can't access anything that hits the net, but local files play just fine. I've verified that the box itsef has connectivity (ssh'ed in and pinged some addresses and got responses). I even verified that the addresses that SqueezeCenter was trying to hit were reachable from from the box.




Any ideas? Things to try? I did see some stuff on the SqueezeCenter forums that seemed somewhat related where people were able to get connectivity by upgrading to the current 7.4 beta... What would be the best way to try 7.4 on VortexBox?

[andrew]

Thatis is very strange 1000s of people have VortexBox 0.7 working with SC 7.3.3 Seem like a networking problem of some kind. Have you read our documantation section yet? There are docs on subjects includign upgrading to BETA versions of SC




http://vortexbox.org/documenta.....ezecenter/ (http://vortexbox.org/documentation/installing-beta-version-of-squeezecenter/)

[SubFuze]

Thanks- got it working with the testing version (7.3.4 – 27488), however the instructions in your documentation failed for me with the error:


Public key for squeezecenter-7.3.4-0.1.27488.noarch.rpm is not installed




I was able to do the update with the instructions on the SqueezeCenter Wiki:


http://wiki.slimdevices.com/in.....Center_RPM (http://wiki.slimdevices.com/index.php/SqueezeCenter_RPM)


Ran:

rpm -Uvh http://repos.slimdevices.com/y.....noarch.rpm (http://repos.slimdevices.com/yum/squeezecenter/squeezecenter-repo-1-6.noarch.rpm)

Edited:
/etc/yum.repos.d/squeezecenter.repo

so that the proper release had enabled=1

Ran:
yum update squeezecenter


I'm really enjoying VortexBox so far- I just installed it today for the first time.
I haven't even tried the automatic CD ripping, but so far it's turning out to be
a way better fit than the last server I was using (Openfiler).

[echols]

I followed Andrew's directions but it only goes to 7.3.3 (27044) and no change to the error message, unable to resolve the ip address.


Steve

[echols]

I followed Andrew's directions but it only goes to 7.3.3 (27044) and no change to the error message, unable to resolve the ip address.


Steve

[SubFuze]

echols: did you try the instructions I provided?


sorry about the formatting, looks like I inadvertantly introduced a pre tag


and this board doesn't display them properly




Andrew:


You can fix the formatting by adding this rule to your css:


pre {

width: 500px;
overflow: auto;

}

[echols]

No,


I don't know how to edit stuff. If its type in the command, I'm ok, but I haven't learned how to edit. I haven't been able to listen to any internet radio for about a week. Unless I just plug the laptop into the stereo. Frustrating, and there are 10 other things I should be spending my time on instead of vb. On the vb screen it says to access use 192.168.2.7, but when I run ifconfig it says its 192.168.2.5 if I am reading it correctly. Don't know if that is a clue to the problem.


thanks for your help


steve echols

[SubFuze]

The easiest way would be to navigate to the directory, in this case:


cd /etc/yum.repos.d




Then edit the file with nano:


nano squeezecenter.repo




It's a pretty straightforward editor, make your changes then hit:


ctrl-x




They hit Y to save.

[echols]

How do I know if I have 7.4 available?

[SubFuze]

You can find the version number in settings -> information (I believe, I'm not at my computer atm)


also, if my experience holds true, you only need to go to the current testing version 7.3.4, not to the unstable nightly (7.4)

[echols]

Is the right side of all the messages cut off on your browser for these messages?

[SubFuze]

Yeah, it is... A pre tag found its way into one of my posts


and screwed up the layout




I provided a fix in one of my prior posts...

[echols]

You can't update my system remotely can you??




mac os

[SubFuze]

Looks like I spoke too soon- the fix didn't survive a reboot.


However, stopping then restarting squeezecenter fixed it.


Maybe it's being brought up too early and not seeing the connection?

[andrew]

It's possible that it is taking a very long time for your network connection to come up. But SqueezeCenter should be able to handle this.

[pfd]

It look like this is a bug in some linux builds. See


http://forums.slimdevices.com/.....hp?t=64400 (http://forums.slimdevices.com/showthread.php?t=64400)

[pfd]

There is a fix towards the end of that trail which changes the order that squeezecenter starts relative to the newwork connection but i don't know how to apply it via the fedore command line. Can anyone help with that?

[andrew]

pfd said:


There is a fix towards the end of that trail which changes the order that squeezecenter starts relative to the newwork connection but i don't know how to apply it via the fedore command line. Can anyone help with that?




try this



chkconfig –-del squeezecenter


nano /etc/init.d/squeezecenter



replace the 80 on line 5 with a 99



chkconfig –-add squeezecenter


reboot





please post with the results. This problem doesn't happen for me so I am relying on you to test this.

[echols]

-del command not found


pico command not found




This is getting to be like work..

[pfd]

ok tried that. needs two minus signs before the del and before the add. pico isnt installed but edited the file via winscp.


no luck i'm afraid. still no radio on first bootup but running "service squeezecenter restart" solves things until the next reboot.

[pfd]

this may be a daft idea, but can we automatically run a batch file to restart squeezecenter as the last thing that happens before you get the command prompt on startup? it seems that is what you have to do manually to make the thing work so why not just automate it? (or is that what we were trying to do above?)

[andrew]

OK, I think I may have out done myself this time :) forget all that other stuff.

yum -y update

is all you need. In the latest venison I have a script that pings google.com. If it can't get there is waits and tries again. Once it can connect it restarts SqueezeCenter. That should solve the problem no matter how long it takes the network to come up.

[wizardofoz]

After the yum update do we need to restart anything or reboot?




Does this also mean we are no longer having to deal with reinstalling the whole system for updates like it was from 6-7 for the first round?

[andrew]

yes you should reboot. That's should be all you need to do.

[echols]

I did a clean install of .8 and I now have the radio back Yeah!!


Thanks Andrew.




echols

[pfd]

update installed sucessfully and AlienBBC is back up and running again. http://vortexbox.org/wp-content/forum-smileys/sf-laugh.gif

[andrew]

pfd said:


this may be a daft idea, but can we automatically run a batch file to restart squeezecenter as the last thing that happens before you get the command prompt on startup? it seems that is what you have to do manually to make the thing work so why not just automate it? (or is that what we were trying to do above?)




That's what the commands in my previous post do. 99 is the highest start priority. SqueezeCenter will get started last. I updated my post to make it easier to read. try it again.

[dramen1]

Ok also did a clean install of 0.8 and it worked for the rest of the day. Booted up the server this morning and its back to how it was before. i have to restart squeezecenter or go back to 7.3.2.http://vortexbox.org/wp-content/forum-smileys/sf-frown.gif