Description of problem: systemctl start httpd hangs with : 2systemd-tty-ask-password-agent --watch" and does not return. Version-Release number of selected component (if applicable): 2.4 How reproducible: 100% Steps to Reproduce: systemctl start httpd.service Actual results: it starts the httpd in the background, but systemctl does not return. [root@s113 ~]# pstree -up | grep ask |-sshd(743)-+-sshd(1444)---bash(1450)---systemctl(3811)---systemd-tty-ask(3812) [root@s113 ~]# cat /proc/3812/cmdline /usr/bin/systemd-tty-ask-password-agent--watch Additional info: This bug is reported for debian years ago. This specific fedora was just upgraded from FC17 to Fc18 via yum. The httpd in questions uses the fc17 httpd.conf with minor changes in the module support. But as httpd starts in the background . After a while systemctl times out: Feb 04 19:15:53 s113.resellerdesktop.de httpd[3813]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/httpd/conf.d/sites.conf:6 Feb 04 19:15:53 s113.resellerdesktop.de httpd[3813]: [Mon Feb 04 19:15:53.170998 2013] [core:warn] [pid 3813] AH00117: Ignoring deprecated use of DefaultType in line 452 of /etc/httpd/conf/httpd.conf. Feb 04 19:17:23 s113.resellerdesktop.de systemd[1]: httpd.service operation timed out. Terminating. Feb 04 19:17:23 s113.resellerdesktop.de systemd[1]: Failed to start The Apache HTTP Server. Feb 04 19:17:23 s113.resellerdesktop.de systemd[1]: Unit httpd.service entered failed state
BugFix: "/usr/lib/systemd/system/httpd.service" Unit File changed to : ---------------------------------------------------------------------- [Unit] Description=The Apache HTTP Server After=network.target remote-fs.target nss-lookup.target [Service] Type=forking EnvironmentFile=/etc/sysconfig/httpd ExecStart=/usr/sbin/httpd $OPTIONS -k start ExecReload=/usr/sbin/httpd $OPTIONS -k graceful ExecStop=/usr/sbin/httpd $OPTIONS -k graceful-stop PrivateTmp=true [Install] WantedBy=multi-user.target ---------------------------------------------------------------------- Starts now as expected.
Additional Information: After reinstalling httpd 2.4 from scratch, it restarts nicely with the shipped systemd service file. After further investigation, it looks to me, that the systemd_module wasn't included to load on startup, after the FC17/18 upgrade. If i manually disable the systemd_module entry in /etc/httpd/conf.modules.d/00-systemd.conf I get the same result, trying to restart httpd via systemctl . The configs inside conf.modules.d were not loaded in the migrated httpd.conf from httpd 2.2 . I think, that it is safe to assume, that a migrated httpd.conf won't include this dir by default. Which means, without converting it while upgrading the distro, it has to fail for sure. As i don't expect anyone to write a convert script for the yum upgrade process, a hint on the upgrade wiki page https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 would be nice. I suggest to resolve this to "can't be fixed", except someone has a very good idea how to update the upgrade process ;)
This is somehow expected RPM behaviour. It won't touch your httpd.conf if you have done some changes in it and it creates httpd.conf.rpmnew instead. You should use some tool like rpmconf to merge these files after update or just do it manually.