| View previous topic :: View next topic |
| Author |
Message |
adabisnis
Joined: 31 Jul 2012
Posts: 14
Location: Indonesia
|
 Posted: Wed Sep 05, 2012 10:09 am Post subject: EROR connection/connection_setup_sockets |
 |
|
I run icecast :
| Quote: |
icecast -c /usr/local/etc/icecast.xml -b
Starting icecast2
Detaching from the console
[2012-09-05 10:07:41] EROR connection/connection_setup_sockets Could not create listener socket on port 8000
[2012-09-05 10:07:41] EROR connection/connection_setup_sockets No listening sockets established
[2012-09-05 10:07:41] EROR main/fatal_error Server startup failed. Exiting |
i have off iptable, but still find this problem
_________________
Klikhost.com |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Sep 05, 2012 10:23 am Post subject: |
|
|
that is probably not a firewall issue, it's typically because something is already listening on the port (and optionally bind) combination. Look at netstat -tnlp | grep 8000, that should show the pid and process name listening on the port, typically an icecast already running.
karl.
Last edited by karlH on Wed Sep 05, 2012 2:22 pm; edited 1 time in total |
|
| Back to top |
|
|
adabisnis
Joined: 31 Jul 2012
Posts: 14
Location: Indonesia
|
| Posted: Wed Sep 05, 2012 10:51 am Post subject: |
|
|
Thank you KarlH
_________________
Klikhost.com |
|
| Back to top |
|
|
pph
Joined: 17 May 2014
Posts: 3
|
| Posted: Sat Aug 12, 2017 2:26 pm Post subject: |
|
|
Hi everyone,
While what KarlH said is true in most of the cases, mine was different. I was trying to start icecast2 on an AWS EC2 instance, and it turns out it cannot bind on a public IP address. Instead, I had to use a private IP – one can get it from the instance description in AWS console, or by running the ifconfig command. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
