I have upgraded inn today, and I have problem with init script. # /etc/init.d/innd start * Starting innd ... Starting innd. [ !! ] But, it is running : # ps axf | grep inn 6426 ? Ss 0:00 /usr/lib/news/bin/innd -p 4 and I can use/access to it.
Does this always happen when you start Inn? If so, please use the --debug option: /etc/init.d/innd --debug status >innd.start.log 2>&1 Then attach innd.start.log to this bug. Thanks!
Created attachment 117451 [details] innd.start.log when innd is not running (after /usr/lib/news/bin/rc.news stop)
I just realised I wrote "status" instead of "start": /etc/init.d/innd --debug start >innd.start.log 2>&1 Please attach the log resulting from that. I apologize for the inconvenience. (And please use "/etc/init.d/innd stop" to stop Inn instead of running rc.news directly.)
(In reply to comment #3) > I just realised I wrote "status" instead of "start": > > /etc/init.d/innd --debug start >innd.start.log 2>&1 I'll do it. > Please attach the log resulting from that. I apologize for the inconvenience. > (And please use "/etc/init.d/innd stop" to stop Inn instead of running rc.news > directly.) How can I stop a service never started ? # /etc/init.d/innd stop * WARNING: innd has not yet been started. Did you really understand my problem ? I know my english is not really good.
Created attachment 117761 [details] innd.start.log /etc/init.d/innd --debug start >innd.start.log 2>&1
Yes, I really understood your problem. :-) (Your English is fine, btw. Way better than my French. :) ) As long as this problem persists, you can't stop Inn regularly, of course. I just wanted to make sure that you generally use the init script (if it works... ;-) ).
(In reply to comment #6) > Yes, I really understood your problem. :-) (Your English is fine, btw. Way > better than my French. :) ) Then, your French must be very bad :-) > As long as this problem persists, you can't stop Inn regularly, of course. You get it ! ;-) > I just wanted to make sure that you generally use the init script (if it > works... ;-) ). Of course I do. I use Gentoo only (almost) for its init scripts :-D
Oh, yes, my French was barely good enough to get to Airbus in Toulouse in a cab. :) Anyway, this is a very strange issue. I'm going to set up a dedicated testing environment. Please post both your "emerge --info" and the output from "emerge -pv =net-nntp/inn-2.4.3".
Created attachment 117768 [details] emerge --info
Created attachment 117769 [details] emerge emerge -pv =net-nntp/inn-2.4.3
It seems that init script is looking for /usr/lib/news/bin/rc.news running. But this script just launch innd and is not running after (if I understand well). So it won't never find pidof /usr/lib/news/bin/rc.news. But may be I'm very wrong.
May be I'm not wrong at all :-) this modification is surely the cause : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-nntp/inn/files/innd?r1=text&tr1=1.1.1.1&r2=text&tr2=1.2&diff_format=h
Actually, it *does* find the pid: +++ /bin/pidof -x /usr/lib/news/bin/rc.news + pids=26011 + [[ -z 26011 ]] + [[ -s '' ]] + return 0 (Excerpt from the log you posted.) I couldn't reproduce this problem at all. With any combination of USE flags (including your own, of course) it just works for me both in my testing environment as well as on two production servers I'm running. The change you've noticed in the init script is absolutely correct and should just as it is. I'm sorry but this must be some strange local issue.
