similar to: Problem connecting to icecast2

Displaying 20 results from an estimated 2000 matches similar to: "Problem connecting to icecast2"

2004 Aug 06
0
Problem connecting to icecast2
I see that I don't understand why it is still using the xaudiocast protocol here is my config file located in this same directory. <?xml version="1.0"?> <ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices"> <ices:Playlist> <ices:File>test.txt</ices:File>
2004 Aug 06
0
Problem connecting to icecast2
In your Ices0. config file you need to change the protocol to work with Icecast 2 (at the moment you have it set up for Icecast 1.3 server). HTTP is the required protocol for connecting to Icecast 2. -------------------------------------- <Protocol>http</Protocol> -------------------------------------- <p>This should solve your immediate problem. <p>Joe.
2004 Aug 06
0
Problem connecting to icecast2
The mountpoint is created by the Icecast server after initiated by Ices and only exists while it's source does. <p>Check the error.log in the Icecast 2 directorys to see why the Ices is having trouble making a connection. <p>>From: "Kristoffer R. Munroe" <krism@ragemp3.com> >Reply-To: icecast@xiph.org >To: icecast@xiph.org >Subject: Re: [icecast]
2004 Aug 06
2
Problem connecting to icecast2
I am trying to connect to an icecast2 server that I have running on redhat 9. Via Ice0. Here are the errors that I am getting. Any help would be greatly appreciated. Kris. <p>[root@wyatt icecast]# ices -m mymp3stream -c ices.conf -P hackme Unknown Node: Server Unknown Execution keyword: Base_Directory Logfile opened DEBUG: Sending following information to libshout: DEBUG: Stream: 0
2004 Aug 06
0
Problem connecting to icecast2
I am using the http protocol now and I still get the same results. Does the mount point in ices need to be a directory that I am mounting to with read write permissions? Or is it a virtual mountpoint? <p>At 12:06 AM 4/15/2004, you wrote: >I am trying to connect to an icecast2 server that I have running on redhat 9. > >Via Ice0. Here are the errors that I am getting. >
2004 Aug 06
4
Problem connecting to icecast2
On Thursday, 15 April 2004 at 08:07, Kristoffer R. Munroe wrote: > I am using the http protocol now and I still get the same results. <snip> > >DEBUG: Sending following information to libshout: > >DEBUG: Stream: 0 > >DEBUG: Host: 127.0.0.1:8000 (protocol: xaudiocast) According to the log file you attached, you're still using xaudiocast. Double check your
2004 Aug 06
1
Problem connecting to icecast2
On Thu, 15 Apr 2004, Kristoffer R. Munroe wrote: > I see that I don't understand why it is still using the xaudiocast protocol <SNIP> > [root@wyatt icecast]# ices -m mymp3stream -c ices.conf > Unknown Node: Server > Unknown Execution keyword: Base_Directory hmmm. Just before we go any further, are you using Ices 0.3 with libshout 2.0? Older versions will not work with
2004 Aug 06
0
Multiple Stream? Request for Config
----- Original Message ----- From: "Ben Wilson" <ben@thelocust.org> To: <icecast@xiph.org> Sent: Friday, September 07, 2001 12:12 PM Subject: [icecast] Multiple Stream? Request for Config > I'm having some problems setting up multiple streams with iceS, for > example, a hi-bandwidth and lo-bandwidth stream of the same audio. Could > someone post a config that
2004 Aug 06
2
bitstream problem: resyncing...
This one really has me stumped. I'm running 866MHz, 256MB RAM, 80GB Disk (7200RPM) on Linux-mandrake 8.2 icecast 1.3.12 & ices 0.2.3 & lame 3.91 all mp3s encoded with lame 3.91 or higher and --r3mix (VBR) Sorry for the long email but I'm hoping to get someone out there that's seen this before and give me some advice... I'm continually getting errors like this when running
2004 Aug 06
0
ices configuration not working
You are trying to use ices 2 with an ices version 1 config file. On Friday, 13 June 2003 at 08:01, admin wrote: > OS: FreeBSD4.8 > > okay I installed ices from /usr/ports/audio/ices > > copied ices.conf.dist to config.xml > > can somebody explain to me why the configuration file is not getting loaded > > root@hurricane# ices
2004 Aug 06
2
Two Things: Python 2.1 & ices 0.2.2 / Multiple Streams
First off, I managed to build iceS 0.2.2 with Python 2.1, though I had to add -lutil to the $LIBS definition whilst ./configure'ing. Otherwise, configure won't find Py_Initialize Secondly - multiple streams I've added a second "stream" definition to my ices.conf, and both streams show up as sources for icecast, (http://blah.com:8000/list.cgi), though when i try to connect
2004 Aug 06
2
ices configuration not working
OS: FreeBSD4.8 okay I installed ices from /usr/ports/audio/ices copied ices.conf.dist to config.xml can somebody explain to me why the configuration file is not getting loaded root@hurricane# ices [/usr/local/etc/ices] IceS 2.0beta2 (c) Copyright 2001-2002 Michael Smith <msmith@icecast.org> Usage: "ices config.xml" root@hurricane# ices
2004 Aug 06
0
ices: PQueue module error
Hi All-- I'm trying to get icecast working with ices, but I'm having a problem with the PQueue module. I'm including my ices.connf file and verbose output when running in non-daemon mode below. I'm running on Fedora Core 1, and have all packages updated (via yum). I'd greatly appreciate any insights. Jim <p><?xml version="1.0"?>
2004 Aug 06
3
ices 0.2.2 does not reencode mp3s
Brendan Cully wrote: > > The format of ices.conf changed somewhat in 0.2, to support multiple streams > from the same playlist with different reencoding options. In short, these > settings have been moved into the Stream node. For more info have a look > at the sample ices.conf included with the distribution. I did modify my ices.conf when I made the upgrade. Here's my
2004 Aug 06
1
Ices 0.3 won't play mp3 file
OK...finally got Icecast 1.3/2 set up. Currently testing things with Icecast 2 and Ices 0.3 Icecast 2 runs fine and I can access the admin facility through the web...alls good there. <p>When I launch Ices (0.3) it loads up the song from the supplied playlist throws out this... Playing /usr/home/herbal/GanjaSmugglin.mp3 DEBUG: Updated metadata on /stream.mp3 to: Test Artist - Test
2004 Aug 06
0
ices2 not compiling on OpenBSD 3.3 -> ices 0.3 cofig problem?
> > Playlist streaming works well on OpenBSD, of course. The > first step to > > actually fix this would be improving the autodetection to > disable Sun > > audio on OpenBSD automatically - next would be to write im_bsd.c. ;P > > Hmm, I would need that for live streaming. How about ices 0.3? Ices 0.3 compiles OK, but I have troubles to make a config file. Here is
2004 Aug 06
1
Problems with ices
Hi, I compiled the latest version of ices from cvs, but I have some problems with it. When I start it up, I only get the error "Failed to read config file "/usr/local/icecast/etc/ices.conf"" My /usr/local/icecast/etc/ices.conf looks like this: <?xml version="1.0"?> <ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices">
2004 Dec 05
0
permissions, permissions
Hello, Clueless newbie using ices 0.4 and icecast 2. Situation: a small closed network, no worries about security. Error I am bumping into: [devprog1@localhost ices-0.4]$ ices Logfile opened Playing /home/devprog1/mp3/01.mp3 Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Login failed Following are my two config files, could anyone help me out? TIA, Bert <icecast>
2004 Aug 06
7
cannot get icecast and ices to talk...authentication failed
I have a weird one... I installed icecast 2 and ices .23 on Mandake, and am not having any luck I compiled and installed the nightly icecast just today. It seems to work fine, however when I telnet to it (10.0.0.3, port 8000), I am unable to login unless the first line contains ONLY the password. I used ethereal to see that iceS is trying to send to authenticate, and it is sending (as the first
2004 Aug 06
2
Ices -> Icecast Authentication Failure
Hello, list -- Sorry for the dumb post about confirmation -- I've always wanted to run majordomo so I could see how this stuff works. Whoops! I guess replying to the email really isn't the thing to do -- even though it explicitly states it as an option... My problem, outside of list etiquette, is this: having compiled all the latest, installed, etc., ... having read all I can find