| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Thu Jul 20, 2006 8:25 am Post subject: Mountpoints disappearing after some time |
 |
|
Hello,
I have a problem I haven't been able to solve myself.
When I (re)start the server and sources (I use Ices for the sources) running, it runs fine. Only after a few hours of smooth running the mountpoints aren't accessable anymore and also dissappear from the status page.
I have found out that when I kill the processes that have been added after I started it, the mountpoints are accessable again and appear on the status page.
I hope anyone has a solution for this. 
Thanks in advance. |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Jul 20, 2006 1:49 pm Post subject: |
|
|
No information to go one really, check your error log, it sounds like icecast terminating the connection due to a timeout, which may be down to ices stalling or network trouble.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Thu Jul 20, 2006 3:44 pm Post subject: |
|
|
Sorry, forgot to post my current setup.
| Code: |
<icecast>
<limits>
<clients>85</clients>
<sources>5</sources>
<threadpool>1</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- 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></source-password>
<!-- Relays log in username 'relay' -->
<relay-password></relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password></admin-password>
</authentication>
<!-- 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>maputo.virtualbuilding.nl</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>8000</port>
</listen-socket>
<listen-socket>
<port>8011</port>
<shoutcast-compat>1</shoutcast-compat>
</listen-socket>
<!-- 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>/stream5</shoutcast-mount>-->
<!--<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>-->
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords -->
<mount>
<mount-name>/stream1</mount-name>
<max-listeners>20</max-listeners>
<dump-file>/tmp/dump-stream1</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/stream2</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<hidden>0</hidden>
<no-yp>1</no-yp>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<mount>
<mount-name>/stream2</mount-name>
<max-listeners>20</max-listeners>
<dump-file>/tmp/dump-stream2</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/stream3</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<hidden>0</hidden>
<no-yp>1</no-yp>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<mount>
<mount-name>/stream3</mount-name>
<max-listeners>20</max-listeners>
<dump-file>/tmp/dump-stream3</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/stream3</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<hidden>0</hidden>
<no-yp>1</no-yp>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<mount>
<mount-name>/stream4</mount-name>
<max-listeners>20</max-listeners>
<dump-file>/tmp/dump-stream4</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/stream1</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<hidden>0</hidden>
<no-yp>1</no-yp>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<mount>
<mount-name>/stream5</mount-name>
<max-listeners>20</max-listeners>
<dump-file>/tmp/dump-stream5</dump-file>
<burst-size>65536</burst-size>
<hidden>0</hidden>
<no-yp>1</no-yp>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
<!--<fileserve>1</fileserve>-->
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/share/icecast2</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast2</logdir>
<webroot>/usr/share/icecast2/web</webroot>
<adminroot>/usr/share/icecast2/admin</adminroot>
<!-- <pidfile>/usr/share/icecast2/icecast.pid</pidfile> -->
<!-- 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>icecast2</user>
<group>icecast</group>
</changeowner>
</security>
</icecast> |
The problem is that icecast starts new processes without a reason and there doesn't appear to be anything about it in the logs.
When I kill the extra icecast processes, my streams show up and are accessable again.
I use ices0.4 as source and it's running on the same server, so I would find it wierd that it would be a network problem.
Last edited by Anonymous on Fri Jul 21, 2006 7:27 am; edited 1 time in total |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Jul 20, 2006 11:39 pm Post subject: |
|
|
There is only one place where icecast starts processes (directly) and that is with the on-connect/on-disconnect tags which you have. I don't know what you do with those scripts but they are run when the stream starts and stops.
Other things of note are :-
you have a port 8011 as shoutcast emulation but you have no 8010 port. Are you sure you want that?
mountpoint /stream3 has a fallback mount of /stream3, probably not what you intend.
karl. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2002 phpBB Group
subRebel style by ktauber
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
