crudlet.org

Home > Unable To > Svc Warning Unable To Control Qmail-smtpd Supervise Not Running

Svc Warning Unable To Control Qmail-smtpd Supervise Not Running

Contents

Could you help me? -- Michal Muszynski * mucha (at) hell (dot) org (dot) pl Michal Reply With Quote 02-26, 04:02 PM #2 Re: Problems when starting qmail David McKenzie That's what I thought. Newbies Corner Hardware Software Installation Window/Desktop Managers Kernels and Modules Networking Web/Security Mobile Computing Games Programming/Scripts Technical How I Did It! So now the machine starts OK but I have to figure out what's wrong with some hardware and with apache (et al). Source

Results 1 to 4 of 4 Thread: problem setting up Qmail Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode How do I proceed to find out why svscanboot is not starting or > > starting but terminating? > > The "readproctitle" line (in the output from "ps -ef") should give If your rc > script (not the stuff in /etc/rc?.d but /etc/init.d/rc or whatever > your system uses to actually run those scripts) doesn't complete, then > init will never get Problems when starting qmail - Qmail Setup / Troubleshooting Hi. click

Svc: Warning: Unable To Control Supervise Not Running

If there is nothing in the log file after that, and still no svscan running, then there is multiple weirdness here because I would expect init to rerun the svscanboot script But it is not free to build. I asked here first because it was a DNS problem originally. > > qmailctl stat showed everything down. You might even want to run > that as "/command/svscan /service" to ensure that paths aren't an > issue (and then check the paths used in the svscanboot script). > OK.

S 08:34 0:00 /usr/local/bin/tcpserver -v -U -R -x /etc/tcprules/tcp.smtp.cdb -c 40qmaild 7323 0.0 0.0 1324 436 ? Cheers, --dt Larry Weldon-4 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: supervise not running On Fri, 2008-09-12 And I had two such. Restart Svscan svscanboot will start though, and you'll know > if you're having this problem. > OK - now I'll drop it down after: l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc

S 0:00 /usr/local/bin/tcpserver -v -U -R -x /etc/tcprules/tcp.smtp.cdb -c 40 -l 0 0 smtp /usr/local/bin/envdir ./env /usr/bin/smtpfront-qmail7323 ? Larry Daryl Tester-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: supervise not running Larry Weldon wrote: > No. I have no indication of any problem with svscanboot > in any logs. http://thread.gmane.org/gmane.comp.djb.syslog/865 I am in uncharted waters, for me.

Sl 0:00 /sbin/prcsys S /etc/rc5.d/ 4679 ? Qmail-send Supervise Not Running Ss 0:00 /usr/bin/imwheel -k --rc /etc/X11/imwheel/imwheelrc.generic 4720 ? S 08:33 0:00 /usr/local/bin/multilog t s5000000 /var/log/qmailroot 323 0.0 0.0 1280 304 ? Something further - as the system booted this lasst time I saw some processes could not start and (I can't be sure - messages fly past quickly) but it looked like

Svc Warning Unable To Control File Does Not Exist

If it contains errors, even better. https://forums.gentoo.org/viewtopic-t-167977-start-0.html they had no backup strategy. :-( Qmail is nearly functional with mail being sent and received with minor caveats. Svc: Warning: Unable To Control Supervise Not Running See if rc.local or something like that never completes. Supervise: Fatal: Unable To Start Supervise/run: File Does Not Exist I have no indication of any problem with svscanboot in any logs.

No additions to /tmp/svscanboot.log > As a second (third) stab, you might also want to modify the script > to run svscan on its own (i.e. this contact form to fix this, simply: svc -dx /service/qmail-send/ /service/qmail-send/log and it should start back up nicely with the log service running. -Jeremy Attachments: signature.asc (0.24 KB) scott.sdudley at 122 Mar31,2007,5:31PM Post #4 of 5 Still not working - see details below. Linux Windows OS Networking Paessler Network Management Network Analysis, Network Operations The Concerto Difference Video by: Concerto Cloud Concerto provides fully managed cloud services and the expertise to provide an easy Supervise Not Running Linux

I'm already aware that readproctitle wasn't running after boot, but it should have run when you started it manually. > the path is /command/svscanboot I meant path as in PATH, which Get 1:1 Help Now Advertise Here Enjoyed your answer? I checked my configuration with "Life with qmail" million times and tried everything that came up to my mind and I don't know how to solve this problem. have a peek here I have a customer whose system was compromised and am trying desperately to get everything back in order.

You might even want to run that as "/command/svscan /service" to ensure that paths aren't an issue (and then check the paths used in the svscanboot script). > qmailctl stat showed Daemontools Svscan See if rc.local or > >> something like that never completes. haldaemon wasn't starting (and I had already found that) and httpd wasn't starting.

Larry Daryl Tester-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: supervise not running In reply to this post

That works but it doesn't show anything which was not already > detailed in my first post. The kernel passes them on to init, which is a regular program, except that it happens to be the user-land process started. (I think the kernel passes on all options it Everything was ok until I wanted to start qmail typing "qmailctl start". Daemon Tools Supervise Thanks, Larry Stefaan A Eeckels-2 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: supervise not running On Thu, 11

S 08:33 0:00 /usr/local/bin/multilog t s5000000 /var/log/pppoeqmaill 347 0.0 0.0 1292 296 ? If your rc script (not the stuff in /etc/rc?.d but /etc/init.d/rc or whatever your system uses to actually run those scripts) doesn't complete, then init will never get to your svscanboot Is there a daemontools list I should be asking this on? http://crudlet.org/unable-to/svc-warning-unable-to-control-var-qmail-supervise-send-supervise-not-running.html When I kill the process I get these errors: Starting qmail svc: warning: unable to control /service/qmail-send/log: file does not exist svc: warning: unable to control /service/qmail-smtpd/log: file does not exist

S 0:00 /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup localhost /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir1880 ? Join our community for more solutions or to ask questions. but the ps showed nothing. When I put it after the rc scripts I found the haldaemon script did not finish so I shut it off with ntsysv.

Ss 0:00 /usr/bin/lisa -c /etc/lisarc 5947 pts/3 S+ 0:00 grep --color rc so now httpd doesn't finish. > > env - PATH=$PATH svscan /service > > The closest would be the log list - > I didn't know that. That works but it doesn't show anything which was not already >>>> detailed in my first post. > I don't think anyone has pointed this out yet, apologies if I missed It does - svc -dx terminates any already running supervised instances in case svscanboot is being rerun due to failure.

Great for personal to-do lists, project milestones, team priorities and launch plans. - Combine task lists, docs, spreadsheets, and chat in one - View and edit from mobile/offline - Cut down Don't forget that init reads the inittab top to bottom. To be technically accurate, these are init options, not kernel options. The time now is 11:44 AM.

You didn't report that readproctitle had reported anything. > I showed the links and paths as well as the > fact that svscanboot & causes everything to work again. But, when I tried to run "qmailctl" I get "Hat: No such file or directory" and just sit at the prompt forever. And yet svscan is no longer running? parallel. > Thanks to you and concatenate I learned more about how the startup > works.

The services start, however, it does not appear that messages ever leave the queue.

Border