similar to: Icecast not working (error log provided)

Displaying 20 results from an estimated 800 matches similar to: "Icecast not working (error log provided)"

2008 Jul 03
3
Icecast Fedora9 migration problems
Karl Heyes wrote: > Seann Clark wrote: > >> The biggest being is that the server binds to whatever port it feels >> like instead of the bind port specified. The rest of the issues I have > > a random port bind is a new issue. Can you show us the > netstat -tnlp | grep icecast > for the xml provided? Thu Jul 03-13:54:17-root at haruhi-new:~> netstat -tnlp | grep
2016 Oct 09
1
SSL.
Hello, I’m new to icecast and I’m trying to setup icecast on Debian 8, with the 2.4.3 version, compiled manually. The thing is I can’t make the ssl part work. I have a listen directive like this : <listen-socket> <port>8483</port> <ssl>1</ssl> </listen-socket> and ssl-certificate :
2019 Jul 23
0
Files not populated in var/www
error.log [2019-07-22 13:25:18] INFO main/main Icecast 2.4.4 server started [2019-07-22 13:25:18] INFO connection/get_ssl_certificate No SSL capability on any configured ports [2019-07-22 13:25:18] INFO stats/_stats_thread stats thread started [2019-07-22 13:25:18] INFO yp/yp_update_thread YP update thread started [2019-07-22 13:26:23] INFO main/_server_proc Caught halt
2014 Jun 22
0
second life listener connects but does not get stream
Linux blort.psg.com 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:02:19 UTC 2014 i686 i686 i686 GNU/Linux # icecast2 --version Icecast 2.3.3 <listen-socket> <port>43000</port> </listen-socket> <listen-socket> <port>43001</port> <shoutcast-compat>1</shoutcast-compat> </listen-socket> source is
2010 Apr 27
4
Icecast Server doesnt work.
I am very new on this list, so that I will first say hello to everybody. I been this morning on the IRC and some guy there explained me that if I want real help I must pay him 60 euros pe hour. I hope you dont charge me 60 euros for readiung this email and giving a hint. I have tryed to install icecast2 and ices2 on my dedicated server and followed allthe steps described on your site. in the end
2005 Mar 27
1
Beginner needs help.............
This is what I get in the icecast logfile. [2005-03-27 15:35:13] INFO main/main Icecast 2.2.0 server started [2005-03-27 15:35:13] WARN main/main YP server handling has been disabled [2005-03-27 15:35:13] INFO stats/_stats_thread stats thread started [2005-03-27 15:35:13] INFO fserve/fserv_thread_function file serving thread started [2005-03-27 15:36:38] INFO admin/admin_handle_request Bad
2006 Feb 15
1
Setup problems please assist
This is my first time setting this up and having a problem. I don't know where the problem lies. Do the files need a special permissions? What is wrong with my setup? $cat icecast.xml <icecast> <limits> <clients>2</clients> <sources>2</sources> <threadpool>5</threadpool>
2008 Jul 03
2
Icecast Fedora9 migration problems
Ok, First I want to start off with this isn't the first icecast I have cloned, but it is the first where I have not only jumped Fedora release versions, but arch types as well (i386 - x86_64) and I am having strange problems. The Icecast versions are the same between the old and new servers. The biggest being is that the server binds to whatever port it feels like instead of the bind port
2020 May 26
1
problem creating a systemd service
Hello! Icecast behaves oddly for me in debian testing, somehow the permissions on my log file directory was set to root:adm if I remember things right. Also there was no systemd service starting when I tried to start from /etc/init.d, somehow init services refer to systemd services nowadays whether they exist or not. I tried to create a systemd service looking like this: [Unit]
2005 Jul 28
2
understanding error.log
Hello. A couple questions. When I execute curl http://myserver.xxx.xxx:8000/test.mp3 , I get "<b>The source you requested could not be found.</b>" I've placed my error.log and icecast.xml files below. Could someone help me understand my error.log a little better - to maybe see why I'm not getting a stream when I make the above curl call. Also, you'll see in
2020 Oct 14
0
meaning of global connections and global client_connections in error log
hallo firstly sorry for posting to wrong thread i want to ask if somebody could explain meaning of log records below DBUG stats/modify_node_event update global connections (686) DBUG stats/modify_node_event update global client_connections (685) number in parentheeses is increasing in every log line what is menaing of this number? because this number goes over 59669 and it seems that after
2019 Jul 23
4
Files not populated in var/www
Greetings, I would love any advice configuring icecast on a virtual redhat server hosted by our university. I am currently trying to configure Icecast and cannot get the icecast server to start. The config file looks correct. I checked the /var/www/icecast/web and /var/www/icecast/admin folders and they were both empty, leading me to believe that this is why the server will not start. Since I was
2015 Apr 29
0
Segmentation fault issue with new install
On 04/28/2015 02:27 PM, Jan-Pieter wrote: > Hi all, > see my reply inline. > Cheers, Jan-Pieter > > > 2015-04-26 7:23 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi > <mailto:thomas at ruecker.fi>>: > > On 04/25/2015 07:32 PM, Jan-Pieter wrote: > > Hi all, > > > > I am a long-time user of Icecast, always without
2015 May 03
0
Icecast-dev Digest, Vol 115, Issue 2
sorry can u make some simplesty in your mail date and mail and why all that you can divided all make link for each part like link has message link has "> > bad start (segfault): > > [2015-04-28 15:56:53] INFO main/main Icecast 2.4.1 server started > > [2015-04-28 15:56:53] DBUG yp/yp_recheck_config Updating YP > configuration > > [2015-04-28 15:56:53] INFO
2025 Jan 02
2
Not getting listed on the YP Directory
I think I have everything set correctly, but still not getting there. Requested data: <hostname>stream.wortfm.org</hostname> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> <listen-socket> <port>8000</port> <!-- <bind-address>127.0.0.1</bind-address> -->
2015 Apr 28
2
Segmentation fault issue with new install
Hi all, see my reply inline. Cheers, Jan-Pieter 2015-04-26 7:23 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi>: > On 04/25/2015 07:32 PM, Jan-Pieter wrote: > > Hi all, > > > > I am a long-time user of Icecast, always without problems. However i > > made a new setup using icecast 2.4.1 on a fresh and quick CentOS VPS. > > EPEL package or from
2015 Apr 30
1
Segmentation fault issue with new install
2015-04-29 8:57 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi>: > On 04/28/2015 02:27 PM, Jan-Pieter wrote: > > Hi all, > > see my reply inline. > > Cheers, Jan-Pieter > > > > > > 2015-04-26 7:23 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi > > <mailto:thomas at ruecker.fi>>: > > > > On
2015 Apr 30
0
Fwd: Segmentation fault issue with new install
Now with attachment ;-) 2015-04-29 8:57 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi>: > On 04/28/2015 02:27 PM, Jan-Pieter wrote: > > Hi all, > > see my reply inline. > > Cheers, Jan-Pieter > > > > > > 2015-04-26 7:23 GMT+02:00 "Thomas B. R?cker" <thomas at ruecker.fi > > <mailto:thomas at ruecker.fi>>:
2005 Jun 01
3
Icecast locks with WARN connection/_accept_connection accept() failed with error 24: Too many open files
My icecast server has been running happily for months now, but just yesterday it locked up, chewing up all the cpu time it could find, and not allowing connections. The last snippet of the error log shows this: [2005-06-01 09:36:13] WARN connection/_accept_connection accept() failed with error 24: Too many open files [2005-06-01 09:36:15] WARN connection/_accept_connection accept() failed
2015 Apr 25
3
Segmentation fault issue with new install
Hi all, I am a long-time user of Icecast, always without problems. However i made a new setup using icecast 2.4.1 on a fresh and quick CentOS VPS. The issue is that starting icecast gives a segmentation fault at around 80% of all starts. No core file nor a entry in error.log is posted. In the remaining 20% of the starts icecast start with no problem. Contents of the error.log with a succesfull