after all kinds of editing :( :/ yea....
1: localhost will open it works! and when you refresh the page it does not work and refresh the page again and it shows up again.
2: even after running sudo apachectl stop localhost still shows it works
3: running in terminal jobs shows 9 sudo vi /etc/apache/httpd.conf
4: at one time https.config had php7 now only shows php5 after some other edits
?????any way to complete just remove apache and reinstall the hole apache?????
after a lot of editing files around found out the solution was:
for
#3 on unix ie Mac
1....( run the command in terminal) rm .httpd.conf.swp
2.... (then going back in and editing files as follows run ..... )
nano /etc/apache2/httpd.conf
3.... (change the text of ((LoadModule php5_module libexec/apache2/libphp5.so)) just change the 5 to a 7 then hit control o then enter then control x
4.... run. apachectl restart and open web browser run localhost
now if you want php add the phpmyadmin folder downloaded from phpmyadmin
first rename the folder to phpmyadmin after it has been unzipped and move it into the folder located at your Mac harddrive/Library/webserver/document you should also see your index.html.en
by the way editing this index.html.en file will let you know when you run localhost if this is intact the location it is rendering. another problem some have if they use other things like node.js mongodb and so forth and or files moved around.
Related
Today I updated my mac to macOS Big Sur and I can't open XAMPP. When I click on app it doesn't give any response.
Do you know how solve this problem?
You can do a clean installation, but you will lose all your old files and databases. I suggest making a backup of this data.
Uninstall old versions of xampp.
Installation of Xampp by the brew
brew install --cask xampp
If you don't have the brew installed
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
HomeBrew
After Big Sur installation if XAMPP is not opening, get newest version of XAMPP (7.4.12) from their web site.
If you end up with error "Error starting “XAMPP” stack: cannot calculate MAC address: signal killed". After installing the latest version, do following:
Go to terminal ->
cd ~/.bitnami/stackman/helpers
Mv hyperkit hyperkit_backup
After that XAMPP opens and tells its the first time opening, but at least I found all the files etc as before Big Sur upgrade.
Install XAMPP 7.4.12, works perfectly in MacOS Big Sur
I had Xampp 7.4.9 and update Mac OS to Big Sur. Xampp didn't want to launch after that. I lost access to all my projects inside of /htdocs folder hidden somewhere in path structure of my virtual machine.
Kindly note I used version 7.4.9-VM (not 7.4.9-Installer) that is why all my files blocked inside of
/Users/'your_user_name'/.bitnami/stackman/machines/xampp/vm/machine.qcow2
Actually all files are important here:
/Users/'your_user_name'/.bitnami/stackman/machines/xampp
not only machine.qcow2
My solution is kind a mix of before mentioned solutions because they didn’t help in full.
First of all make a backup - copy old structure (with blocked files) to some directory - all this structure:
/Users/'your_user_name'/.bitnami/stackman/machines/xampp
(To see hidden files in MacOS use [Command]+[Shift]+[.])
You also can just rename
/Users/'your_user_name'/.bitnami/
to something like
/Users/'your_user_name'/.my_blocked_files_bitnami/
As programmers here advised to install 7.4.12-VM I installed this version. Very important to install "Virtual Machine" version (as you can see there are 2 installers for each version of Xampp)
Right after I launched 7.4.12-VM the new directory was created here:
/Users/'your_user_name'/.bitnami/
and Xampp will work properly but with no your old projects.
Do not do this step: As programmers here advised to change only one file
/Users/'your_user_name'/.bitnami/stackman/machines/xampp/vm/machine.qcow2
for me it was not enough - Xampp failed with an error:
ERROR: Error starting "XAMPP" stack: cannot start stack: ssh not accessible
My solution was put whole structure from folder xampp
/Users/'your_user_name'/.my_blocked_files_bitnami/stackman/machines/xampp
to here:
/Users/'your_user_name'/.bitnami/stackman/machines/xampp
You may before rename your current folder
/Users/'your_user_name'/.bitnami/stackman/machines/xampp
to something like
/Users/'your_user_name'/.bitnami/stackman/machines/new_xampp_without_my_projects
Then launch Xampp (Xampp should say something about incopatible versions but allows to continue), start all services, mount the disk. press "Expore" and you should see all your old projects.
Thank you.
You can solve this problem by updating xampp ver 7.2.34 .
https://www.apachefriends.org/download.html
Same thing happened to me but the version 7.4.12 seems to be working. I download it from the link I'll but below. I've been reading and the problem seems to be that Big Sur changes some paths that are set by default and so the apps won't launch. Same thing happened to Apache NetBeans.
XAMPP Download Link:
(https://sourceforge.net/projects/xampp/files/XAMPP%20Mac%20OS%20X/7.4.12/)
I had the same problem. This is how I solved it:
First, be sure that you back up your files in XAMPP VM. Your files are in
/Users/'your_user_name'/.bitnami/stackman/machines/xampp/vm/machine.qcow2
Then you can reinstall XAMPP again. I have installed 7.4.12 and it worked fine.
If you see stack error message, this is what you have to do:
Close XAMPP
Open a terminal and remove the stack folder with the following code:
rm -rf ~/.bitnami/stackman
Open XAMPP and check if a new stackman folder is created.
/Users/'your_user_name'/.bitnami/stackman/
If it does not, then start XAPP and stop again. When the stackman folder is created, override the file below with your backup file.
/Users/'your_user_name'/.bitnami/stackman/machines/xampp/vm/machine.qcow2
Close XAMPP again and restart again.
Voila! Here are your files...
I tried reinstalling XAMPP on MACos Big Sur, and it worked. However, my files are not recovered.
you can type this code in terminal
before this code you should close xampp
rm -rf ~/.bitnami/stackman
if you are getting error message saying:
Cannot calculate MAC Address: Using fd 10 for I/O notifications hv_vm_create HV_ERROR (unspecified error)
you need to download new hyperkit from bitnami and replace the current one
cd /tmp
curl -LJO "https://downloads.bitnami.com/files/hyperkit/hyperkit-testing-`20210430"`
mv /tmp/hyperkit-testing-20210430 ~/.bitnami/stackman/helpers/hyperkit
chmod +x ~/.bitnami/stackman/helpers/hyperkit
read tutorial here:
https://floyk.com/en/post/xampp-doesnt-work-after-update-to-macos-big-sur
I am running MacOS Mojave 10.14 with XAMPP 7.2.5
Earlier today, I tried to start up XAMPP after a crash/restart. XAMPP Manager was unable to start the MYSQL Server. Apache did start correctly.
Figuring there was a potential corruption, I used my Time Machine to restore my XAMPP folder (to a 36-hour old file) in Applications.
Now when I try to run XAMPP Manager, I get a "Cannot find any readable ctl script" error message.
I've tried to run MYSQL Server directly from CLI. I receive the following message:
./mysql.server: line 200: my_print_defaults: command not found
Starting MariaDB
ERROR! Couldn't find MariaDB server (/Applications/XAMPP/xamppfiles/bin/mysqld_safe)
Any thoughts on how to resolve?
The issue has to do with a quirk with Time Machine - it does not completely regenerate all recorded folders/files. A bit of a pain.
I was able to run XAMPP from the command line:
-> cd /Applications/xampp/xamppfiles
-> sudo ./xampp start
To check on MYSQL status:
-> mysql status -u [username] -p [password]
Issue resolved
I spend a day on this and the solution in my case was:
Uninstall XAMPP
Delete all files except my databases folders from Applications/XAMPP/xamppfiles/var/mysql (there was some .err and log files if I remember well)
Reinstall XAMPP
Reconfigure it. If you use different user than root to access your databases you need to recreate it.
I got the "Cannot find any readable ctl script" error after a Time Machine restoration, too. I'm on 10.12.6 and XAMPP 5.6.
You are correct that it appears to be a TM issue, but I was able to resolve it by entering TM and specifically selecting the directories in XAMPP/xamppfiles/ that TM would not copy over by just selecting XAMPP/xamppfiles/. (In your case, you would not want to copy over /var/mysql, assuming you want to keep your data.)
Relief. There's nothing worse than realizing your trusty backup is not so trusty.
I have spent weeks trying to resolve different errors in building Hadoop. SO was helpful in pointing me towards the answer to an occasional problem, but after a lot of searching here on SO, I was never able to get the whole thing to build.
It’s been a couple of weeks since all this started so I have forgotten most of the explicit error messages, but the problems I had included
Protobuff versions being wrong
SSH connections not working
Mojofailure Exceptions during build
Incorrect Java versions being used
C++ sanity checks failing
a host of other crap that made no sense to me and I couldn't decipher root causes for
Today I finally got Hadoop to build from the git repo source and wanted to record the process for the SO community members that face similar problems.
For those of you trying to build Hadoop from source, here is how I got everything to compile from source.
Some notes on configuration:
I am installing Hadoop in a virtual environment, in my case VirtualBox.
The Host machine runs Windows 7 x64
The Guest VM runs CentOS 7 x64
I am aiming for the bare minimum installation
How to Build Hadoop From Source Without Errors
Preliminary Downloads:
You need to download the following before you begin.
Virtual Box (I used version 4.3.16 r95972 available here: old VB builds)
CentOS 7 minimal iso file from - http://www.centos.org/download/
WinSCP (version 5.7.4) - https://winscp.net/eng/download.php
This walk through consists of 4 Phases
Create a CentOS Appliance inside VirtualBox that can support
building Hadoop
Add SSH capabilities to the Appliance so that downloaded prerequisites can be scp’ed from the Host to the Guest VM
Install all the things (utilities and dependencies) needed to build Hadoop
Build Hadoop without errors
Phase 1 - Creating a CentOS Appliance for VirtualBox
Start by opening VirtualBox and clicking on the “New” button in the top left corner. This will open a new window asking for some information about the virtual machine appliance you want to create.
Name it “CentOS x64 – Hadoop Base”
Select Linux as the “Type” of operating system
Select RedHat (64 Bit) as the “Version.”
Click “Next”
Follow the remaining prompts in the VM creation wizard. The only things I changed from the defaults where on the “Memory size” passage (I used 4096 MB) and the “File location and size” passage (I used 128 GB). I would encourage you to do the same if your system can support it. Leave all other defaults alone
Click “Create” on the last passage of the VM creation wizard
Once created, the VM will show up on the left hand pane of the VirtualBox Window.
Double click on the VM you just created and wait for the dialog to come up asking you for the iso file you want to use.
When the dialog appears, click on the folder icon on the right and navigate to / select the “CentOS minimal iso” you downloaded during the Preliminary steps.
Once the iso is listed in the drop down box Click “Start”
When prompted, after the VM boots, select “Install CentOS 7” (this is not the default, you have to press the “up” arrow) and press “Enter”. When the setup program loads, the first thing it will ask you about is your keyboard layout. I leave the defaults in place and just click the “Continue” button in the lower right corner. This brings up the Installation Summary page on which you need to make changes to 2 areas: “Installation Destination” and “Network & Host Name”
Click “Installation Destination”
Double Click the virtual disk (make sure that the background is blue and the check mark is there)
Click “Done” to go back to the "Installation Summary" page.
Back on the Installation Summary page,
- Click “Network and Host Name”
- In this menu screen turn on Ethernet networking by clicking the toggle switch on the right.
- Click “Done” in the top left corner.
With both modifications complete you can click the “Begin Installation” button in the bottom right corner. As the iso installs to your system you should take the time to provide a root password by
Clicking on that option at the top left of the page
Filling out the form it brings up
Clicking “Done” (if you select a password considered weak, you have to double click “Done” to accept anyway).
I added a password, but I did not bother to add any non-root users.
Once everything is installed click on the “Reboot” button that appears in the bottom right of the screen.
Once the system reboots select CentOS 7 and allow it to boot. Check your credentials by logging in as root, and then close the CentOS VM by clicking on the red X button at the top right of the window and selecting “Power off the machine” when prompted.
This completes Phase 1
You should now be looking at just VirtualBox
Phase 2 - Adding SSH capabilities to the VM to support download transfers
Open the settings of your CentOS Appliance by first clicking the appliance
Next, click the “Settings” button on the top left of VirtualBox’s main menu. This will bring up a new window.
In the left hand pane of the new window, click on “Network” which will display a set of adapter tabs.
Now click on the Triangle to the left of the label “Advanced”.
This will reveal a series of options, but the one you need to click on is the button labeled “Port Forwarding”
This will bring up another window where you can set port forwarding rules.
Click the green plus sign in the top right corner. This will produce a row where you can enter in a port forwarding rule.
Add the following rule to the row
Name= ssh, Host port =2222, Guest port = 22
Click the “OK” button on the Port Forwarding window
Click the “OK” button on the Appliance Settings window.
With this rule in place you should now be able to ssh from your Windows Host to the CentOS Guest on port 2222 and avoid the following error:
ssh: connect to host localhost port 22: Connection refused
You should now be looking at just VirtualBox again.
Start the CentOS VM appliance and log in as root.
Once logged in, execute the following line from the command prompt.
yum –y install openssh-server openssh-client
This command will install a ssh server on the CentOS VM. After the install, confirm that the ssh server is running by typing the following command.
ps –aux | grep sshd
This command should return 2 processes showing sshd (the ssh daemon). One is the grep command itself. The other is your server running in the background.
Now we need to make sure that ssh did in fact generate the keys it will need to communicate with WinSCP. Issue the following command and make sure that all keys’ byte size values are non-zero.
ls -l /etc/ssh
If the sizes of the keys are 0 bytes, you need to remove them, restart the sshd daemon, and validate that the keys were regenerated when sshd restarted. To do all that, execute the following commands
rm –rf /etc/ssh/ssh*key*
systemctl restart sshd
ls -l /etc/ssh
This processes will help avoid unexpected “connection closed by 127.0.0.1” errors.
Now that we have an ssh daemon up and keys generated, we are going to test the connection. Start by opening WinSCP. And entering in the following values on the start menu that pops up.
Host name = localhost, Port number = 2222, User name = root, Password = , File Protocol = SCP.
Note that you need to set “File Protocol” last. If you don’t, it will try to outsmart you when you enter in a “Port number” that it isn’t expecting. When all the values are entered. Click the “Login” Button and accept / click Update or OK to any security warnings you get.
Once you have logged in, move a file between the Host and VM Guest to confirm everything is working.
Though I won’t focus on it here, you can also us Cygwin to connect to the VM, and it is useful for diagnosing connection problems. The command you need to enter to get verbose diagnostic output is
ssh –vvv –p 2222 root#localhost
This completes Phase 2
Phase 3 - Install Utilities and Dependencies Needed to Build Hadoop
Our CentOS distribution really is “barebones” and so we need to install everything required to build Hadoop. We will do this by downloading most things in Windows and then moving them over to the VM via WinSCP.
Before we start, we need to add a “downloads” directory to the home directory of the root user on the CentOS VM by issuing the following command at the CentOS command line.
mkdir ~/downloads/
We can now begin downloading Hadoop dependencies. We will download everything to Windows and then use WinSCP to move it over to the VM.
Start by downloading the Java 7 JDK from - http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Ignore the “End of Public Updates” error message at the top of the page. Java 7 is what Apache recommends.
You want to download the jdk-7u79-linux-x64.rpm file
Once downloaded use WinSCP to navigate to the Downloads directory of the Host computer and the newly created “downloads” directory of the Guest VM (you may need to click the refresh icon on the VM side of the WinSCP pane to see the directory). Drag and drop the jdk file from the Host over to the VM Guest.
Now we just need to install the JDK on the CentOS VM. From the CentOS command line change your directory to the “downloads” folder we created under root’s home, once in the “downloads” directory use rpm to install java 7.
cd ~/downloads
rpm –ihv jdk-7u79-linux-x64.rpm
Once installation is complete, you can verify it by typing
java –version
Which will produce output stating that you have a Java Run Time Environment installed.
Next we are going to install a subset of the packages Hadoop needs to build successfully. The list is taken straight from the Apache website: https://wiki.apache.org/hadoop/HowToContribute and the command we need to enter on the command line to retrieve them is:
yum -y install lzo-devel zlib-devel gcc autoconf automake libtool openssl-devel fuse-devel
Next we are going to install Apache’s Maven. You can download it here:
https://archive.apache.org/dist/maven/binaries/
Apache’s website says you can use version 3+. I used version 3.2.2 so download this file to follow along:
apache-maven-3.2.2-bin.tar.gz
Once you have the file downloaded, use WinSCP to move it from your host computer to the Guest VM ‘s “downloads” folder just like you did with the JDK file. We then untar the file into the /usr/local/ directory, and create a symbolic link in the /usr/local/ directory that points to the maven folder with the following three commands.
tar xzf apache-maven-3.2.2-bin.tar.gz -C /usr/local
cd /usr/local
ln -s apache-maven-3.2.2 maven
We now need to add Maven’s bin directory to the $PATH variable. We do so by editing the .bashrc file in root’s home directory. Open the file for editing in vi by using the following command
vi ~/.bashrc
This will bring up the bash file in the vi editor ( if you need it, a tutorial on vi can be found here: http://www.unix-manuals.com/tutorials/vi/vi-in-10-1.html ) follow these instructions to correctly update the file.
Enter Edit mode by pressing the “a” key
Add the following lines to the file:
export M2_HOME=/usr/local/maven
export PATH=$M2_HOME/bin:$PATH
Press the “Esc” key to leave Edit mode
Type “:wq” – it will automatically show up at the vi command line (bottom left of the screen)
Press “Enter”
Now log out of CentOS. Log back into CentOS, and check to make sure that the new PATH variable is appropriately set using the following commands.
exit
<log back in as root>
mvn –version
you should see output indicating that maven is currently installed
Next we need to install C++ support for gcc. We do that with the following one line command
yum –y install gcc-c++.x86_64
Next we need to install git so that we can pull down the Hadoop source code.
yum –y install git
Once you have git. Go ahead and pull down the Hadoop source. There is still one more thing (ProtocolBuffer) we need before we can build the source code, but we need to see the BUILDING.txt file in the repo before we download ProtocolBuffer to make sure that we get the right version.
To get the Hadoop source we run the git clone command. Simply execute the following commands from the CentOS command line to download the Hadoop repo.
cd /usr/local
git clone git://git.apache.org/hadoop.git
The clone operation will place a “hadoop” directory in your /usr/local directory. When the operation has completed and you have the command prompt back, take a look at the BUILDING.txt file in your new hadoop directory using the following command:
less /usr/local/hadoop/BUILDING.txt
In the “Requirements” section of the file it states the version of ProtocolBuffer we need for Hadoop to build correctly. In this case it’s ProtocolBuffer 2.5.0. With this information in hand we go back to the command prompt by pressing “q” for quit.
Now we can finally, install the last of the things Hadoop needs: ProtocolBuffer. To get the right version of ProtocolBuffer, we visit the ProtocolBuffer release page:
https://github.com/google/protobuf/releases
and scroll down until we see the version needed for Hadoop to compile. For this walkthrough you want to download the following file.
protobuf-2.5.0.tar.gz
Once downloaded, use WinSCP and transfer it to the VM’s “downloads” folder like you did earlier for the other downloads. Once the file is sitting in the VM’s “downloads” folder, issue the following commands to install ProtocolBuffer on CentOS
cd ~/downloads
tar xzf protobuf-2.5.0.tar.gz -C /usr/local
cd /usr/local/protobuf-2.5.0
./configure
`make'
make install
Once this is done all the prerequisite utilities and dependencies needed for building Hadoop will be installed.
This completes Phase 3
Phase 4 - Build Hadoop Without Errors
Go to the Hadoop directory, and run Maven skipping the tests using the following commands:
cd /usr/local/hadoop
mvn clean install -DskipTests
The build should now occur without any problems and when everything is finished, you should see a screen like the one below.
This completes the walk through
I hope some of you find it helpful.
I know this was a question of how to build hadoop from source, but after running into a variety of errors throughout the build process, I found this extremely helpful. Someone has already built Hadoop on Windows and posted the binaries. I setup this version on my Windows machine and it is working great:
http://www.barik.net/archive/2015/01/19/172716/
I'm running a MacPro G5 w/ 10.5.8. I ran:
sudo port selfupdate and then ran:
sudo port upgrade outdated
When it was all finished, I rebooted and apache2 was broken and would not serve PHP file any longer. If I replace the httpd.conf file, it will serve html files.
I finally gave up and restored the backup and the machine is running again. The problem is I have a second machine that I did the same thing on and don't want to go through the same process. I've read several posts about uninstalling/reinstalling Macports like this one from Kirk Roybal How to do a clean reinstall with macports?, but it doesn't say if this process will destroy or reset the contents of the /opt/local/ directory. Especially the MySQL DBs and htdocs contents. Does anyone know if this process is linked or destructive? I'll make backups of everything, of course, before trying anything.
SOLUTION:
I got it to work by making the php53 install work instead of going backwards. Here's what I did:
sudo port select --set php php53 (set MacPorts to use php53 instead of php5)
sudo port installed (Check to make sure php53-apache2handler is installed)
sudo port install php53-apache2handler (It wasn't and yours probably isn't either)
once that's done installing
php -v (check the version of PHP that's running)
cd /opt/local/apache2/modules
sudo /opt/local/apache2/bin/apxs -a -e -n php mod_php53.so (activates php within apache)
this should append
LoadModule php5_module modules/mod_php53.so
to your /opt/local/apache2/conf/httpd.conf file (check it now)
There will also be a line like this
LoadModule php5_module modules/mod_php5.so
Comment it out or remove it so is doesn't interfere with new install
It should also move a copy of mod_php53.so to
/opt/local/apache2/modules
If it's not there, see php53-apache2handler install above.
Check your httpd.conf file for errors
/opt/local/apache2/bin/httpd -S
Finally, create/edit php.ini file to tell apache2 how to connect to MySQL database
cd /opt/local/etc/php53
sudo cp php.ini-production php.ini (for production machine use development for dev machine)
sudo cp php.ini php.ini.bak
Add the default socket paths to php.ini
pdo_mysql.default_socket=/opt/local/var/run/mysql5/mysqld.sock (may vary based on MySQL version. Check the /opt/local/var/run directory if not sure)
mysql.default_socket=/opt/local/var/run/mysql5/mysqld.sock
mysqli.default_socket=/opt/local/var/run/mysql5/mysqld.sock
If you are having problems connecting to MySQL, check for typos in the above paths FIRST. Trust me it will save you tons of time!
If all went according to plan, you should be able to restart the machine, test to make sure all ports started automatically and things should be working.
The files that you add (eg: MySQL DBs) are not destroyed by an update. If you modify files that are managed by MacPorts (eg: they are listed in 'port contents '), then those modifications will be clobbered by an update.
Some projects install config files as examples and have the user make the real config file so as to not clobber it with an update. It looks like the apache2 port follows this pattern. It installs /opt/local/apache2/conf/original/httpd.conf and then copies it to the real location of /opt/local/apache2/conf/httpd.conf at activation time only if the file does not exist.
Today I updated to OS X Mountain Lion. I noticed that Apache won't start in MAMP. Nothing new seems to be in the apache log file. Running sudo apachectl -k start in Terminal gives me this:
httpd: Could not reliably determine the server's fully qualified domain name, using Ryan-Smiths-MacBook.local for ServerName
I do have ServerName defined in my httpd.conf file.
I also noticed that "Web sharing" is no longer in the Settings pane... weird.
Any Ideas?
Thanks!
Hi Ryan we had this problem
It turns out the systems own apache is running. We've documented it here http://support.servertastic.com/mamp-not-starting-after-upgrade-to-mountain-lion/
Cheers
Richard
To fix the problem, and to start MAMP apache, you can now refer to: (the above link is broken now.)
https://support.servertastic.com/mamp-not-starting-after-upgrade-to-mountain-lion/
Or simply run the following command:
sudo apachectl stop
In addition if you run into trouble where your mysql no longer will start, try killing the mysql process that may already be running by doing the following:
Open up the program called "Activity Monitor" on your Mac.
Search for a process called “mysqld“.
Click on that process and “Quit Process”
Credits:
http://eliteeternity.com/mysql-server-wont-start-mamp-red-light-mac/
http://forum.mamp.info/viewtopic.php?f=6&t=6149
In MAMP PRO 2.1.1, click Tools > Quit Built-in Apache.
I was able to solve this running OS X 10.8.4 by opening up Activity Monitor, choosing "All Processes" then killing any with "httpd" in the title. After that I was able to start MAMP and both the MYSQL and Apache servers gave the green light!
this one fix my MAMP
Just navigate to /Applications/MAMP/bin/apache2/bin using Finder, and rename envvars to _envvars (yes, just add the underscore). Boom! Done and done.
from codesoap
Had the same problem; no other tricks helped. I found I had an instance with "allow from 127.0.0.1" – removing the IP did the trick. Don't know why.
http://cl.ly/image/253g1L1W472z
The problem with OSX Mountain Lion is that /usr/lib/libpq.5.3.dylib does not exist, but /usr/lib/libpq.5.dylib does.
To fix the issue, open terminal and:
~# sudo ln -s /usr/lib/libpq.5.3.dylib /usr/lib/libpq.5.dylib
just try to modify mamp in httpd.conf with:
LoadModule php5_module /Applications/MAMP/bin/php/php5.5.3/modules/libphp5.so
My solution to the similar problem. I.e. MySQL was running fine from MAMP manager utility. Apache server did not and the "Open start page" was greyed i.e. not working.
It seems that my problem was, that the Apache server was not for one reason or another able to access it's log file apache_error.log in /Applications/MAMP/logs folder. The file seemed to be somehow "stuck" i.e. I was not able to change the access rights to the file with chmod command. Only after I deleted the log file completely and then restarted the MAMP control utility and started there the MySQL and Apache again, everything worked fine.
BR,
Janne
Had the same problem.
I then set the ServerName to localhost and the Listen port to 8080, because 80 was somehow not available (even not as sudo). In my case it seems to have fixed the problem.
If nothing works for you like me, the problem is likely that you ran your MAMP update with MAMP running, then you closed the existing MAMP without stopping your server. All you need to do is restart your machine.