Hi Martin! 2013/1/28 Martin Konečný <[email protected]>: > We've had a few instances in the past few weeks where Liquidsoap would stop > responding to telnet commands. I've tried my best to track down the source > of this problem, but with no luck thus far. > > It appears to happen randomly when "kicking" an input.harbour source via > harbor_id.kick. Once this happens, the Liquidsoap process is still running, > and I can even telnet in, but any telnet command sent will block with no > response from Liquidsoap. > > I'm going to look into whether I can get more information, what's the best > place to start? So far I've done set("log.level", 5), any other tips to help > track this down?
While working on supporting external decoders for streams, I realized that some operations done in input.http and input.harbor were not thread-safe. Typically, closing the harbor would be done in a duppy thread and could result in a race condition with the main thread reading data off that socket. Finally, duppy's tasks would be messed up, resulting in the symptoms you describe. I have addressed all I've been able to spot in a pending PR there: https://github.com/savonet/liquidsoap/pull/16 It'd be nice if you could rebuild from this branch and see if you are able to reproduce your issue with this code.. Thanks! Romain ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
