Apache couldn't be started because port 8888 is in use by some other software
I am having an issue starting up MAMP, when I attemp it, I get this error message:
Apache couldn't be started because port 8888 is in use by some other software
I have been trying for the last 2 days.
I have tried changing ports, I have tried deleting the httpd.pid and MySQL.pid files and I have tried reinstalling MAMP all together with no luck.
As it is right now I have no access to my website, I am trying to get on my myphp.admin to move my wordpress database to a new host (was using a local host)
If anyone knows how I can fix my issue with MAMP or how I could go about moving my database without access to myphp.admin (if that's even possible) that would be fantastic, I am running out of options here.
mysql database wordpress hosts mamp
migrated from serverfault.com Feb 9 '15 at 8:06
This question came from our site for system and network administrators.
add a comment |
I am having an issue starting up MAMP, when I attemp it, I get this error message:
Apache couldn't be started because port 8888 is in use by some other software
I have been trying for the last 2 days.
I have tried changing ports, I have tried deleting the httpd.pid and MySQL.pid files and I have tried reinstalling MAMP all together with no luck.
As it is right now I have no access to my website, I am trying to get on my myphp.admin to move my wordpress database to a new host (was using a local host)
If anyone knows how I can fix my issue with MAMP or how I could go about moving my database without access to myphp.admin (if that's even possible) that would be fantastic, I am running out of options here.
mysql database wordpress hosts mamp
migrated from serverfault.com Feb 9 '15 at 8:06
This question came from our site for system and network administrators.
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over thedb/andhtdocs/directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.
– JakeGould
Jan 24 at 2:23
add a comment |
I am having an issue starting up MAMP, when I attemp it, I get this error message:
Apache couldn't be started because port 8888 is in use by some other software
I have been trying for the last 2 days.
I have tried changing ports, I have tried deleting the httpd.pid and MySQL.pid files and I have tried reinstalling MAMP all together with no luck.
As it is right now I have no access to my website, I am trying to get on my myphp.admin to move my wordpress database to a new host (was using a local host)
If anyone knows how I can fix my issue with MAMP or how I could go about moving my database without access to myphp.admin (if that's even possible) that would be fantastic, I am running out of options here.
mysql database wordpress hosts mamp
I am having an issue starting up MAMP, when I attemp it, I get this error message:
Apache couldn't be started because port 8888 is in use by some other software
I have been trying for the last 2 days.
I have tried changing ports, I have tried deleting the httpd.pid and MySQL.pid files and I have tried reinstalling MAMP all together with no luck.
As it is right now I have no access to my website, I am trying to get on my myphp.admin to move my wordpress database to a new host (was using a local host)
If anyone knows how I can fix my issue with MAMP or how I could go about moving my database without access to myphp.admin (if that's even possible) that would be fantastic, I am running out of options here.
mysql database wordpress hosts mamp
mysql database wordpress hosts mamp
asked Feb 7 '15 at 5:56
Brianna
migrated from serverfault.com Feb 9 '15 at 8:06
This question came from our site for system and network administrators.
migrated from serverfault.com Feb 9 '15 at 8:06
This question came from our site for system and network administrators.
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over thedb/andhtdocs/directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.
– JakeGould
Jan 24 at 2:23
add a comment |
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over thedb/andhtdocs/directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.
– JakeGould
Jan 24 at 2:23
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over the
db/ and htdocs/ directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.– JakeGould
Jan 24 at 2:23
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over the
db/ and htdocs/ directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.– JakeGould
Jan 24 at 2:23
add a comment |
1 Answer
1
active
oldest
votes
I don't know anything about MAMP, but when I see that something else is using a port that I want to use, I can find out which process it is by doing netstat -napl | grep <portno> as root. This will list the process that is listening on that port. You can then use that information to figure out what is getting in the way.
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
|
show 1 more comment
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't know anything about MAMP, but when I see that something else is using a port that I want to use, I can find out which process it is by doing netstat -napl | grep <portno> as root. This will list the process that is listening on that port. You can then use that information to figure out what is getting in the way.
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
|
show 1 more comment
I don't know anything about MAMP, but when I see that something else is using a port that I want to use, I can find out which process it is by doing netstat -napl | grep <portno> as root. This will list the process that is listening on that port. You can then use that information to figure out what is getting in the way.
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
|
show 1 more comment
I don't know anything about MAMP, but when I see that something else is using a port that I want to use, I can find out which process it is by doing netstat -napl | grep <portno> as root. This will list the process that is listening on that port. You can then use that information to figure out what is getting in the way.
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
I don't know anything about MAMP, but when I see that something else is using a port that I want to use, I can find out which process it is by doing netstat -napl | grep <portno> as root. This will list the process that is listening on that port. You can then use that information to figure out what is getting in the way.
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
answered Feb 7 '15 at 6:04
Jon WatteJon Watte
3062414
3062414
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
|
show 1 more comment
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
Thank you for your response! How do I do a "netstat -Napl | grep" ??? I have no idea what that is. :/
– Brianna
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
First, you open a root shell on your server. Then you type the command line "netstat -napl | grep 8888" This will show you the name and process ID of the process that is using that port number.
– Jon Watte
Feb 7 '15 at 6:09
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
All it says when I enter that is:
– Brianna
Feb 7 '15 at 6:26
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
Unknown or uninstrumented protocol
– Brianna
Feb 7 '15 at 6:27
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
It sounds like your version of netstat has a different "-p" option than the one I'm used to. I presume MacOS X? The goal of the command is to find the actual program binding to port 8888, which prevents Apache from also binding to that port, because the error means "something else already uses port 8888." That "something else" might be another copy of Apache, for all I know -- you have to investigate that using system administration methods.
– Jon Watte
Feb 9 '15 at 0:00
|
show 1 more comment
Maybe Tomcat or Skype?
– kenorb
Mar 31 '15 at 22:50
This issue popped up occasionally on older versions of MAMP but is a non-issue (at least in my experience) on newer versions. The solution I had was simply to reboot my Mac. The next solution would be to rename the installed MAMP directory, reinstall the exact same version of MAMP and then manually move over the
db/andhtdocs/directory from the old install to the new one. Toss out the old MAMP directory, start MAMP again and you should be good.– JakeGould
Jan 24 at 2:23