Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Diego Ante
5,251 PointsHelp with Xampp
I had Xampp installed and it was working perfectly and then I restarted my pc and suddenly it didn't anymore. Neither Apache nor MySQL would work, the Error is giving me is:
07:11:03 p.m. [Apache] Error: Apache shutdown unexpectedly.
07:11:03 p.m. [Apache] This may be due to a blocked port, missing dependencies,
07:11:03 p.m. [Apache] improper privileges, a crash, or a shutdown by another method.
07:11:03 p.m. [Apache] Check the "/xampp/apache/logs/error.log" file
07:11:03 p.m. [Apache] and the Windows Event Viewer for more clues
07:11:04 p.m. [mysql] Error: MySQL shutdown unexpectedly.
07:11:04 p.m. [mysql] This may be due to a blocked port, missing dependencies,
07:11:04 p.m. [mysql] improper privileges, a crash, or a shutdown by another method.
07:11:04 p.m. [mysql] Check the "/xampp/mysql/data/mysql_error.log" file
07:11:04 p.m. [mysql] and the Windows Event Viewer for more clues
I've looked for the error logs, but there's none in the folder requested.
Can anyone help me please!?
10 Answers
Randy Hoyt
Treehouse Guest TeacherDid you install XAMPP in C:\xampp? If so, there should be an error log in C:\xampp\mysql\apache\logs\ called error.log. Are you not seeing that?
Diego Ante
5,251 PointsActually I did, and the file isn't there... neither for Apache.
Diego Ante
5,251 PointsAt one point the error told me that probably skype would be using the ports, but I'm not sure how to fix it.... then the error changed back to the one I posted.
James Barnett
39,199 Points@Diego -
- Try re-running
setup_xampp.bat, located in the folder you installed xampp in - It's possible you have another program listening on port 80
- To check this, run this command
netstat -an | find /i "listening"and post the output here
- To check this, run this command
Randy Hoyt
Treehouse Guest Teacher@Diego - Yes, it sounds like a problem with the port. I found this thread that discusses how to get Skype and XAMPP running together: Skype interferes with XAMPP on port 80. It has some good tips for checking ports.
If you do run any of the terminal commands, please do post the output here. Also, let us know what version of Windows you are running and anything that might be unusual about your environment (like if you are running VMware or anything like that).
Diego Ante
5,251 PointsOk, first of all the error for MySQL finally appeared (Apache's one has not), Is a pretty long file, I'm not sure if I should paste it here or how can I attach it?
Now, after doing what James suggested this is the output:
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 0.0.0.0:17500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:18465 0.0.0.0:0 LISTENING
TCP 0.0.0.0:35729 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49162 0.0.0.0:0 LISTENING
TCP 0.0.0.0:51099 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2559 0.0.0.0:0 LISTENING
TCP 127.0.0.1:3939 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
TCP 127.0.0.1:10000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49212 0.0.0.0:0 LISTENING
TCP 192.168.11.106:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:18465 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49161 [::]:0 LISTENING
TCP [::]:49162 [::]:0 LISTENING
Diego Ante
5,251 PointsI'm using windows 7 (I did uncheck skype's option and it didn't work)
After using telnet localhost 80 the output was:
Connecting To localhost...Could not open connection to the host, on port 80: Con
nect failed
But still it doesn't work, so I used
netstat -o -n -a | findstr 0.0.0.0:80
But this doesn't gives me any output.
Diego Ante
5,251 PointsWell finally I solved it. What I think it happened is that I recently installed "Trillian" for IM, and it allows me to connect my skype account aswell, so inside of it it has also the option enabled to use port 80 and 443, what you have to do (in case someone has the same problem) is to go into manage accounts, then open skype settings and finally go into the miscellaneous tab and there uncheck Use port 80 and 443 as alternatives for incoming connections as you did in skype itself.
But this still didn't work for me, so I uninstalled Xampp and reinstalled it and now it works correctly.
Thank you for your help!
Randy Hoyt
Treehouse Guest TeacherGlad you got it working!
Maxime Braire
5,954 PointsHello there,
I'm using Windows 8 Pro and I had a similar issue. Port 80 was already used by Microsoft-IIS server which is activated by default in Windows 8 Pro. To solve this issue, I unchecked Internet Information Service (IIS) in Windows functionalities.
I found the solution in these threads from french forums: http://www.siteduzero.com/forum/sujet/wamp-amp-windows-8-85935 http://www.tadpu.com/systeme/configuration-et-outils-divers/telecharger_comment-faire-fonctionner-wamp-server-sous-windows8/
For non french speakers, you may read this thread which discusses the same issue with WAMP: http://wpfirstaid.com/2012/11/wamp-server-microsoft-iis-windows-8-pro/
Larry Wright
7,325 PointsHello Maxine, I had the same problems, first of all used the forums at Xampp and they were worthless. I took your advice and took care of my problem. Thanks for knowing!