Tag Info

Hot answers tagged

10

I'd say unified GUI integration. With MAMP, you've got a single window to manage Apache, PHP, and MySQL. Whereas with the built-in stack, you have to active PHP manually and have another interface for MySQL (with no easy way to turn it on or off)


5

MySQL is not installed by default, even though the included PHP is compiled with MySQL support. Check out this guide for MySQL installation.


5

OK, so I found the culprit. It is amazing that no error message was visible in console or in the error logs, but I found a site which helped me a lot. http://blog.joshdick.net/2012/07/28/troubleshooting_apache_in_os_x_10.8_mountain_lion.html In that post, the author, Josh, suggested restarting apache using the following command: sudo bash -x ...


5

The disadvantage is that you're installing stuff that you already have installed. This can cause problems when - for example - you want to use PHP using the command-line. This will trigger the built-in PHP version by default instead of the one bundled with MAMP. If these are different the results can be unexpected. I would recommend using the default OSX ...


5

There is no way to make Numbers get data from a database. (It's more of a consumer tool.) https://discussions.apple.com/thread/1827581 A workaround: you can use Excel to grab the data, and import the XLS file to Numbers for prettier chart-making.


4

The correct answer is sudo launchctl unload -w /Library/LaunchDaemons/org.macports.mysql5.plist And you start it with sudo launchctl load -w /Library/LaunchDaemons/org.macports.mysql5.plist Thanks to kh13org for the pointer.


4

Actually, the #1 advantage to using MAMP is tremendous: Each time you upgrade your system, your environment won't break! There were a couple of Snow Leopard updates (or maybe it was Leopard to Snow Leopard, I can't remember) that broke Mysql. One was by moving the mysql.socket file. There was another update the broke PHP. In both cases I had to hunt around ...


4

In Activity Monitor there is a dropdown menu in the top of the window. My Processes was selected. Changing it to All Processes solved the issue.


3

It is not ridiculous at all. I'd assume that, seeing you're coming from a Windows environment, you simply don't understand Unix sockets. An Unix socket file is created when mysqld is started up, and mysql.sock is that file. It is a faster alternative to TCP/IP for use on a local system. So yeah, it is actually totally normal that the file is deleted when ...


3

If you are using the terminal client, generally you can do things like reset the root users password for mysql or create databases. A simple example can be found at the MySQL docs site, of which I will copy the highlights. To create a new MySQL user: Login to MySQL in Terminal:mysql -u username In the prompt:CREATE USER 'admin'@'localhost'; GRANT ALL ...


3

You can use a GUI client, like Sequel Pro.


3

Feel free to copy one of the example files into the /etc directory or make your own. You won't have any problems until you ever want to have more than one version of mysql installed and running - then you can set up shell variables to keep things apart - but for the short run - one file in one place would be good. So let the Workbench make /etc/my.cnf and ...


3

Briefly; no there is no easy way to update them. (Assuming that compiling from source is not considered easy) I would strongly caution against modifying the system installed versions as you're likely to have your updated versions broken when Apple issues an update that updates them. (Usually Security Updates and has bitten some users/sysadmins when Perl has ...


3

I had the same symptoms, but a different problem: perl, by default, runs as 64bit executable, but my mysql installation and hence all its libraries are 32bit only. Forcing perl to run in 32bit mode solved it: defaults write com.apple.versioner.perl Prefer-32-Bit -bool yes


3

Open terminal, then: sudo launchctl list | grep -i mysql launchctl remove xxx.xxx.mysql Where "xxx.xxx" is included in the output of the first command, for example "org.macports.mysql". The password for the "sudo" command is your own user account's password. True, sudo isn't needed to "list" but because you already gave a sudo password for the first ...


3

The following assume your MySQL 5.1 is installed in /usr/local/mysql-5.1.46-osx10.6-x86_64 and that MySQL 5.6 will install in /usr/local/mysql-5.6.11-osx10.7-x86_64. The exact directory names might differ depending on the exact version number you are using. Download the MySQL 5.6 installer, for instance in DMG format, and run ...


3

command not found just means that the executable you're trying to run is not found in any of the directories in your $PATH environment variable. Try /usr/local/mysql/bin/mysql The documentation links include a platform guide where it tells you that MySQL gets installed into /usr/local/, and then a symlink is created at /usr/local/mysql that points to this ...


2

This is not a problem with OS X or Apache. A redirect doesn't change any PHP code behavior and since you apparently get response from the code, nothing is wrong with the server setup. The problem lies in the way Wordpress reads the domain name from the request (which is the only thing that should differ) and what it does with it.


2

I was able to solve this problem—it turns out that WordPress behaves better when I set both the WordPress address and the site address to http://localhost/~Gabe/mysite.dev/.


2

PROBLEM SOLVED! I found the way around it. Just create an AppleScript with sudo inside for mysql server startup do shell script "apachectl start" password "mypassword" with administrator privileges do shell script "sudo /usr/local/mysql/bin/mysqld_safe > /dev/null 2>&1 &" password "mypassword" with administrator privileges


2

No, I don't believe Lion comes with any sort of SQL server pre-installed.


2

Depending on the uid mysqld is using, chmod 700 on the data directory might not help. You may do the following: chmod 777 /usr/local/mysql-5.5.15-osx10.6-x86_64/data/ Startup mysqld again ls -l /usr/local/mysql-5.5.15-osx10.6-x86_64/data/ to identify the owner of the created files chown OWNER /usr/local/mysql-5.5.15-osx10.6-x86_64/data chmod 700 ...


2

Starting MySQL server automatically actually means executing the /usr/local/mysql/bin/mysqld dæmon on startup. If MySQL won't do it for you, it's easy enough to add the necessary instructions yourself. For this, we'll add a launchd job descriptor to the /Library/LaunchDaemons folder. The procedure is very well described in this Mac OS X Hints article. ...


2

Its not exactly what your looking for, but we used automator to create a launchable application that runs a commandline to export the sql database. We then used crontab to schedule the app to run at certain intervals. In automator add the "Run Shell Script" action. Set the shell to "/bin/bash" and add the command /usr/local/mysql/bin/mysqldump --opt ...


2

The answer to this superuser question and this stackoverflow question both say approximately the same thing, that you need to perform the following actions: If you haven't yet rebooted your computer, the process could still be running. First, reboot. Then if MySQL is still showing up after a reboot, from the Terminal, issue the following ...


2

See my answer to your question at superuser.com.


2

We (myself and Mr. Burning) did some diagnosis in chat, and I will detail what we did find: The root of his problem was that MySQLd was already running in some capacity. This could have been a previous version of MySQL installed from Homebrew, still running after upgrading the binaries/libraries. Our resolution was to simply kill all of the running ...


2

Yes, Apache and PHP already come by default with a Mac OS X installation, and you can download an installer for MySQL on their website. For a configuration guide, have a look at this related answer: How to turn Mac OS X Lion into a web server? The linked answer also applies to Mac OS X Snow Leopard. Another popular (and imo superior) way of running ...


2

The log says it all: The script cannot write to the file /usr/local/var/mysql/xxx.local.err due to insufficient permissions. I assume the log file belongs to a dedicated mysql user while you are starting the process using your user account.



Only top voted, non community-wiki answers of a minimum length are eligible