You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also noticed that after reboot, /run is there but the httpd subdir is gone. Have to recreate it manually after every reboot. Put the workaround in /etc/rc.local.
Encountered the same error with fresh ROCKS 7 installation (includes a total of 11 rolls: area51-7.0-0, base-7.0-2, CentOS-7.4-1708, core-7.0-2, fingerprint-7.0-0, ganglia-7.0-2, hpc-7.0-0, kernel-7.0-0, Updates-CentOS-7.4-1708-2017-12-01, yumfix-7.0-0, zfs-linux-0.7.3-2). Everything seems to be normal right after installation. But errors, including failed to start httpd due to missing /run/httpd directory, occurred after first reboot.
It turned out httpd is not the only victim here. libstoragemgmt, iptables, fail2ban, named also failed to start due to missing directories under /run.
These directories are supposed to be created automatically at startup with systemd-tmpfiles-setup.service, which is deleted in the startup proces: Nov 14 17:34:19 raccoon systemd: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
Actually, another 11 systemd services/targets are deleted with the same reason:
plymouth-read-write.service
rhel-autorelabel-mark.service
system-machine-id-commit.service
rhel-autorelabel.service
systemd-update-done.service
systemd-journal-catalog-update.service
systemd-update-utmp.service
auditd.service
rhel-import-state.service
selinux-policy-migrate-local-changes@ targetd.service and
local-fs.target
I traced /var/log/messages and found that ip6tables.service failed to start because of a syntax error in "/etc/lib/systemd/system/ip6tables.service", which is a know bug for (RedHat 7.4): After=syslog.target,iptables.service
the comma should be space: After=syslog.target iptables.service
Magically, after I corrected the ip6tables.service file, all the 12 systemd services/targets started normally and therefore httpd and the other 4 services started normally.
I am still not sure why the failure in ip6tables.service causes such result. But the problem is solved for now.
Facing the same problem in July 2019. head Node crashes after installation as every other services fails to start. Will enabling ipv6 on the network solve the problem?
Also "/etc/lib/systemd/system/ip6tables.service" does not exists on my installation.
Activity
jdkruzr commentedon Jul 29, 2018
Just wanted to chime in to say that it's July and this still appears to be an issue in ROCKS 7.
kirbyjason commentedon Aug 16, 2018
Also noticed that after reboot, /run is there but the httpd subdir is gone. Have to recreate it manually after every reboot. Put the workaround in /etc/rc.local.
jonesuki commentedon Nov 15, 2018
Encountered the same error with fresh ROCKS 7 installation (includes a total of 11 rolls: area51-7.0-0, base-7.0-2, CentOS-7.4-1708, core-7.0-2, fingerprint-7.0-0, ganglia-7.0-2, hpc-7.0-0, kernel-7.0-0, Updates-CentOS-7.4-1708-2017-12-01, yumfix-7.0-0, zfs-linux-0.7.3-2). Everything seems to be normal right after installation. But errors, including failed to start httpd due to missing /run/httpd directory, occurred after first reboot.
It turned out httpd is not the only victim here. libstoragemgmt, iptables, fail2ban, named also failed to start due to missing directories under /run.
These directories are supposed to be created automatically at startup with systemd-tmpfiles-setup.service, which is deleted in the startup proces:
Nov 14 17:34:19 raccoon systemd: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/startActually, another 11 systemd services/targets are deleted with the same reason:
I traced /var/log/messages and found that ip6tables.service failed to start because of a syntax error in "/etc/lib/systemd/system/ip6tables.service", which is a know bug for (RedHat 7.4):
After=syslog.target,iptables.servicethe comma should be space:
After=syslog.target iptables.serviceMagically, after I corrected the ip6tables.service file, all the 12 systemd services/targets started normally and therefore httpd and the other 4 services started normally.
I am still not sure why the failure in ip6tables.service causes such result. But the problem is solved for now.
sunracesuraj commentedon Jul 9, 2019
Facing the same problem in July 2019. head Node crashes after installation as every other services fails to start. Will enabling ipv6 on the network solve the problem?
Also "/etc/lib/systemd/system/ip6tables.service" does not exists on my installation.
EllisonYim commentedon Dec 4, 2019
You install rocks 7 sucessfull?I can not install the frondant node. Reoport mod_ssl-2.4.6-67.el7.centos.x86_64 requires httpd