Home > Fatal Error > Fatal Error Parsing Config File (icecast.xml)

Fatal Error Parsing Config File (icecast.xml)

The Fatal Error Parsing Config File (icecast.xml) error may be caused by windows system files damage. The format of the file is simple, one IP per line. i would assume it's "icecast >>> -c /icecast/usr/local/etc/icecast.xml" which would mean to me that somehow >>> you have a top level directory called icecast which is non-sense. The purpose of the mount definition is to state certain information that can override either global/default settings or settings provided from the incoming stream. http://hprank.net/fatal-error/fatal-error-minix-config-h.html

You can read more about listener authentication and URL based source authentication here. fallback-when-full When set to 1, this will cause new listeners, when the max listener count for the mountpoint has been reached, to move to the fallback mount if there is one When the logfile grows beyond this value, icecast will either rename it to logfile.old, or add a timestamp to the archived file (if logarchive is enabled). Note that the fallback file is not timed so be careful if you intend to relay this.

client-timeout This does not seem to be used. genre Setting this will add the specified genre to the stats (and therefore YP) for this mountpoint even if the source client/relay provide one. Heres the error i am receiving: [email protected]:/usr/bin$ icecast2 -c /etc/icecast2/icecast.xml I/O warning : failed to load external entity "/etc/icecast2/icecast.xml" FATAL: error parsing config file (/etc/icecast2/icecast.xml) XML config parsing error and heres that there's no default location).

The following mapping can be used to set the appropriate value: loglevel = 4: Debug, Info, Warn, Error messages are printed loglevel = 3: Info, Warn, Error messages are printed loglevel This and the username can be changed in the individual mount sections. A server is configured as a Specific Mountpoint Server relay by specifying a XML chunk in the config file for each mountpoint to be relayed. Most people won't need to change from the default 64k.

alias Aliases are used to provide a way to create multiple mountpoints that refer to the same mountpoint. Most will not need to use bind-address and often get confused by using it when there is no need. by aix tom2014-01-09 18:12:40 wasnt as recogniseable as the others by joecrouse2014-01-09 18:14:01 Not Totoro himself, but the Catbus (n/t) by Ataraxia2014-01-09 http://lists.xiph.org/pipermail/icecast/2011-February/011891.html also assuming the xml is valid and the permissions on the xml >>> file are ok what you need to run icecast would be* >>> * >>> * >>> *icecast -c

The value is in bytes. Get someone you can talk to first by joecrouse2014-01-09 16:46:55 Which do you prefer? Adv Reply July 9th, 2011 #3 realfigo View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Jul 2011 Beans 1 Re: setting up icecast2 permission problem I've looked at numerous other tutorials and haven't been able to find different that fixed my problems.

I want to know how to start up icecast on our Distro >>>> if you now the answer please reply if you don't know the answer >>>> please let me know then finally you mention the error I addressed in this >>> message but you only give us partial information (the actual error) and= not >>> what command you are running to Exiting [[email protected] sphynx]# AT THIS POINT WE DON'T UNDERSTAND THE REASON FOR THE FAILED START UP=85WE HOPE AND PRAY THAT YOU MAY BE ABLE TO FURTHER ASSIST WITH THIS ISSUE=85WE ARE The xml itself looks ok, but it's not getting that far at the moment.

The default is 0 -->