svc: warning: unable to control .: file does not exist

svc: warning: unable to control .: file does not exist

[Scott Dudley]

Please forgive me if this isn't the appropriate forum but I was unable to
locate a general daemontools forum.

I was exposed this week for the first time to both qmail and daemontools. 
I have a customer whose system was compromised and am trying desperately
to get everything back in order.  And no... they had no backup strategy. 
:-(

Qmail is nearly functional with mail being sent and received with minor
caveats.

My sticking point is this... While going through the Life With Qmail
HOWTO, I get to the point of testing the start/stop of qmail via qmailctl.
 Qmailctl stat returns the message:

/service/qmail-send/log: unable to open supervise/ok: file does not exist

I'm then instructed to do the following:

cd /service/qmail-smtpd/log
svc -d .

Which returns:

svc: warning: unable to control .: file does not exist

Here's what the files look like:

[root@monster-isp log]# ls -l /service/qmail-send
lrwxrwxrwx  1 root root 31 Jun 13  2005 /service/qmail-send ->
/var/qmail/supervise/qmail-send
[root@monster-isp log]# ls -lR /var/qmail/supervise/qmail-send
/var/qmail/supervise/qmail-send:
total 20
drwxr-xr-x  2 root root 4096 Mar 31 14:46 log
-rwxr-x--x  1 root root   29 Jun 14  2005 run
drwx------  2 root root 4096 Mar 31 01:45 supervise

/var/qmail/supervise/qmail-send/log:
total 4
-rwxr-x--x  1 root root 88 Mar 31 00:38 run

/var/qmail/supervise/qmail-send/supervise:
total 16
prw-------  1 root root  0 Mar 31 01:45 control
-rw-------  1 root root  0 Jun 14  2005 lock
prw-------  1 root root  0 Jun 14  2005 ok
-rw-r--r--  1 root root 18 Mar 31 01:45 status

I also performed an strace:

[root@monster-isp log]# strace svc -d .
execve("/usr/local/bin/svc", ["svc", "-d", "."], [/* 21 vars */]) = 0
uname({sys="Linux", node="monster-isp.monster-isp.com", ...}) = 0
brk(0)                                  = 0x9855000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=43377, ...}) = 0
old_mmap(NULL, 43377, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fec000
close(3)                                = 0
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\317"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1525032, ...}) = 0
old_mmap(0xa28000, 1223868, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xa28000
mprotect(0xb4c000, 27836, PROT_NONE)    = 0
old_mmap(0xb4d000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x124000) = 0xb4d000
old_mmap(0xb51000, 7356, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb51000
close(3)                                = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7feb000
mprotect(0xb4d000, 8192, PROT_READ)     = 0
mprotect(0xa24000, 4096, PROT_READ)     = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7feb8e0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7fec000, 43377)               = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
open(".", O_RDONLY|O_NONBLOCK)          = 3
chdir(".")                              = 0
open("supervise/control", O_WRONLY|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
write(2, "svc: warning: unable to control "..., 55svc: warning: unable to
control .: file does not exist
) = 55
fchdir(3)                               = 0
exit_group(0)                           = ?

I hope that's not too much for one posting.

If anyone can steer me in the right direction, I would be forever in your
debt.  I'm extremely impressed with what I've seen thus far of both
product and am anxious to learn and begin using both.  Oh to finally say
farewell to sendmail.  :-)

Thanks.

Re: svc: warning: unable to control .: file does not exist

[Paul Jarc]

Scott Dudley <scott.sdudley@122.telesoft.com> wrote:
> /service/qmail-send/log: unable to open supervise/ok: file does not exist

If this happens for all services and loggers, then I'd guess svscan is
not running.  (This could be because you created /service before
installing daemontools, or because you didn't reboot after installing,
if you're on BSD.)  If it happens only for loggers (all or some), then
I'd guess you created the log directories after their parent services
were already running; svscan checks for a logger only once when it
first notices a server.  In either case, you can try rebooting to make
sure everything starts up cleanly.


paul

Re: svc: warning: unable to control .: file does not exist

[Scott Dudley]

> Scott Dudley <scott.sdudley@122.telesoft.com> wrote:
>> /service/qmail-send/log: unable to open supervise/ok: file does not
>> exist
>
> If this happens for all services and loggers, then I'd guess svscan is
> not running.  (This could be because you created /service before
> installing daemontools, or because you didn't reboot after installing,
> if you're on BSD.)  If it happens only for loggers (all or some), then
> I'd guess you created the log directories after their parent services
> were already running; svscan checks for a logger only once when it
> first notices a server.  In either case, you can try rebooting to make
> sure everything starts up cleanly.

Paul,

I failed to mention that the log folders were missing and no, I've not
rebooted since.

This is a Fedora Linux system.  Is there any was to restart svscan without
rebooting?

[root@monster-isp log]# ps awux|grep svscan
root      4373  0.0  0.1  2364 1052 ?        Ss   Mar23   0:00 /bin/sh
/command/svscanboot
root      4763  0.0  0.0  2736  332 ?        S    Mar23   0:01 svscan
/service

>
>
> paul
>

Re: svc: warning: unable to control .: file does not exist

[Paul Jarc]

Scott Dudley <scott.sdudley@122.telesoft.com> wrote:
> This is a Fedora Linux system.  Is there any was to restart svscan without
> rebooting?

On Linux, you can kill it and then run "svc -dx" on all your services
and loggers.  init will restart svscan.


paul