Le lundi 25 janvier 2010 18:20:49, polemon a écrit :
> Hello,
Hi Polemon !
> I'm using output.icecast.aacplusenc() and output.shoutcast.aacplusenc().
> The setup works rather good, but from time to time, the aacplusenc process
> finishes and enters a zombie state (defunct). This makes liquidsoap
> unresponsive. The only solution is to restart liquidsoap.
>
> I was wondering if that's a bug in liquidsoap (like, shouldn't waitpid() or
> something capture finished processes?), or is this related to an internal
> aacplusenc bug?
>
> I'd like some suggestions how I could work around that problem.
> The problem occurs about once every 24 hours.
Hmmm...
When I implemented external encoders, I realized that most of the external
encoders assume that they encode a finite amount of data. Hence, most of them
cannot run indefinively.
For this reason, I programmed it to restart the encoder after some time,
precisely 1 hour. Have you tweaked this parameter to 24 hours ?
Another possible explanation is that this restart is desactivated and the
encoding program cannot run for more that 24h.
Anyway, there can be several solutions to this problem:
* If the automatic restart is desactivated (parameter restart_encoder_delay
being negative), you may try to set it to a value lower than 24h.
* Use the internal AAC+ encoder. If you have only one AAC+ output, I believe
this is the best solution. In this case, there is no external process, so no
risk of any crash...
Romain
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
