MAMP PRO localhost waiting...

Hi,

My setting :

OSX : 10.10.3
Mamp Pro : 3.2.1
MODX : 2.3.3
MySql : 5.5.42
PHP : 5.6.7
Apache HTTP port : 8888
Apache HTTPS port : 8890
MySql port : 8889

I use MAMP Pro for local development with MODX fo many years. I have more than 20 sites under Mamp Pro. Since today (2015-06-09) I had never had any problems.

Now, It take more than 5 minutes to log to the manager, but I have no problem at all to see the front end of my local websites.

And when I am logged, it take several seconds (more than 10) to display any pages in the manager.

I have access to PHPmy Admin with no problem.

Clearing the core/cache and clearing the browser cache did not change anything.

The error log (Apache, MySql, PHP, DDNS ) of MAMP and Modx error log, indicates no error.

Does anyone encountered this problem and found a solution?

Thank you for your help.

I use XAMPP so I have no idea if there are any different factors for MAC and MAMP... but I have had some problems before, yand I chalked it up to some files either in the system that got changed or after being away from using the system OR migrating a site over, etc etc (keyword files system and server like htaccess) something got screwed up.

I had a production installation screwed up just sitting on a shared server. This was before shellshock was revealed. I knew the server had been compromised. Poor hoster didn't listen, blamed me. In the end I discovered it was and the hacker got in - If I remember correctly I found some corrupt/missing files/and surprise new files being deposited, that a db user/pass had been sniped, etc. My local copy was just fine, backed that up, imported my production in and wham -ok. After this I moved to a better host who was up on security and patching aggressively to the recent shellshock bug, restored and fine. Point is - always have a backup and you probably have to restore your files.

Now how does this apply to local environment??

Due to the shellshock problem that the media, and companies like Apple have ignored and hidden from their customers: linux web servers can be patched (yet this relies on humans at hosting) but local Apple (linux-based OS) cannot be patched, this requires a proper rebuilt OS. So all MACs and devices are sitting ducks for hackers. Windows is not susceptible. I am not an apple user but the same scenario could be possible and I'm guessing Apple has not released an replacement OS? So security might be an issue where some of your local files have been compromised or make sure you check your core local server/php files, etc that you didn't change anything or when editing left an mistake.

But first thing I would do is backup your existing and restore a backup of your last good one. From my experience I have a checklist where I literally have a mirror copy of my modx installation, dbs, everything, so i can troubleshoot fast - organization key.

Hopes this helps - got to be a problem with file(s).

My local MAMP started doing that, but only on first Manager login after installation. I had just "upgraded" to Yosemite, but it turns out that Yosemite has broken external monitor support. So I backed up what I wanted to keep on an external hard drive, wiped the machine clean and re-installed the original OS and upgraded it to Mavericks, then re-installed the latest versions of my apps. So I know it's not anything wrong with my installations.

As far as shellshock and OS X, you are misinformed. It is quite possible to manually build and update bash on OS X, and Apple has provided updates for several versions of OS X.

http://arstechnica.com/apple/2014/09/apple-patches-shellshock-bash-bug-in-os-x-10-9-10-8-and-10-7/

Looks like your right, my info came from Norton, and I think Wired I believe around when it broke, and I read and followed it in-depth - at the time no word from Apple. And seriously then the articles I read from supposedly good sources were incorrect. I remember reading that linux web servers could be patched but OS and bash-based, not patched but rebuilds only. Hmmm... very shady.

An Apple representative told Ars that the company would not be releasing an individual patch for users running the current OS X Yosemite developer or public beta builds, but the rep went on to say the bug will be fixed in future builds of the software.

I wonder how many average Apple consumers (not one out of several I have talked to ever heard word from Apple about Shellshock or updates) have not patched their system or have old OS. Guess it doesn't matter according to that article.

Thanks for the article... geesh, one really can't believe what you read online these even from supposedly legitimate sources - I'm wondering if that PR from Apple and Ars is even correct, seems a couple elements are contradictory towards what I read when there was fury to patch web servers. Can't believe anyone these days :\

Well, the patch I linked to is only good for the three versions previous to Yosemite, so whether or not Yosemite has been patched or not I can't say. But the article I linked to has links to manually building it, so I think it can be done.

Thank you for your comments.

As for me, I think I found the problem. MAMP PRO does not like MODx 2.3.3 or MODX 2.3.3 does not like MAMP PRO

Here's what I did :

- Backup all my websites under my MAMP Pro
- Uninstall MAMP Pro
- Re-install OS X 10.10.3
- Re-install MAMP Pro
- Install MODX 2.3.3

After install MODX 2.3.3, the problems was there again :

- login to the manager take more than 5 minutes

- Loading Extras was ok for the firts one, but for the second I can not load it, I got a error message.

- Sometines I got this message => Internal Server Error. The server encountered an internal error or misconfiguration and was unable to complete your request,

- In the error log of Apache I got these messages:

[Mon Jun 15 23:13:52 2015] [error] [client ::1] FastCGI: comm with server "/Applications/MAMP/fcgi-bin/php5.6.7.fcgi" aborted: idle timeout (30 sec)

[Mon Jun 15 23:13:52 2015] [error] [client ::1] FastCGI: incomplete headers (0 bytes) received from server "/Applications/MAMP/fcgi-bin/php5.6.7.fcgi"

[Mon Jun 15 23:36:56 2015] [error] [client ::1] FastCGI: comm with server "/Applications/MAMP/fcgi-bin/php5.4.38.fcgi" aborted: idle timeout (30 sec), referer: http://simo:8888/manager/?a=workspaces

[Mon Jun 15 23:36:56 2015] [error] [client ::1] FastCGI: incomplete headers (0 bytes) received from server "/Applications/MAMP/fcgi-bin/php5.4.38.fcgi", referer: http://simo:8888/manager/?a=workspaces

I decided to check if these problems were common to all versions of MODX.

- I install MODX 2.2.16 => No problem at all.

- I install MODX 2.3.1 => No problem at all.

- I install MODX 2.3.2 => No problem at all.

Only MODX 2.3.3 causes problems.

For now everything works fine if I don't use MODX 2.3.3.

It might be good to know if other people have had problems with MAMP PRO 3.2.1 and 2.3.3 MODx, so whether MODx 2.3.3 is involved.

It is always better to work with the latest version of MODx, something I can not do now.

Thank

When I had updated to Yosemite, I had long Manager load times on first access after installation. Since I have returned to Mavericks, that isn't happening. I don't use MAMP Pro, though.

It might be interesting to try the Bitnami MODX stack and see how that behaves for you. https://bitnami.com/stack/modx

Thank sottwell, for the information.

For now, I'm pretty busy. I will try this option later.