Very strange. But more importantly -- dangerous for the project.
My WAMP server was down. Wamp = down means I can't develop Wedge locally anymore. And I'm definitely not excited about developing and testing it remotely, really...
I did absolutely nothing-- well, I tuned on FIP Radio (online) and listened to the Portico Quartet concert, then went for a cigarette, and when I came back, the radio was down.[1]
I couldn't log into my local website after that -- or any site for that matter. One of my two httpd.exe process was using 50% of my CPU time (i.e. one core at 100%), and it keeps opening new handles. After about 2.040.000 handles, CPU use goes back to 0%, handle count doesn't increase anymore, and the Net is down for me (anything on port 80 I'd say), including non-local stuff. Once I kill the httpd.exe task, I get my Net back.
Sounds similar to what this guy had:
http://www.apachefriends.org/f/viewtopic.php?f=16&t=41141&view=previous
Upon which he was told to switch to Linux. Great... To solve what, an Apache (=from Linux world) memory leak?
Now this is very annoying, because it started without warning, and it stopped without warning either -- all in all the problem lasted for a couple of years.
Anyone got an idea about this?
http://www.wampserver.com/
Apache 2.2.11
PHP 5.3.0
MySQL 5.1.36
Changed absolutely nothing to the default setup. Worked perfectly until an hour ago. And yes, I rebooted my machine just to be sure... :-/
The only thing I did when it 'came back', was that I only started the Apache module, not the rest. I doubt this is related, because I'd left my server offline for several minutes, and I tried to restart all services at once anyway, and I'm not getting the error again...
Oh, how I hate Apache.
My WAMP server was down. Wamp = down means I can't develop Wedge locally anymore. And I'm definitely not excited about developing and testing it remotely, really...
I did absolutely nothing-- well, I tuned on FIP Radio (online) and listened to the Portico Quartet concert, then went for a cigarette, and when I came back, the radio was down.[1]
I couldn't log into my local website after that -- or any site for that matter. One of my two httpd.exe process was using 50% of my CPU time (i.e. one core at 100%), and it keeps opening new handles. After about 2.040.000 handles, CPU use goes back to 0%, handle count doesn't increase anymore, and the Net is down for me (anything on port 80 I'd say), including non-local stuff. Once I kill the httpd.exe task, I get my Net back.
Sounds similar to what this guy had:
http://www.apachefriends.org/f/viewtopic.php?f=16&t=41141&view=previous
Upon which he was told to switch to Linux. Great... To solve what, an Apache (=from Linux world) memory leak?
Now this is very annoying, because it started without warning, and it stopped without warning either -- all in all the problem lasted for a couple of years.
Anyone got an idea about this?
http://www.wampserver.com/
Apache 2.2.11
PHP 5.3.0
MySQL 5.1.36
Changed absolutely nothing to the default setup. Worked perfectly until an hour ago. And yes, I rebooted my machine just to be sure... :-/
The only thing I did when it 'came back', was that I only started the Apache module, not the rest. I doubt this is related, because I'd left my server offline for several minutes, and I tried to restart all services at once anyway, and I'm not getting the error again...
Oh, how I hate Apache.
1. | And *of course* I was recording it because PQ is my favourite jazz band and they never released a live album and I was so thrilled by their concert last year that I wanted to have it in my archives... >_< Thanks to this problem, I'm missing the last few minutes of the concert. |