named-chroot.service hangs in F19

Sam Varshavchik mrsam at courier-mta.com
Thu Jul 4 22:15:02 UTC 2013


Sam Varshavchik writes:

> systemctl start named-chroot.service hangs for a minute, or so.
>
> ps shows that named is running, but systemctl is trying to execute the  
> following:
>
> root      2036  2035  0 09:53 pts/0    00:00:00 /usr/bin/systemd-tty-ask- 
> password-agent --watch

Follow-up, I don't think this has anything to do with systemd-tty-ask- 
password-agent. I set up named-chroot on another server, in its default  
configuration, and it starts fine, and I can see that systemctl also  
executes systemd-tty-ask-password-agent, as part of starting the service.

The problem on the problematic server has to do with systemd itself. For  
some reason the service remains in "Activating" state, and systemd never  
believes that the server finished starting.

After executing "systemctl start named-chroot.service", and its start  
hanging, a minute later, "systemctl status named-chroot.service" comes back  
with:

named-chroot.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled)
   Active: activating (start) since Thu 2013-07-04 18:02:35 EDT; 1min 6s ago
  Process: 1650 ExecStart=/usr/sbin/named -u named -t /var/named/chroot $OPTIONS (code=exited, status=0/SUCCESS)
  Process: 1645 ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf (code=exited, status=0/SUCCESS)
  Process: 1552 ExecStartPre=/usr/libexec/setup-named-chroot.sh /var/named/chroot on (code=exited, status=0/SUCCESS)
  Process: 1509 ExecStartPre=/usr/libexec/generate-rndc-key.sh (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/named-chroot.service
           └─1652 /usr/sbin/named -u named -t /var/named/chroot

[ syslog messages from named, unimportant ]

I can manually start /usr/sbin/named -u named -t /var/named/chroot, and it  
runs happily, but systemd does not believe that the service has started, and  
kills the entire process group, after the default 90 second timeout.

So, what's systemd's problem, here?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130704/718e9ef6/attachment.sig>


More information about the users mailing list