I've installed WAMP successfully and it works as expected until I've tried to use it with a Dropbox folder, having followed a tutorial.
Owing to that challenge, I've uninstalled, deleted all the files, and have re-installed WAMP after a system restore.
I can access localhost, but not localhost/phpmyadmin; I keep getting a Forbidden error (403) with the following message: you do not have permission to view this directory.
I literally spent all afternoon yesterday and all morning reading every single Google result I could for solutions and I still can't fix it.
I've already tried common solutions such as modifying the configuration files to no avail.
Below is the content of my Apache error log:
[Tue Jan 24 15:53:39 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Tue Jan 24 15:53:39 2012] [notice] Server built: Sep 10 2011 11:34:11
[Tue Jan 24 15:53:39 2012] [notice] Parent: Created child process 4992
[Tue Jan 24 15:53:40 2012] [notice] Child 4992: Child process is running
[Tue Jan 24 15:53:40 2012] [notice] Child 4992: Acquired the start mutex.
[Tue Jan 24 15:53:40 2012] [notice] Child 4992: Starting 64 worker threads.
[Tue Jan 24 15:53:40 2012] [notice] Child 4992: Starting thread to listen on port 80.
[Tue Jan 24 15:53:40 2012] [notice] Child 4992: Starting thread to listen on port 80.
[Tue Jan 24 15:53:50 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Tue Jan 24 15:53:50 2012] [notice] Child 4992: Exit event signaled. Child process is ending.
[Tue Jan 24 15:53:51 2012] [notice] Child 4992: Released the start mutex
[Tue Jan 24 15:53:52 2012] [notice] Child 4992: All worker threads have exited.
[Tue Jan 24 15:53:52 2012] [notice] Child 4992: Child process is exiting
[Tue Jan 24 15:53:52 2012] [notice] Parent: Child process exited successfully.
[Tue Jan 24 15:53:53 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Tue Jan 24 15:53:53 2012] [notice] Server built: Sep 10 2011 11:34:11
[Tue Jan 24 15:53:53 2012] [notice] Parent: Created child process 4576
[Tue Jan 24 15:53:53 2012] [notice] Child 4576: Child process is running
[Tue Jan 24 15:53:53 2012] [notice] Child 4576: Acquired the start mutex.
[Tue Jan 24 15:53:53 2012] [notice] Child 4576: Starting 64 worker threads.
[Tue Jan 24 15:53:53 2012] [notice] Child 4576: Starting thread to listen on port 80.
[Tue Jan 24 15:53:53 2012] [notice] Child 4576: Starting thread to listen on port 80.
[Tue Jan 24 15:54:01 2012] [error] [client ::1] client denied by server configuration: C:/WAMP/apps/phpmyadmin3.4.5/, referer: http://localhost/
There was no PHP log.
Following, is the content of the MySQL error log:
120124 15:53:38 [Note] Plugin 'FEDERATED' is disabled.
120124 15:53:38 InnoDB: The InnoDB memory heap is disabled
120124 15:53:38 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120124 15:53:38 InnoDB: Compressed tables use zlib 1.2.3
120124 15:53:38 InnoDB: Initializing buffer pool, size = 128.0M
120124 15:53:38 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
120124 15:53:38 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
120124 15:53:39 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120124 15:53:39 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
120124 15:53:41 InnoDB: Waiting for the background threads to start
120124 15:53:42 InnoDB: 1.1.8 started; log sequence number 0
120124 15:53:43 [Note] Event Scheduler: Loaded 0 events
120124 15:53:43 [Note] wampmysqld: ready for connections.
Version: '5.5.16-log' socket: '' port: 3306 MySQL Community Server (GPL)
Apparently your server is configured to block your IPv6 loopback address:
[Tue Jan 24 15:54:01 2012] [error] [client ::1] client denied by server configuration: C:/WAMP/apps/phpmyadmin3.4.5/, referer: http://localhost/
Try allowing it or if that fails try disabling IPv6 on your network interface.
Related
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.
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.
I'm getting this error when trying to restart Apache after installing litespeed on my dedicated server:
Apache restarted, but pid file does not match process list pids.
If apache restart reported success but it failed soon after,
it may be caused by oddities with mod_ssl.
You should run /usr/local/cpanel/scripts/ssl_crt_status as part of your
troubleshooting process. Pass it --help for more details.
Also be sure to examine apache's various log files.
Apache Restart Output:
Log:
2013-02-09 20:54:17.062 [NOTICE] [Child: 15131] Shut down successfully!
2013-02-09 20:54:17.066 [NOTICE] [AutoRestarter] cleanup children
processes and unix sockets of process with pid=15132 !
2013-02-09 20:54:17.070 [NOTICE] [AutoRestarter] child process with
pid=15132 exited with status=0!
2013-02-09 20:54:17.070 [NOTICE] [AutoRestarter] cleanup children processes
and unix sockets of process with pid=15131 !
2013-02-09 20:54:17.170 [NOTICE] [AutoRestarter] child process with
pid=15131 exited with status=0!
2013-02-09 20:54:17.170 [NOTICE] [PID:15129] Server Stopped!
2013-02-09 20:54:18.200 [NOTICE] [AutoUpdate] Checking for new releases..., pid=15272
2013-02-09 20:54:18.201 [NOTICE] Start to clean up cache directory, pid=15273
2013-02-09 20:54:18.518 [INFO] [AutoUpdate] No new update.
[Sat Feb 09 20:54:19 2013] [notice] suEXEC mechanism enabled
(wrapper: /usr/local/apache/bin/suexec)
[Sat Feb 09 20:54:19 2013] [notice] Apache/2.0.64 (Unix)
mod_ssl/2.0.64 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1
mod_bwlimited/1.4 FrontPage/5.0.2.2635 configured -- resuming normal operations
I don't have enough experience to workout what the issue is , but I'm trying to learn... any help would be appreciated..thanks
Specs:
CENTOS 6.3 x86_64
WHM 11.34
PHP Version 5.3.21
Litespeed 4.2.1
Server Version:Apache/2.0.64 (Unix) mod_ssl/2.0.64 OpenSSL/1.0.0-fips
mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
LiteSpeed is running (PID = 15263). Apache is running (PID = 15335).
suEXE enabled
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