I'm running the xampp on os x mavericks
Xampp doesn't start the ProFTPD server.
when i tried to start it always failed.
In application log it says
Starting ProFTPD...
Checking syntax of configuration file
/Applications/XAMPP/xamppfiles/proftpd/scripts/ctl.sh : proftpd started
Even after reinstalling the XAMPP ProFTPD doesn't start
This happens when another FTP is running on the same port.
I also faced same issue, then i resolve this by doing following steps.
1. Open the file /Applications/XAMPP/etc/proftpd.conf
2. Search for the port "21" and change it to some other port (e.g 28).
3. Open the file /Applications/XAMPP/xamppfiles/xampp
4. Search for the port "testport 21" and replace it to "testport 28".
5. Now go and run "sudo /Applications/XAMPP/xamppfiles/xampp start". (It should work now).
Hope this Helps :)
If you are Linux server, the the best and most quickly way is to do:
Step 1, Find the PID of ftp server (the second column), such as 21882, 22108....
ps aux | grep ftp
Step 2, kill these PID
sudo kill -9 21882
Related
I just find out that when I simply type 'localhost' in the url without anything more in the path, the browser displays a message from a local backend test project in Express that I've made days ago.
I'm trying to stop this process.
I was sure that to have started this server on port 3001 but when I try to kill it , it says that there is no process running on this port.
I tried to kill 8080 as well, but the message is still displayed.
Obviously, I refreshed the page, I tried on several different browser, even restarted my computer.
How can i determine which port is running?
How can I stop the process?
[Edit]:
Here's what I keep receiving :
<html><head></head><body><h1>It works!</h1>
</body></html>
You could use lsof:
lsof -i #localhost
Can you try this command :
sudo lsof -nP -i4TCP:80
I have a local instance of Jenkins running on port 8080 on my mac machine. I want to kill this process and have tried doing so, like below :
lsof -i tcp:8080
kill -9 <the pid>
This closes my chrome instance. But when I open Chrome again and go to localhost:8080, Jenkins is still running over there. Any ideas as to why these commands don't kill it? Also how to kill the process?
Thanks
Try using the below :
Try to identify the Jenkins instance/process id , like something below:
ps -ef| grep jenkins
Go to the server (like apache) where your Jenkins is installed and kill the process id like below :
$ kill -9 1001(processId)
lost -i tcp:8080 will also list processes that connect to port 8080, e.g. chrome. What happens if you repeat above commands after you've quit chrome? Then hopefully Jenkins should be the only process working on port 8080.
If you installed Jenkins via the OSX Installer you'll need to follow these instructions to edit the plist file via the command line (manually doing it is a pain).
When you've made necessary changes, such as running
sudo defaults write /Library/Preferences/org.jenkins-ci httpPort [YOUR DESIRED PORT HERE]
you'll need to 'unload' Jenkins:
sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist.
And now Jenkins is dead. To undead Jenkins just swap load for unload in the above command.
Whenever I'm trying to start my Apache server from XAMPP on my Macbook (MacOS-Sierra) . I'm getting following application log :
Starting Apache Web Server...
/Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd started
And status remains Stopped. I re-install XAMPP and restarted my laptop multiple times, but I'm still having same issue. Couldn't find anything help to resolve this issue.
I found the solution:
Make sure port 80 is not being used (Use Network Utility and scan for port 80. If you found any application using port 80, then kill it)
Open terminal and execute
sudo apachectl stop
(ignore, if you get any error)
On the same terminal window execute
sudo /Applications/XAMPP/xamppfiles/bin/apachectl start
Open XAMPP control panel, your apache server might have started by now, if not then you can start manually by clicking start button.
This worked for me!!
Simply goto your terminal and type:
sudo apachectl stop
It'll ask for password. Enter your system password.
Go back to XAMPP control panel and start Apache.
It should get started now.
I had the same Problem and fixed it by deleting the lib folder in Applications/XAMPP/xamppfiles/ and installing XAMPP again. It's probably due to old lib files from previous versions not being updated properly.
Another related issue, which I faced caused Apache sever failure. And failure logs is :
[Sun Jul 30 12:43:58.747822 2017] [unique_id:alert] [pid 9188] (EAI 8)nodename nor servname provided, or not known: AH01564:
unable to find IPv4 address of "MacBook-Pro.local" AH00016: Configuration Failed
To solve this :
Executed following command
sudo -e /etc/hosts
Then, changed following entries
127.0.0.1 localhost
::1 localhost
to
127.0.0.1 localhost MacBook-Pro.local
::1 localhost MacBook-Pro.local
I had the same issue when I update my XAMPP app, if you have to do this, you first have to uninstall your XAMPP (save your HTDOCS files in another folder, NOT in XAMPP folder, or you will lose it), and after that you can install the newest version of XAMPP. It worked for me, hope for you too.
I'm trying to install a neo4j server on my localhost (mac osx - El-capitan) and i'm getting this error -
Starting Neo4j failed: Address localhost:7474 is already in use,
cannot bind to it.
I tried to stop the port from running and then install it throw the neo4j install app, but it still give this error
When i try to start the neo4j server it gives me this error :
./usr/local/bin/neo4j: line 229: [: too many arguments
Try to kill your java processes :
sudo killall -9 java
Then restart your neo4j server :
./bin/neo4j restart
Same problem using Win 10, I had to turn off https-support
in neo4j-server.properties, i.e.
\# Turn https-support on/off
org.neo4j.server.webserver.https.enabled=false
You don’t need to install anything. Just download the linux tar.gz package, uncompress it and use the terminal to run the command ‘./bin/neo4j console’ to run it in console mode. You can start it in background too but based on your question, it sounds like this is just a dev machine.
I'm trying to view php files locally on my mac.
I'm running Yosemite.
I have MAMP installed on my computer. When I press start the MySQL server starts but Apache doesn't. An error message appears saying 'Error. Apache couldn't be started. Please check your MAMP installation'
I've gone through the internet typing stuff into terminal and changing 'envvars' to '_envvars' but nothing works.
I reinstalled OSX and that worked but when I shut down the computer the problem occurs again.
Can anyone help?
Thanks
Check if you changed the Document Root Location or Renamed it. At least this was my mistake.
MAMP > Preferences > Web Server > Document Root
I didn't get it working with port 8000 or the default 8888, but did get it working with port 80 per the suggestion here:
http://forums.macrumors.com/showthread.php?t=1744944
That didn't work after all, but it didn't error out. However I manually ran the following at the command line (because log file was empty):
sudo /Applications/MAMP/Library/bin/apachectl start
Only to find that after upgrading I was missing the mod_example.so
httpd: Syntax error on line 83 of /Applications/MAMP/conf/apache/httpd.conf: Cannot load /Applications/MAMP/Library/modules/mod_example.so into server: dlopen(/Applications/MAMP/Library/modules/mod_example.so, 10): image not found
Copied it from my old install and I was good to go.
If you try to start the server from the terminal, likely that will tell you what is wrong e.g.
sudo /Applications/MAMP/bin/startApache.sh
Password:
(48) Address already in use: make_sock: could not bind to address [::]:8888
(48) Address already in use: make_sock: could not bind to address 0.0.0.0:8888
no listening sockets available, shutting down
Unable to open logs
What you can do in this case, I was inadvertently running a Blockstack browser out of 8888, so changing MAMP to 8887 allowed it to start. [Your mistake might be different.]
Had the same problem, nothing in the logs. After trying the_dillio's suggestion:
sudo /Applications/MAMP/Library/bin/apachectl start
I got an error that pointed back to my vhosts file. It turns out I had an extra /VirtualHost tag. Removed it and it started working again.
i've solved this issue using this command in the terminal :
sudo apachectl stop
I think I've found the solution.
It was the wrong port. I altered the .conf file in the Apache folder. I changed all instances of port 8888 to 8000. When I run MAMP now it all seems to work fine.
Thanks for your help
Also be aware that if you by any chance deleted the folder that was set as Document Root the last time you were using MAMP, you will get this error. Simply open MAMP again, change Document Root to a location that does exist and start the servers.
I received the same error but interestingly it was caused simply because I renamed the root folder and didn't realize it. Sounds like you have a different issue but for anyone else who gets this error message, make sure you haven't renamed the root!
Absolutely bizarre behavior for MAMP PRO (paid license too btw...)
In my case I had to change the location of the log file in order to get it to work...
Click on Mysql icon then the little folder to the right of the path and try changing it to something else.
For MAMP :
You can open the terminal and write:
ps aux | grep mysql
lsof -i
killall -9 mysqld
I hope is good for you!
Bye
I had this experience when upgrading to V4. It tried to used the files from my previous installation and it just never worked. The workaround was to RENAME the original MAMP installation to something different than "MAMP", install brand new version and then copy files you may need like VHOST configs and DATABASES. After all this it worked just fine.
My Apache server problem arose after I enabled SSL. So if this is your case, check your https-ssl.conf file (Applications -> Mamp -> conf -> apache -> extra). The Document Root under the Virtual Host settings had a different file path for htdocs than where it was actually located (easily overlooked). I changed this to "/Applications/MAMP/htdocs" and problem solved. Perhaps also check Document Root in your https.conf file (Applications -> Mamp -> conf -> apache) to see if it has the correct file path to htdocs too.
These are the steps I used to solve this issue.
Checking vcredist that are required and installing them. to check which are the missing vcredist I used a tool called "check_vcredist" from wamp.
I also installed latest Microsoft Visual C++ Redistributable x64.
Doing this steps solved my issue of Apache server not running