| View previous topic :: View next topic |
| Author |
Message |
MrOnline
Guest
|
 Posted: Fri Apr 14, 2006 11:03 pm Post subject: Segmentation fault |
 |
|
hi, i got a problem using Icecast 2.3-kh4, on the Icecast 2.2-kh6 i run it works perfect...
This is it, i've manged to narov it down to a ;... i use relay and mount, and on the
<server>xxx.yyy.zzz.vvv</server>
<port>####</port>
<mount>/;stream.nsv</mount>
<local-mount>/stream01.nsv</local-mount>
This works perfect on the 2.2-kh6 version, but not on 2.3-kh4 version... it wont start and gives me Segmantation Fault, if i remove the ; in <mount>/;stream.nsv</mount> and just have <mount>/stream.nsv</mount> it works and server starts, but then my shoutcast dont reconize the "request".... 
Anybody got any idea ?? |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sun Apr 16, 2006 12:54 am Post subject: |
|
|
try using a mount of / instead of the /;stream.nsv
obviously the segv error is something to track down. Can you email me the connection details so I can look into it.
karl. |
|
| Back to top |
|
|
MrOnline
Guest
|
| Posted: Sun Apr 16, 2006 7:30 pm Post subject: Email ? |
|
|
do i send it to "icecast@xiph.org" or is there somewhere else i can find your email adr ??
Well thing is that if i use
<mount>/stream.nsv</mount> it works, but shoutcast doesnt recognize it
or do you want me to try just <mount>/</mount> ??
i'll be happy to send u the whole "script" if thats needed
Atm this is only on a box home here with me... but would love to have it fixed so i can upgrade our servers with some "newer" versions... |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sun Apr 16, 2006 8:34 pm Post subject: |
|
|
The latter reference, I think the ; acts as a seperator/comment. Send details to my email address (along with the xml so I know what setting you are using), as I'll be the one fixing it. Email addr is indicated on my posts in this forum.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Mon Apr 17, 2006 4:56 pm Post subject: Had a chance to have a look yet ?? |
|
|
hope i found correct email.... if not ehh i have no clue how to find ur email hehe
But i can post the whole thing in here... |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Mon Apr 17, 2006 7:04 pm Post subject: Realy would love some help here... |
|
|
i'll post the whole thing here...
| Code: |
<icecast>
<limits>
<clients>100</clients>
<sources>20</sources>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>
<authentication>
<!-- Sources log in with username 'source' -->
<source-password>forsure</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>forsure</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>myuser</admin-user>
<admin-password>shait</admin-password>
</authentication>
<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->
<!-- This is the hostname other people will use to connect to your server.
It affects mainly the urls generated by Icecast for playlists and yp
listings. -->
<hostname>zzz.www.xxx.yyy</hostname>
<!-- You can use these two if you only want a single listener -->
<!--<port>8000</port> -->
<!--<bind-address>127.0.0.1</bind-address>-->
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8020</port>
<bind-address>zzz.www.xxx.yyy</bind-address>
</listen-socket>
<!--
<listen-socket>
<port>8021</port>
<ssl>1</ssl>
</listen-socket>
-->
<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</master-password>-->
<!--<master-relay-auth>1</master-relay-auth>-->
<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions here.
The default is 0 -->
<!--<relays-on-demand>1</relays-on-demand>-->
<!-- Request the master server to redirect new listeners to this slave
the details passed are based on <hostname> and <port> -->
<!--<master-redirect>1</master-redirect>-->
<!-- Relays. State connection information, and by default
request inline metadata for mp3 streams if available.
An on-demand relay will only retrieve the stream if
there are listeners connected -->
<relay>
<server>zzz.www.xxx.yyy</server>
<port>6160</port>
<mount>/;stream.nsv</mount>
<local-mount>/stream01.nsv</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords -->
<mount>
<mount-name>/stream01.nsv</mount-name>
<max-listeners>991</max-listeners>
<burst-size>65536</burst-size>
<hidden>0</hidden>
<authentication type="url">
state username/password if url requires it
<option name="username" value=""/>
<option name="password" value=""/>
<option name="add" value="http://myserver.com/userauth/add_ppv.php"/>
<option name="remove" value="http://myserver.com/userauth/del_ppv.php"/>
</authentication>
</mount>
<fileserve>1</fileserve>
<!-- set the mountpoint for a shoutcast source to use, the default if not
specified is /stream but you can change it here if an alternative is
wanted or an extension is required
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/local/share/icecast</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/home/icecast/icecast/log</logdir>
<webroot>/home/icecast/icecast/web</webroot>
<adminroot>/home/icecast/icecast/admin</adminroot>
<!-- <pidfile>/home/icecast/icecast/icecast.pid</pidfile> -->
<!-- <ssl_certificate>/usr/local/share/icecast/icecast.pem</ssl_certificate> -->
<!-- Aliases: treat requests for 'source' path as being for 'dest' path
May be made specific to a port or bound address using the "port"
and "bind-address" attributes.
-->
<!--
<alias source="/foo" dest="/bar"/>
-->
<!-- Aliases: can also be used for simple redirections as well,
this example will redirect all requests for http://server:port/ to
the status page
-->
<alias source="/" dest="/status.xsl"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <playlistlog>playlist.log</playlistlog> -->
<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
<!-- If logarchive is enabled (1), then when logsize is reached
the logfile will be moved to [error|access|playlist].log.DATESTAMP,
otherwise it will be moved to [error|access|playlist].log.old.
Default is non-archive mode (i.e. overwrite)
-->
<!-- <logarchive>1</logarchive> -->
</logging>
<security>
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>
|
There are several of the relays and mounts, this is just for my testing before we "upgrade" all servers.. would be nice to have 1 up'n running first..
All "relays" comes from Shoutcast servers, this due to we have several servers relaying of 1 shoutcast server and we use icecast for user authentication... If you have a better solution that u know woule work GREAT for us streaming live video and music. please let me know...
if i use this
| Code: |
<relay>
<server>zzz.www.xxx.yyy</server>
<port>6160</port>
<mount>/;stream.nsv</mount>
<local-mount>/stream01.nsv</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
|
i get Segmentation error
if i use
| Code: |
<relay>
<server>zzz.www.xxx.yyy</server>
<port>6160</port>
<mount>/</mount>
<local-mount>/stream01.nsv</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
|
i get segmentation error
if i use
| Code: |
<relay>
<server>zzz.www.xxx.yyy</server>
<port>6160</port>
<mount>/stream.nsv</mount>
<local-mount>/stream01.nsv</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
|
it starts ok, but Shoutcast doesnt recognize the "request" for /stream.nsv
And would be nice with a "how to" on the file on demand stream.. still not sure if i can use 1 mount to stream 20 files on demand, or if i have to use 20 mounts with 1 file on each, nor how they access the "file" they request...
Thnks for any help... |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Tue Apr 18, 2006 1:11 am Post subject: Suuper thnks |
|
|
thnks for Suuuper support KarlH
Now it's all up'n running...
And it works great with just the add thing i used...
my php script sends 1 back and if i remeber correct that should do the trick..
Or is it now improved even more ?? |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Apr 18, 2006 1:23 am Post subject: |
|
|
there will of been plenty of changes since 2.2kh6 to the current code, I tend to list them in the NEWS file on each release. Most of the time it has been internal work
Thanks for reporting the bug, a missed check causing a segv. kh5 will have it in.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
