From: Audiodef O. <on...@au...> - 2011-09-29 16:00:18
|
I've found what's going on in this case. I was messing with the log file as root, and that prevented user liquidsoap from accessing it: init: exception encountered during start phase: Sys_error("/usr/local/etc/liquidsoap/liquidradio.log: Permission denied") I only found this out when I tried to start my script manually. I think the init script needs to pass errors like this to the console. On 09/29/11 15:55, Audiodef Online wrote: > Furthermore, I just observed that if I wait a few minutes, the init > script SAYS that liquidsoap has been stopped/started, whatever, but > there is no such process when I look for the name of my script > "main.liq" using ps aux | grep main. > > Looks like something is wrong somewhere... > > On 09/29/11 15:52, Audiodef Online wrote: >> However, if I wait a few minutes, the pid is stopped when I try >> /etc/init.d/liquidsoap restart/stop again. I don't think I should have >> to wait, right? Shouldn't it be killed immediately? >> >> On 09/29/11 15:51, Audiodef Online wrote: >>> I spoke too soon. The init script is back to not stopping the pid, and >>> I've zero idea why. >>> >>> On 09/29/11 15:14, Audiodef Online wrote: >>>> Thus far, it seems to be working now. There must have been a bug in the >>>> beta 3 init script...? >>>> >>>> On 09/29/11 15:12, Audiodef Online wrote: >>>>> Update: I forgot to copy the script from the latest sources I >>>>> downloaded. I don't know if the Gentoo init script has changed, but I >>>>> will post as to whether or not this helped. >>>>> >>>>> On 09/29/11 15:00, Audiodef Online wrote: >>>>>> I mentioned this in another post, but this is apparently an issue, at >>>>>> least for me, on its own now. >>>>>> >>>>>> My init script has stopped working properly, and I'm at a loss as to >>>>>> why, because even when I go back to the script I was using that USED to >>>>>> work, /etc/init.d/liquidsoap restart or stop still cannot kill the pid. >>>>>> I don't even know where to look for info to troubleshoot this, because >>>>>> the log I tell my script to write to has no info on any crashes or >>>>>> segv's, and there's nothing at all in /usr/local/var/log/liquidsoap. >>>>>> >>>>>> This started happening when I was on beta-3, and continues to happen >>>>>> since fetching the latest development code this morning. >>>>>> >>>>>> Other than that, I have changed nothing in the init script or anything >>>>>> else anywhere on my system since the time when this was working - that's >>>>>> why I'm confused about this. >>>>>> >>>>>> Where can I begin? >>>>>> >>>>>> Damien >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> All the data continuously generated in your IT infrastructure contains a >>>>>> definitive record of customers, application performance, security >>>>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>>>> sense of it. Business sense. IT sense. Common sense. >>>>>> http://p.sf.net/sfu/splunk-d2dcopy1 >>>>>> _______________________________________________ >>>>>> Savonet-users mailing list >>>>>> Sav...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/savonet-users >>>>>> >>>>> ------------------------------------------------------------------------------ >>>>> All the data continuously generated in your IT infrastructure contains a >>>>> definitive record of customers, application performance, security >>>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>>> sense of it. Business sense. IT sense. Common sense. >>>>> http://p.sf.net/sfu/splunk-d2dcopy1 >>>>> _______________________________________________ >>>>> Savonet-users mailing list >>>>> Sav...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/savonet-users >>>>> >>>> ------------------------------------------------------------------------------ >>>> All the data continuously generated in your IT infrastructure contains a >>>> definitive record of customers, application performance, security >>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>> sense of it. Business sense. IT sense. Common sense. >>>> http://p.sf.net/sfu/splunk-d2dcopy1 >>>> _______________________________________________ >>>> Savonet-users mailing list >>>> Sav...@li... >>>> https://lists.sourceforge.net/lists/listinfo/savonet-users >>>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2dcopy1 >>> _______________________________________________ >>> Savonet-users mailing list >>> Sav...@li... >>> https://lists.sourceforge.net/lists/listinfo/savonet-users >>> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> _______________________________________________ >> Savonet-users mailing list >> Sav...@li... >> https://lists.sourceforge.net/lists/listinfo/savonet-users >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Savonet-users mailing list > Sav...@li... > https://lists.sourceforge.net/lists/listinfo/savonet-users > |