WampServer

Hello guys !

I'm having an issue that is quite urgent and i have no clue what to do.
I'm using wamp for quite a long time even if i'm not an expert everything has always been running easy and smooth.
Today when i started up wamp and went to localhost i noticed that my main website wont load and is sending a ERROR 500. I've checked the htaccess ,etc ,etc. couldn't find anything so it tried to connect to Phpmyadmin and to my suprise it cannot acces it. The page is blank and it won't load so in the end i'm thinking the error 500 might come from a database issue.

So i have 2 questions :

The most urgent one , how can i backup my database without phpmyadmin ? I'm sacred of uninstalling the soft since i have no backup of this database and cannot loose it.

And obviously the second question is how to fix this problem.

I've already checked a couple forum on this issue and people were asking to check for a couple of thing so i'll list the answers here directly so that you might ans wer quicker :

Apache => service > port 80 it say :
Your port 80 is used by apache 2.2.222 and php 5.4..3

In the appache error log i get :

[error] [client 127.0.0.1] PHP Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 28672 bytes)

This is for actually multiple different php files , it says " error on line xxx " but there are not error on those lines.

This is is also WRONG since my memory_limit in php.ini is actually 128 and was previously 1024.

_____


In mysl log i got :


130430 3:02:05 [Note] Plugin 'FEDERATED' is disabled.
130430 3:02:05 InnoDB: The InnoDB memory heap is disabled
130430 3:02:05 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130430 3:02:05 InnoDB: Compressed tables use zlib 1.2.3
130430 3:02:05 InnoDB: Initializing buffer pool, size = 128.0M
130430 3:02:05 InnoDB: Completed initialization of buffer pool
130430 3:02:05 InnoDB: highest supported file format is Barracuda.
130430 3:02:05 InnoDB: Waiting for the background threads to start
130430 3:02:06 InnoDB: 1.1.8 started; log sequence number 938965737
130430 3:02:06 [Note] Server hostname (bind-address): '(null)'; port: 3306
130430 3:02:06 [Note] - '(null)' resolves to '::';
130430 3:02:06 [Note] - '(null)' resolves to '0.0.0.0';
130430 3:02:06 [Note] Server socket created on IP: '0.0.0.0'.
130430 3:02:06 [Note] Event Scheduler: Loaded 0 events
130430 3:02:06 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log' socket: '' port: 3306 MySQL Community Server (GPL)
130430 3:20:08 [Note] wampmysqld: Normal shutdown

130430 3:20:08 [Note] Event Scheduler: Purging the queue. 0 events
130430 3:20:08 InnoDB: Starting shutdown...
130430 3:20:09 InnoDB: Shutdown completed; log sequence number 938965737
130430 3:20:09 [Note] wampmysqld: Shutdown complete

130430 3:20:09 [Note] Plugin 'FEDERATED' is disabled.
130430 3:20:09 InnoDB: The InnoDB memory heap is disabled
130430 3:20:09 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130430 3:20:09 InnoDB: Compressed tables use zlib 1.2.3
130430 3:20:09 InnoDB: Initializing buffer pool, size = 128.0M
130430 3:20:09 InnoDB: Completed initialization of buffer pool
130430 3:20:09 InnoDB: highest supported file format is Barracuda.
130430 3:20:09 InnoDB: Waiting for the background threads to start
130430 3:20:10 InnoDB: 1.1.8 started; log sequence number 938965737
130430 3:20:10 [Note] Server hostname (bind-address): '(null)'; port: 3306
130430 3:20:10 [Note] - '(null)' resolves to '::';
130430 3:20:10 [Note] - '(null)' resolves to '0.0.0.0';
130430 3:20:10 [Note] Server socket created on IP: '0.0.0.0'.
130430 3:20:10 [Note] Event Scheduler: Loaded 0 events
130430 3:20:10 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log' socket: '' port: 3306 MySQL Community Server (GPL)

and there are actually no Php error log created for some reason.


I'm not quite sure what else to add expect that i hope you can help

I've " fixed " it or it fixed itself.

For people that might find this topic in the futur , i've found that reboot the comptuer / software was doing nothing but going cick on " online mode " then " offline mode " fixed it for some rreason.