Jump to content

Localhost Stopped Working?!


Recommended Posts

Not sure if this is the right place for this but...

I was building my site on localhost and its been working for the longest time.

I got to work on it the other day and now I get the "Error 404 The requested resource is not found"

I am using XAMPP and it appears Apache won't start up.

Any ideas why this stopped working and how to fix?

 

Thanks everyone!

Link to comment
https://forums.phpfreaks.com/topic/261948-localhost-stopped-working/
Share on other sites

Ok I found out how to see that.  Here is the last day's entries.  I would say this date is probably right around when I know it worked last.

 

[Thu Apr 19 18:34:07 2012] [warn] pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?

[Thu Apr 19 18:34:07 2012] [notice] Digest: generating secret for digest authentication ...

[Thu Apr 19 18:34:07 2012] [notice] Digest: done

[Thu Apr 19 18:34:09 2012] [notice] Apache/2.2.17 (Win32) mod_ssl/2.2.17 OpenSSL/0.9.8o PHP/5.3.4 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations

[Thu Apr 19 18:34:09 2012] [notice] Server built: Oct 18 2010 01:58:12

[Thu Apr 19 18:34:09 2012] [notice] Parent: Created child process 3500

Terminating on signal SIGTERM(15)

] Digest: generating secret for digest authentication ...

[Thu Apr 19 18:34:10 2012] [notice] Digest: done

[Thu Apr 19 18:34:10 2012] [notice] Child 3500: Child process is running

[Thu Apr 19 18:34:10 2012] [notice] Child 3500: Acquired the start mutex.

[Thu Apr 19 18:34:10 2012] [notice] Child 3500: Starting 150 worker threads.

[Thu Apr 19 18:34:10 2012] [notice] Child 3500: Starting thread to listen on port 443.

[Thu Apr 19 18:34:10 2012] [notice] Child 3500: Starting thread to listen on port 80.

Terminating on signal SIGTERM(15)

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.