I've got a drupal 6.x multi-site setup going, which has been working pretty well. Recently, on some of my sites, I've started getting 500 Errors when trying to visit /admin/build/modules. Not on all of the sites running off of this multi-site codebase, however. The sites that are breaking seem to be the ones that have more modules installed than the sites that still work.
It's cheap shared hosting, so my lead suspect is memory limits, and I'm waiting on a response from my host to confirm it. I've noticed there are a lot of inquiries on d.o. concerning 500 errors, but not a lot of answers. The most likely insight I found was this comment.
However (and while I await error log confirmation from my host), it has also been suggested that incorrect execute permissions on scripts will cause a 500 error. So I'm wondering if there are any shell-scripting geniuses that could show me how to fish out any scripts from /sites/all/* that might have incorrectly set execute permissions... anyone?
Incorrect execute perms does seem unlikely, since I have sites with fewer contrib modules enabled where the /admin/build/modules page still loads fine... and all my contribs are in the same place in this multi-site arrangement: /sites/all/modules & /sites/all/themes
In any case, I thought a command or script that could crawl around and fish out "fishy" file & folder permissions might be useful, but I don't know how to do it myself.
Thanks upfront!
--
Matt J. Sorenson (emjayess)
d.o. | g.d.o. | WEBJAX'd! | twitter
