similar to: ices spawning zombie perl processes

So, I finally had some time to go through my scripts and after some poking and fixing I discovered that there is nothing wrong with my Perl script. It may be ugly and inefficient but it gets the job done and closes without throwing errors when run thru perl outside of ices. However, ices continues to produce the defunct processes, a listing of ices and icecast2 related material from ps is

do ices-ad.pm perl script work with ices2? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20050826/80499d8d/attachment.htm

/me grumbles about upcoming finals: I note that the mountpoint entry displays the current songs title and artist, but not the album. In the particular case of my station, album is often more important (recognizable) as there are a variety of pop/classical artists who do music for anime. So I'd like to add an album nature but am going to need a quick overview on how stats.xml is generated.

Last I checked, iTunes was unable to play my static playlist ogg vorbis stream. Assuming this is expected behaviour and not an anomaly; Does iTunes 4 resolve this issue? --thanks Michael Edwards http://www.walledcity.ca <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

According to the oddcast website ices by default sends ice-public: 0 when informing directories of itself. What changes do I need to make to my configuration file to change this behaviour? --thanks Michael Edwards http://walledcity.ca <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

I can heartily garuntee that if your script doesn't return anything ices will whine about only getting newlines and promptly terminate. For you this is desired behaviour. For me it was undesired.. god it took me awhile to work the kinks out of that script... --thanks Michael Edwards http://www.walledcity.ca/ >===== Original Message From Karl Heyes <karl@pts.tele2.co.uk> =====

Doesn't ices only read the first line returned from the script? --thanks Michael Edwards http://www.walledcity.ca/mars/ >===== Original Message From Karl Heyes <karl at pts.tele2.co.uk> ===== >On Sat, 2003-03-01 at 18:41, Adam Scriven wrote: > >> Is there anywhere I can go to get detailed information on how this works? >> I'm wondering about passing information

Hello, I'd like to be able to run multiple instances of Ices (2.0), each with their own playlist and streaming to different mountpoints. Although I'm relatively new to Ices and Icecast, so far I have had little trouble getting it running with two or more instances of Ices feeding off fixed playlists (files). I'd like to be able to set each instance of Ices to run with script based

I get this error every time I try to start ices: ices: relocation error: ices: undefined symbol: resolver_initialize I'm running a Celeron with 64MB of RAM which up until last moth, ran ices with absolutely no complaint. Here are the steps I've taken to resolve this problem: Full update from debian/unstable -no effect Full reinstall of all dependencies using CVS checkouts -ices fails

That's a little odd, there are streams listed at yp.icecast.org... What's up with that? And of course my question on other directory servers still stands. --thanks Michael Edwards http://www.walledcity.ca >===== Original Message From Manuel Lora <vanguardist@cox.net> ===== >Icecast.org no longer hosts the yp directory. > >ml > > >On Saturday 05 April 2003

[2003-02-20 15:24:05] EROR playlist-script/playlist_script_get_filename Couldn't open pipe to program "/usr/local/icecast2/ices-ad.pm" Segmentation fault I'm running a perl script that apparently (rarely) kills ices for this reason. The error occurs approximately once per day for no apparent reason. For the rest of that period the script runs fine. In fact, after some

I've been trying to track down this mysterious 'icestats' file that the status.xsl and status2.xsl read data from. There is no physical file as far as I can tell, but a perusal of the code seems to indicate that the server generates it on the fly when the XSL file requests it. So then I tried servername.com:8000/icestats but I got nothing. So I really got nothing, I would prefer

I am having a problem with my Samba machine, here are the details. The machine in question is running FreeBSD 4.5-RELEASE on a Dual PIII/XEON 550. I downloaded the source for Samba-2.2.3a and compiled without a hitch. I also setup SWAT to run through an stunnel(ssl) pipe. SWAT configuration of Samba worked great, but if I start the daemons(smbd & nmbd) from SWAT, smbd seems to keep creating

Hello, I changed my config for ices and added passthru. I will see how it will run now. I have realtime I think: [2003-11-24 22:54:25] INFO ices-core/main Streamer version IceS 2.0-kh47 [2003-11-24 22:54:25] INFO ices-core/main libshout version 2.0-kh22 [2003-11-24 22:54:25] INFO ices-core/main realtime scheduling has been enabled

Hello, I will take your last version, but I have fresher news about the bug that occurs every mornings in fact... I think this is ntpdate which is causing the problem, as the time of the machine change for more than one second. Here is all the info: 09:46:17 up 1 day, 1:22, 2 users, load average: 0.60, 0.71, 0.68 86 processes: 84 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 10.4%

Hi all, I am trying to simulate load on on the icecast server using ices source streaming client. I have setup 300 mount points and using the same playlist to send to one icecast server. However, I see that the icecast server is timing out because the source is not sending the data fast enough. Could anyone please explain the internal workings of ices streaming client and how it sends the

Hello Asterisk users, We noticed that on Asterisk 12 zombie processes are being generated - They are released after a while, but we have around 10-20 zombie processes running. We are not sure if this is a normal behavior or an issue. We saw in the documentation that the bridging module creates zombie processes - is it related? Thank you, Yaron. -------------- next part -------------- An HTML

I'm monitoring Asterisk with Nagios. Nagios constantly alerts because of too many zombie processes. I eventually had to disable the notification for the alert but why does Asterisk create so many zombie processes, I've see more than 30 at times and it generally stays in the 20s... just seems unusual and wondering if it's harmful, thanks in advance. -------------- next part

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie state, the parent process (systemd) /proc/1/status shows no pending signals. 4) Attaching gdb to

Hi... now, I have a trouble on one source machine. I'm using oss to get the sound. encoding is ok with ices 2.0kh60 but with ices 2.0.1, I'm getting [2006-06-07 23:17:48] INFO ices-core/main IceS 2.0.1 started... [2006-06-07 23:17:48] EROR input-oss/oss_open_module Couldn't set sampling rate [2006-06-07 23:17:48] EROR input/input_loop Couldn't initialise input module