Install on CentOS 7

phillw · July 3, 2018, 9:10pm

getenforce
Permissive
root@phillw:/etc/httpd#apachectl restart
Job for httpd.service failed because the control process exited with error code. See “systemctl status httpd.service” and “journalctl -xe” for details.
root@phillw:/etc/httpd#systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-07-03 22:19:05 CEST; 48s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 16988 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 2965 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Process: 16986 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 16986 (code=exited, status=1/FAILURE)

Jul 03 22:19:05 phillw.net systemd[1]: Starting The Apache HTTP Server…
Jul 03 22:19:05 phillw.net httpd[16986]: httpd: Syntax error on line 368 of …n
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service: main process exited, …RE
Jul 03 22:19:05 phillw.net kill[16988]: kill: cannot find process “”
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service: control process exite…=1
Jul 03 22:19:05 phillw.net systemd[1]: Failed to start The Apache HTTP Server.
Jul 03 22:19:05 phillw.net systemd[1]: Unit httpd.service entered failed state.
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
root@phillw:/etc/httpd#systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-07-03 22:19:05 CEST; 1min 38s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 16988 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 2965 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Process: 16986 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 16986 (code=exited, status=1/FAILURE)

Jul 03 22:19:05 phillw.net systemd[1]: Starting The Apache HTTP Server…
Jul 03 22:19:05 phillw.net httpd[16986]: httpd: Syntax error on line 368 of /etc/httpd/conf/httpd.conf: Syntax error on line 216 of /etc/httpd/conf.d/ssl.co…t> section
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jul 03 22:19:05 phillw.net kill[16988]: kill: cannot find process “”
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service: control process exited, code=exited status=1
Jul 03 22:19:05 phillw.net systemd[1]: Failed to start The Apache HTTP Server.
Jul 03 22:19:05 phillw.net systemd[1]: Unit httpd.service entered failed state.
Jul 03 22:19:05 phillw.net systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

phillw · July 3, 2018, 9:20pm

systemctl start httpd.service
Job for httpd.service failed because the control process exited with error code. See “systemctl status httpd.service” and “journalctl -xe” for details.
root@phillw:/etc/httpd/conf#getenforce
Permissive

phillw · July 3, 2018, 9:39pm

This has been a toil, but we are at:
cd /etc/httpd/conf.d/
root@phillw:/etc/httpd/conf.d#ls
ssl.conf welcome.conf autoindex.conf README userdir.conf
root@phillw:/etc/httpd/conf.d#nano ssl.conf
root@phillw:/etc/httpd/conf.d#nano ssl.conf
root@phillw:/etc/httpd/conf.d#mv ssl.conf ssl.conf.jic
root@phillw:/etc/httpd/conf.d#apachectl start
root@phillw:/etc/httpd/conf.d#systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2018-07-03 23:36:23 CEST; 18s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 22362 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 2965 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Main PID: 22709 (httpd)
Status: “Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec”
Tasks: 7
CGroup: /system.slice/httpd.service
├─22709 /usr/sbin/httpd -DFOREGROUND
├─22710 /usr/sbin/httpd -DFOREGROUND
├─22711 /usr/sbin/httpd -DFOREGROUND
├─22712 /usr/sbin/httpd -DFOREGROUND
├─22713 /usr/sbin/httpd -DFOREGROUND
├─22714 /usr/sbin/httpd -DFOREGROUND
└─22718 /usr/sbin/httpd -DFOREGROUND

Jul 03 23:36:23 phillw.net systemd[1]: Starting The Apache HTTP Server…
Jul 03 23:36:23 phillw.net systemd[1]: Started The Apache HTTP Server.

schoen · July 3, 2018, 10:11pm

Did you maybe delete too much or too little when removing the _default_ virtual host?

phillw · July 3, 2018, 10:28pm

I took out one line

and now I have a site that cannot be contacted.

As it has several VMs running a re-install is not a viable option,

How do I remove the stuff that your system installer caused my server (since 2011) to suddenly not want to talk with the world? If you need admin access to investigate, that can be granted after a chat on freenode channel #phillw-social

schoen · July 3, 2018, 10:30pm

Which line was that?

phillw · July 3, 2018, 10:35pm

the one you reccomended

schoen · July 3, 2018, 10:37pm

Oh, sorry, you need to remove the entire stanza rather than just its opening line. The virtual host is defined by a set of lines that start with

<VirtualHost _default_:443>

and continue until the closing

</VirtualHost>

All of the other lines should also be deleted or commented out.

phillw · July 3, 2018, 10:42pm

/etc/httpd/conf#ls
httpd.conf.jic httpd.conf magic

I guess i got a bit annoyed in what needed to removed as my site is down.

schoen · July 3, 2018, 10:44pm

I don’t know which file that <VirtualHost _default_:443> was originally in or what else might have been part of that file.

phillw · July 3, 2018, 10:48pm

Unable to connect

Firefox can’t establish a connection to the server at phillw.net.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web

schoen · July 3, 2018, 10:51pm

I understand that the site is down, and I’d like to know more about what you changed or deleted in your Apache configuration files.

phillw · July 3, 2018, 11:15pm

Okies,

we can go back and forth for questions and answers or you could pop onto freenode IRC channel #phillw-social and we can have a live chat in PM and I can grant you sudo access to the server.

schoen · July 3, 2018, 11:22pm

I don’t think anyone from Let’s Encrypt or the Forum is willing to log in to other people’s servers for debugging. However, I’ll come chat with you briefly on IRC.

system · August 2, 2018, 11:35pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.