Fletch;396767 Wrote: > Hmm, the "failed" messages probably just indicate that it's trying to > stop a process that isn't running. I'm not sure why. What happens if > you run (as root) "/sbin/service squeezecenter start"? After running > that command, what's the output of "ps -eF | grep squeeze"? Also, take > a look in /var/log/squeezecenter/server.log for any errors.
I think youre right that squeezecenter was/is not actually running. (See below). "/sbin/service squeezecenter start results in message SELinux setting prevent squeezecenter from starting, See [Squeezecenter wiki] Nothing is in /var/log/squeezecenter/server.log However, I did not check that until just after my last reboot. (See below). Does this file get renewed every restart? gharris999;396775 Wrote: > The firewall and/or SELinux could be what are impeding you. I'd try > disabling SELinux and then check the firewall. I'm not sure if the SC > rpm opens the appropriate firewall ports for you or not. Fletch: what > does the rpm do in terms of SELinux and firewall prep? > > Anyway, I always manually open the appropriate ports when I setup a > Fedora box for SqueezeCenter. I don't usually use the GUI, so this is > the non-gui approach: > > Open a terminal window and enter the following commands at the prompt: > > su (you'll be prompted for root's password) > cd /etc/sysconfig > cp iptables iptables.bak > gedit iptables > > now, if you don't already seem them, paste these lines somewhere into > the middle of the iptables file: > > > Code: -------------------- > > > -A INPUT -m state --state NEW -m tcp -p tcp --dport 3483 -j ACCEPT > -A INPUT -m state --state NEW -m udp -p udp --dport 3483 -j ACCEPT > -A INPUT -m state --state NEW -m tcp -p tcp --dport 9000 -j ACCEPT > -A INPUT -m state --state NEW -m tcp -p tcp --dport 9090 -j ACCEPT > -------------------- > > > > Save the file, exit gedit and restart the firewall from the terminal > prompt: > > service iptables restart > > Now, check to see that SqueezeCenter is actually running: > > /sbin/service squeezecenter status > > If it is, see if your browser can now connect to squeezecenter at > http://127.0.0.1:9000/ I did all of this, except I neglected to try to disable SELinux first. (None of lines you suggest for iptables were there already, although there was one such line with a different port number, and I left it in.) /sbin/service squeezecenter status revealed that squeezecenter was/is not running. I then tried /sbin/service squeezecenter start and got the same result I did before SELinux setting prevent squeezecenter from starting, See [Squeezecenter wiki] Then I noticed your suggestion to disable SELinux. I was unable to. I went to the menu System>Adminisration>Services and SELinux is not listed as a service. How do I disable SELinux? (You still think that a good idea?) Other suggestions? Thanks, Randy -- rmariger ------------------------------------------------------------------------ rmariger's Profile: http://forums.slimdevices.com/member.php?userid=1160 View this thread: http://forums.slimdevices.com/showthread.php?t=60137
_______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
