I'm running the Windows EXE, Oddsock's compiled version of July 13, 2005. I have 1 server running Icecast that generates the streams, and 3 servers that pickup these streams via relay and distribute the streams to our listeners. In other words, I have 3 servers in a cluster that the clients connect to. All three of the cluster servers use the exact same icecast.xml file. The three servers are identical. On one of the 3 servers, Icecast will just go away, no error message, no message, nothing in the logs, etc. I made a little watchdog app to check every few seconds if it was running and if not start Icecast.exe again, if it restarts Icecast, it makes an entry in a log file. I set the logging level in Icecast on this server to 4. This morning, I checked the log for the watchdog app and it had restarted Icecast 6 times overnight. I noted the times and look in Icecast's logs and I don't see anything that indicates a problem. The last restart was at 7/26/2005 11:16:56 PM. The other 2 servers in the cluster do not have this problem - Icecast keeps running as it should. I've attached some snippets from the log files from the server with the problem, as well as the Icecast.xml file (with the passwords removed). Any ideas why this is happening???? thanks, Fred Fred -------------- next part -------------- A non-text attachment was scrubbed... Name: icecast-no-passwords.ZIP Type: application/octet-stream Size: 3024 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast/attachments/20050727/faf60ac7/icecast-no-passwords.obj
More info from the event log: Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 7/26/2005 Time: 11:16:55 PM User: N/A Computer: MP3-002 Description: Faulting application Icecast2.exe, version 1.0.0.1, faulting module Icecast2.exe, version 1.0.0.1, fault address 0x000199f4. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 49 63 65 ure Ice 0018: 63 61 73 74 32 2e 65 78 cast2.ex 0020: 65 20 31 2e 30 2e 30 2e e 1.0.0. 0028: 31 20 69 6e 20 49 63 65 1 in Ice 0030: 63 61 73 74 32 2e 65 78 cast2.ex 0038: 65 20 31 2e 30 2e 30 2e e 1.0.0. 0040: 31 20 61 74 20 6f 66 66 1 at off 0048: 73 65 74 20 30 30 30 31 set 0001 0050: 39 39 66 34 99f4 Fred -----Original Message----- From: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org] On Behalf Of Fred Black Sent: Wednesday, July 27, 2005 8:51 AM To: 'icecast' Subject: [Icecast] Icecast dies I'm running the Windows EXE, Oddsock's compiled version of July 13, 2005. I have 1 server running Icecast that generates the streams, and 3 servers that pickup these streams via relay and distribute the streams to our listeners. In other words, I have 3 servers in a cluster that the clients connect to. All three of the cluster servers use the exact same icecast.xml file. The three servers are identical. On one of the 3 servers, Icecast will just go away, no error message, no message, nothing in the logs, etc. I made a little watchdog app to check every few seconds if it was running and if not start Icecast.exe again, if it restarts Icecast, it makes an entry in a log file. I set the logging level in Icecast on this server to 4. This morning, I checked the log for the watchdog app and it had restarted Icecast 6 times overnight. I noted the times and look in Icecast's logs and I don't see anything that indicates a problem. The last restart was at 7/26/2005 11:16:56 PM. The other 2 servers in the cluster do not have this problem - Icecast keeps running as it should. I've attached some snippets from the log files from the server with the problem, as well as the Icecast.xml file (with the passwords removed). Any ideas why this is happening???? thanks, Fred Fred
On Wed, 2005-07-27 at 13:51, Fred Black wrote:> The other 2 servers in the cluster do not have this problem - Icecast keeps > running as it should.That makes me suspicious to start with, the same app with the same config and the same server keeps failing. Obviously there are other factors that can get involved like the directory server and of course listeners but make sure there is nothing weird hardware-wise, eg run a hard memory test.> Any ideas why this is happening????the generated fault report is about as clear as mud so it needs more investigation, whether the fault address will indicate the real fault is to be checked. karl.
hi, I'm running an live 128kbit mp3-upstream (icecast v 2.2.0 on freebsd) from a site where the internet-connection is rather bad and drops every ~20min for few seconds (I'm using streamtranscoder by the way). my question is if there's any parameter to increase the buffer of the upstreaming-source. the config-file of icecast offers <queue-size>, but this seems to affect only the listeners, not the sources, right? thx for any help, mike