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.
Related
OS: Windows 10
MAMP: 4.1.1
After installation, every time I run the program, Apache light goes green for a second and then turns off automatically. MySQL runs fine though.
The log file located at C:\MAMP\logs\apache_error.log contains these lines.
[Fri Jan 17 18:03:42 2020] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Jan 17 18:03:43 2020] [warn] pid file C:/MAMP/bin/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Jan 17 18:03:43 2020] [notice] Digest: generating secret for digest authentication ...
[Fri Jan 17 18:03:43 2020] [notice] Digest: done
I find a lot of people online encountered the same situation as mine. But I cannot find out the solution. So I come here to find the potential solution.
P.S. I don't have the common Port 80 confliction problem. So I'm sure my problem is not related to it.
Navigate to C:\MAMP\conf\apache\extra.
Edit the httpd-ssl.conf and comment the following line:
...
SSLSessionCache shmcb:/some/example/path/ssl_scache(512000)
...
To:
...
# SSLSessionCache shmcb:/some/example/path/ssl_scache(512000)
...
Also, check out https://cwiki.apache.org/confluence/display/HTTPD/SSLSessionCache for more info. Hope this helps.
There is an issue where I have a cpanel server with cachewall (Xvarnish used to be called) and mod_pagspeed installed.
Cachewall/Xvarnish has https support enabled.
The issue is that even though the header of the website is showing that both Cachewall and modpagespeed is running, I'm getting flooded with this in my apache error log:
[Mon Jul 03 20:45:49.060050 2017] [pagespeed:error] [pid 31223:tid 112490802050816] [mod_pagespeed 1.11.33.4-0 #31223] Serf status 120171(APR does not understand this error code) polling for 1 threaded fetches for 0.05 seconds
[Mon Jul 03 20:45:49.060071 2017] [pagespeed:error] [pid 31223:tid 112490802050816] [mod_pagespeed 1.11.33.4-0 #31223] Serf status 120171(APR does not understand this error code) polling for 1 threaded fetches for 0.05 seconds
[Mon Jul 03 20:45:49.910183 2017] [pagespeed:warn] [pid 31225:tid 112490799363840] [mod_pagespeed 1.11.33.4-0 #31225] Fetch timed out: https://www.example.com/wp-includes/js/jquery/jquery.js?ver=1.12.4 (connecting to:139.xx.xx.xx:82) (1) waiting for 50 ms
Not sure whats going on here.
I think you have to understand the cache flow when using both varnish and page_speed.
Please check the link bellow for details:
https://www.sonassi.com/help/troubleshooting/understanding-cache-flow-when-using-pagespeed-and-varnish
Clear all page_speed cache and varnish cache, then restart both varnish and apache.
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 installed mod_security 2.8.0 on my Apache 2.4 installation. I copied the yajl.dll into my bin folder, the .so file into my modules, added the configuration as the readme suggested, but when I start Apache, it fails.
But it only fails if I specify rules (I tried a lot of different ones, one at a time). Every time there is a rule, Apache fails to start.
If I go with only
SecRuleEngine On
SecDefaultAction "deny,phase:2,status:403"
Then it works fine. The error log shows only:
[Mon May 19 11:24:10.010299 2014] [:notice] [pid 2820:tid 496] ModSecurity for Apache/2.8.0 (http://www.modsecurity.org/) configured.
[Mon May 19 11:24:10.010299 2014] [:notice] [pid 2820:tid 496] ModSecurity: APR compiled version="1.5.0"; loaded version="1.5.0"
[Mon May 19 11:24:10.010299 2014] [:notice] [pid 2820:tid 496] ModSecurity: PCRE compiled version="8.34 "; loaded version="8.34 2013-12-15"
[Mon May 19 11:24:10.010299 2014] [:notice] [pid 2820:tid 496] ModSecurity: LUA compiled version="Lua 5.1"
[Mon May 19 11:24:10.010299 2014] [:notice] [pid 2820:tid 496] ModSecurity: LIBXML compiled version="2.9.1"
I.e. no errors. If I add a rule that is misconfigured (missing ID) it will log it here, but as you can see it doesn't - but Apache won't start.
System is Windows Server 2008 R2 64 bit.
I don't know if this helps, but I had this problem just minutes ago, and diagnosed that the mod_security installation changed my server root in the httpd_conf to "c:/apache24/" when there was no such file on my system, I changed it back to "c:/xampp/apache/" and it started up just fine again, no probs.
localhost not work and IIS server stop
apache error log look like this
[Thu Jan 05 14:55:20 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Thu Jan 05 14:55:20 2012] [notice] Server built: Sep 10 2011 11:34:11
[Thu Jan 05 14:55:20 2012] [notice] Parent: Created child process 3152
[Thu Jan 05 14:55:20 2012] [notice] Child 3152: Child process is running
[Thu Jan 05 14:55:20 2012] [crit] (OS 10022)An invalid argument was supplied. : Child 3152: setup_inherited_listeners(), WSASocket failed to open the inherited socket.
[Thu Jan 05 14:55:21 2012] [crit] Parent: child process exited with status 3 -- Aborting.
[Thu Jan 05 14:55:31 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Thu Jan 05 14:55:31 2012] [notice] Server built: Sep 10 2011 11:34:11
[Thu Jan 05 14:55:31 2012] [notice] Parent: Created child process 3988
[Thu Jan 05 14:55:31 2012] [notice] Child 3988: Child process is running
[Thu Jan 05 14:55:31 2012] [crit] (OS 10022)An invalid argument was supplied. : Child 3988: setup_inherited_listeners(), WSASocket failed to open the inherited socket.
[Thu Jan 05 14:55:31 2012] [crit] Parent: child process exited with status 3 -- Aborting.
anyone know reason for this plz help for me
If you guys have still have problems with this after trying everything (like me) and the wampserver icon remains orange or some internal exception is thrown while trying to put it online, try to do following steps:
Left click the wampserver icon
Navigate to Apache->Service
Press "Remove service" and then navigate there again and press "Install service"
Restart wampserver, start/restart all services and try to put it online again
you can check out if the port 80 is open for wampserver by clicking "test port 80" inside the Apache->Service submenu
There is apparently some kind of bug or misunderstanding and wampserver didn't knew where the apache is installed
It appears to be a common issue on Win XP SP2.
"
The very simple solution is to uncheck the “Enable LMHOSTS Lookup” box in the TCP/IP protocol setup (under WINS setting). Here are the steps to do this:
Open “Control Panel” then “Network Connections.”
Right-click on “Local Area Connection” and select “Properties.”
Double-click on the “Internet Protocol (TCP/IP)” line to open the “Properties.”
On the “General” tab, click the “Advanced” button.
Select the “WINS” tab and uncheck the “Enable LMHOSTS Lookup” box.”
"
http://www.jennyconnors.com/computers/installing-apache2-and-the-wsasocket-failed-to-open-the-inherited-socket-error
I was having the same problem. It usually means that either your
C:\WINDOWS\system32\drivers\etc\hosts
C:\WINDOWS\system32\drivers\etc\lmhosts.sam
file has been changed by a program or virus.
Under Win XP SP2 or SP3, "hosts" should contain 1 entry:
127.0.0.1 localhost
lmhosts.sam should have a load of commented out statements using #.
Viruses and malware will try to put their own entries in there, so check every IP address or hostname listed. 127.0.0.1 is the local host machine, so thats cool.
i think that the problem is Related to httpd.conf file open it & change Port 80 to ex: 8081 because it could be used by another programs then try to Restart services and type http:\localhost:8081 you will find it runs