Parent: Received shutdown signal -- Shutting down the server

Question

Using wampserver and receiving this error:

Parent: Received shutdown signal -- Shutting down the server.

Google doesn't seem to have any solutions that work. Any ideas?

[Mon Jul 25 19:07:02 2011] [warn] NameVirtualHost *:80 has no VirtualHosts
[Mon Jul 25 19:07:02 2011] [notice] Child 5828: Child process is running
[Mon Jul 25 19:07:02 2011] [notice] Child 5828: Acquired the start mutex.
[Mon Jul 25 19:07:02 2011] [notice] Child 5828: Starting 64 worker threads.
[Mon Jul 25 19:07:02 2011] [notice] Child 5828: Starting thread to listen on port 80.
[Mon Jul 25 19:07:40 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Mon Jul 25 19:07:40 2011] [notice] Child 5828: Exit event signaled. Child process is ending.
[Mon Jul 25 19:07:41 2011] [notice] Child 5828: Released the start mutex
[Mon Jul 25 19:08:05 2011] [notice] Child 5828: All worker threads have exited.
[Mon Jul 25 19:08:05 2011] [notice] Child 5828: Child process is exiting
[Mon Jul 25 19:08:05 2011] [notice] Parent: Child process exited successfully.

tell me if you need more information as I don't know what information is relevant. — rgin, Jul 25 '11 at 11:40
More information required: why is this a problem? What were you doing when you got this error / informational message; and what do you want to achieve (cancel the shutdown?) — searlea, Jul 25 '11 at 12:07

score 2 · Answer 1 · answered Jul 07 '15 at 05:45

I got the same error. So, I quit the skype and run the wamp as administrator it works. After that I changed the skype listen port to 88. Now the wamp works fine.

Its the port conflict. So, either you may change the localhost port to 88 in httpd.config file.

score 2 · Answer 2 · edited Jun 10 '23 at 18:00

2

Look at the Apache error log.

This error almost always occurs when another user shuts down a multi-user server. The Apache error log will tell you what happened so we can help if there are further issues.

Edit

Try this- go to C:\WINDOWS\System32\drivers\etc and make sure you have the following in hosts file:

127.0.0.1 localhost

Restart WAMP, and see if anything has changed.

edited Jun 10 '23 at 18:00

Farhan Ibn Wahid

926
1
9
22

answered Jul 25 '11 at 12:12

element119

7,475
8
51
74

I've been staring at these logs all day. I'm adding what seems to be relevant coz these are what's added when I restart the server. – rgin Jul 25 '11 at 14:13

score 1 · Answer 3 · answered Jul 16 '18 at 08:52

This can also be caused by own stupidity, like in my case:

I've had a script on my server (Windows 2008 R2) that was configured to run every 5 minutes. It contained the following two lines:

net stop Apache2.4
net start Apache2.4

Strange enough this script was present for years and did never cause any remarkable effect for my websites. Only recently, Uptime Robot detected some downtimes.

To be honest, I don't know anymore why I had this script configured at all.

Solution:

To solve this, I simply deactivated the script in the Windows Task Scheduler.

score 0 · Answer 4 · answered May 18 '12 at 00:09

0

Have you been messing with your httpd.conf file? I was messing with mine, and changed the first "listen" bit to Listen 8080 and got rid of a the 303 error and am able to start apache. Now I have a 404 error...which is an improvement I guess.

answered May 18 '12 at 00:09

boulder_ruby

38,457
9
79
100

score 0 · Answer 5 · answered Jan 17 '16 at 14:17

0

I have both iis and wamp installed on my windows machine, and accidentally I have opened iis for port 80, which caused the error you have experienced. Either change the port that Wamp listens to, either the port the IIS listens to

answered Jan 17 '16 at 14:17

RomanY

376
2
9

Parent: Received shutdown signal -- Shutting down the server

5 Answers5