I built apache-httpd-2.4.20 from the source and installed properly.
I have created apphttpd.service under /etc/systemd/system.
Script
[Unit]
Description=Apache Web Server
After=network.target remote-fs.target nss-lookup.target
[Service]
Type=simple
TimeoutStartSec=600
PIDFile=/usr/local/apache/logs/httpd.pid
ExecStart=/usr/local/apache/bin/apachectl -k start
ExecStop=/usr/local/apache/bin/apachectl -k stop
ExecReload=/usr/local/apache/bin/apachectl -k graceful
Restart=on-abort
PrivateTmp=true
LimitNOFILE=infinity
#User=root
#Group=root
[Install]
WantedBy=multi-user.target
when i perform systemctl start apphttpd, got message started Apache Web Server,
Status Log
**systemctl status -l apphttpd**
apphttpd.service - Apache Web Server
Loaded: loaded (/etc/systemd/system/apphttpd.service; enabled)
Active: inactive (dead) since Wed 2018-06-13 21:45:20 SGT; 14min ago
Process: 112124 ExecStop=/usr/local/apache/bin/apachectl -k stop (code=exited, status=0/SUCCESS)
Process: 112118 ExecStart=/usr/local/apache/bin/apachectl -k start (code=exited, status=0/SUCCESS)
Main PID: 112118 (code=exited, status=0/SUCCESS)
Jun 13 21:45:20 <host> systemd[1]: Started Apache Web Server.
but the services are not started actually.
error_log information:
[Wed Jun 13 21:45:20.873135 2018] [core:debug] [pid 112123:tid 139709837686656] log.c(1546): AH02639: Using SO_REUSEPORT: yes (1)
[Wed Jun 13 21:45:20.873145 2018] [mpm_worker:debug] [pid 112123:tid 139709837686656] worker.c(1874): AH00294: Accept mutex: sysvsem (default: sysvsem)
[Wed Jun 13 21:45:20.907675 2018] [core:info] [pid 112123:tid 139709837686656] AH00096: removed PID file /usr/local/apache/logs/httpd.pid (pid=112123)
[Wed Jun 13 21:45:20.907684 2018] [mpm_worker:notice] [pid 112123:tid 139709837686656] AH00295: caught SIGTERM, shutting down
But if I start the service from /usr/local/apache/bin/apachectl -k start, the services are started properly and able to get the response.
[Wed Jun 13 21:46:25.146698 2018] [core:debug] [pid 112229:tid 140320724187008] log.c(1546): AH02639: Using SO_REUSEPORT: yes (1)
[Wed Jun 13 21:46:25.146711 2018] [mpm_worker:debug] [pid 112229:tid 140320724187008] worker.c(1874): AH00294: Accept mutex: sysvsem (default: sysvsem)
Is there any issue with my apphttpd.service script, any access issue ? Thanks for you suggestions and help in advance.
Related
Not able to start apache. Giving the below error.
Could some one please help me on this?
Error message:
ip-10-128-9-27 httpd-scl-wrapper: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf: Cannot load modules/mod_ssl.so into server: /lib64/libcrypto.so.10: version `OPENSSL_1.0.2' not found (required by /opt/rh/httpd24/root/etc/httpd/modules/mod_ssl.so)
Below is the detailed error message.
[root#ip-10-128-9-27 centos]# systemctl status httpd24-httpd.service
● httpd24-httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-12-07 12:34:05 UTC; 12s ago
Process: 29020 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
Process: 29018 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 29018 (code=exited, status=1/FAILURE)
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Starting The Apache HTTP Server...
Dec 07 12:34:05 ip-10-128-9-27 httpd-scl-wrapper[29018]: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf...
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Dec 07 12:34:05 ip-10-128-9-27 httpd-scl-wrapper[29020]: httpd: Syntax error on line 56 of /opt/rh/httpd24/root/etc/httpd/conf/httpd.conf: Syntax error on line 1 of /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-ssl.conf...
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Failed to start The Apache HTTP Server.
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: Unit httpd24-httpd.service entered failed state.
Dec 07 12:34:05 ip-10-128-9-27 systemd[1]: httpd24-httpd.service failed.
I ran a yum update after which HTTP Apache server fails to start up on my Centos 7 VM.
The apache details - Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
Kernel version - 3.10.0-327.10.1.el7.x86_64
Here is what the systemctl shows. I'm not able to figure out what is broken after the update.
[root#localhost log]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-02-26 16:32:37 NZDT; 4min 19s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 3654 ExecStopPost=/usr/bin/kdestroy -A (code=exited, status=0/SUCCESS)
Process: 3651 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 3649 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Process: 3574 ExecStartPre=/usr/libexec/ipa/ipa-httpd-kdcproxy (code=exited, status=0/SUCCESS)
Main PID: 3649 (code=exited, status=1/FAILURE)
Feb 26 16:32:37 localhost.localdomain ipa-httpd-kdcproxy[3574]: ipa : WARNING Disabling KDC proxy
Feb 26 16:32:37 localhost.localdomain httpd[3649]: [Fri Feb 26 16:32:37.213684 2016] [so:warn] [pid 3649] AH01574: module rewrite_module is already loaded, skipping
Feb 26 16:32:37 localhost.localdomain httpd[3649]: [Fri Feb 26 16:32:37.217181 2016] [so:warn] [pid 3649] AH01574: module ssl_module is already loaded, skipping
Feb 26 16:32:37 localhost.localdomain httpd[3649]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directi... this message
Feb 26 16:32:37 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 26 16:32:37 localhost.localdomain kill[3651]: kill: cannot find process ""
Feb 26 16:32:37 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1
Feb 26 16:32:37 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
Feb 26 16:32:37 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.
Feb 26 16:32:37 localhost.localdomain systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Could I please request help to get some pointers to dig further or anyone who has seen this before & knows how to fix please?
it was happened to me when i install/uninstall free-ipa, because of which nss.conf has been created inside /etc/httpd/conf.d/nss.conf, you can give a try by just moving this file to another directory as i did, now httpd service is working like a charm.
Can you please setup the correct hostname for your server and check " journalctl -xn " command out while restarting httpd services on yoru server, You will get exact root cause of your httpd issues with journalctl -xn command.
My application is running with an Apache 2 server using mod_wsgi, Flask, and Python 2.7. Oddly enough, the application crashes when the page refreshes. For me, this happens exactly on every other refresh. You can see it here. Furthermore, in Chrome, if I open the web inspector tool, the program does not crash.
In the logs, I see:
[Tue Apr 14 13:45:29.137444 2015] [wsgi:error] [pid 32713] [client 146.203.54.32:58816] Truncated or oversized response headers received from daemon process 'localhost:80': /etc/g2e/htdocs/g2e
[Tue Apr 14 13:45:29.671493 2015] [core:notice] [pid 28845] AH00052: child pid 640 exit signal Segmentation fault (11)
[Tue Apr 14 13:45:29.671520 2015] [wsgi:info] [pid 28845] mod_wsgi (pid=640): Process 'localhost:80' has died, deregister and restart it.
[Tue Apr 14 13:45:29.671524 2015] [wsgi:info] [pid 28845] mod_wsgi (pid=640): Process 'localhost:80' terminated by signal 11
[Tue Apr 14 13:45:29.671527 2015] [wsgi:info] [pid 28845] mod_wsgi (pid=640): Process 'localhost:80' has been deregistered and will no longer be monitored.
...
FWIW, I am using
Linux 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
Any help is appreciated.
I may have a tweak. I had this problem but now it's working somehow.
I tried to run mod_wsgi as a daemon. My application didn't work and I had this error message in the logs.
however running mod_wsgi as non-daemon worked, for instance
python manage.py runmodwsgi --reload-on-changes # for Django
So I once again launched it then killed it.
my app is still running :)
(mod_wsgi 4.4.[1-13], apache2, python 2.7, Django 1.7, Debian8 fresh install, with or without virtualenv)
I'm using Apache2.2 on WIndows 7. I tried to load mod_wsgi.so to Apache2.2 by adding the following line to httpd.conf:
LoadModule wsgi_module modules/mod_wsgi.so
In httpd.conf, there's some lines using directives from mod_wsgi.so (maybe depend on this so, I'm not sure) like this line:
WSGISocketPrefix D:\tool\apache2.2\conf
This line made me stuck by the following error which I get from Apache2.2 log:
[Thu Jul 25 21:44:25 2013] [notice] Parent: Received restart signal -- Restarting the server.
[Thu Jul 25 21:44:25 2013] [notice] Child 6436: Exit event signaled. Child process is ending.
[Thu Jul 25 21:44:25 2013] [warn] module wsgi_module is already loaded, skipping
Syntax error on line 20 of D:/work/tool/apache2.2/conf/graphite.conf:
Invalid command 'WSGISocketPrefix', perhaps misspelled or defined by a module not included in the
server configuration
[Thu Jul 25 21:44:25 2013] [warn] (OS 995)The I/O operation has been aborted because of either a
thread exit or an application request. : winnt_accept: Asynchronous AcceptEx failed.
[Thu Jul 25 21:44:26 2013] [notice] Child 6436: Released the start mutex
[Thu Jul 25 21:44:27 2013] [notice] Child 6436: All worker threads have exited.
[Thu Jul 25 21:44:27 2013] [notice] Child 6436: Child process is exiting
Please help me!!
The WSGISocketPrefix isn't used on Windows and you should not be setting it. It is only relevant to mod_wsgi daemon mode which is only supported on UNIX systems.
This is first problem like that on my PC. Honestly saying I tried all solutions from the first pages of google and no one did work. I was able to start the server without any problem one month ago but today I'm starting it and it automatically stops. I tried to change port from 80 to 8080, 1337, 9999 and no one did work so I don't think it's a port problem(I've also tried to change the port in SSL config of apache) and few other solutions shown on few pages but I cant! It still stops, I don't know if a satan controlls the ports or what. Please help me without posting links because I tried them all. I don't really know if it's a good problem for stackoverflow but it seems to be really annoying so I've decided to post it here. That would be nice to see any help. I don't care if you don't like the problem and give me the magic downvote, all I need is the solution.
[Thu Aug 08 16:42:39.843750 2013] [mpm_winnt:notice] [pid 3324:tid 188] AH00455: Apache/2.4.3 (Win32) OpenSSL/1.0.1c PHP/5.4.7 configured -- resuming normal operations
[Thu Aug 08 16:42:39.843750 2013] [mpm_winnt:notice] [pid 3324:tid 188] AH00456: Server built: Aug 18 2012 12:41:37
[Thu Aug 08 16:42:39.843750 2013] [core:notice] [pid 3324:tid 188] AH00094: Command line: 'd:\\xampp\\apache\\bin\\httpd.exe -d D:/xampp/apache'
[Thu Aug 08 16:42:39.859375 2013] [mpm_winnt:notice] [pid 3324:tid 188] AH00418: Parent: Created child process 3472
[Thu Aug 08 16:42:41.140625 2013] [mpm_winnt:crit] [pid 3472:tid 1884] (OS 10022)An invalid argument was supplied. : AH00405: Child: WSASocket failed to open the inherited socket
[Thu Aug 08 16:42:41.140625 2013] [mpm_winnt:crit] [pid 3324:tid 188] AH00427: Parent: child process exited with status 3 -- Aborting.
i was having the same issue however after i restart the computer it went ok...
that happens because 'system' is using port 80...
try to:
Close XAMPP
Open "SERVICES.MSC"
Stop "Web Deployment Agent Service"
In my case this was apparently caused by Winsock2 corruption. In case anyone else experiences this issue, try the Fix It link at the bottom of this page from Microsoft:
http://support.microsoft.com/kb/811259/en
(as recommended here https://community.apachefriends.org/f/viewtopic.php?f=16&t=49824)
That solved it for me; changing the port and other things mentioned here did not.