I killed my site

I updated my remote site (http://wordsmatter.softville.com) to the latest SVN and now get an "internal server error" in both the front and back end.

I did a fresh update, build, and install on the local site and everything was fine.

I copied the local setup directory to the remote site.

I copied the new core.transport.zip file to the remote.

I did an upgrade install on the remote after unchecking the two files checkboxes.

The only hitch in the install was that I had to manually re-enter the moved and renamed manager directory location.

The install went perfectly after that.

It looks like it’s choking on the index.php file before anything else happens.

I get this in the error log:

[Thu May 14 20:21:47 2009] [error] [client 98.240.00.125] Premature end of script headers: /home/xxx/public_html/wordsmatter/index.php
SoftException in Application.cpp:252: File "/home/xxx/public_html/wordsmatter/index.php" is writeable by group

[Thu May 14 20:21:47 2009] [error] [client 98.240.00.125] Premature end of script headers: /home/xxx/public_html/wordsmatter/index.php
SoftException in Application.cpp:252: File "/home/xxx/public_html/wordsmatter/index.php" is writeable by group

Any suggestions appreciated.

OK, new question.

I’ve got the front end working and can almost log in to the Manager. The permissions of the index.php files and .htaccess files somehow changed to 666 during the install. Changing them to 644 got me this far.

On the login screen for the Manager, I see (all on one line) just the two input boxes followed by the remember me checkbox. The copyright notice is under them.

That’s it. No submit button, no styling, no prompts.  Nothing in the error logs.

Suggestions still welcome. 

Are the permissions on your core/cache directory set correctly? Sounds like that might be an issue. Try checking:

- permissions on core/cache
- emptying your cache dir entirely
- making sure pdo and php’s pdo_mysql is installed
- verify that modx_lexicon_entries table isn’t empty

What version of php and mysql is on the server?

Quote from: BobRay at May 14, 2009, 10:26 PM

I get this in the error log:

[Thu May 14 20:21:47 2009] [error] [client 98.240.00.125] Premature end of script headers: /home/xxx/public_html/wordsmatter/index.php
SoftException in Application.cpp:252: File "/home/xxx/public_html/wordsmatter/index.php" is writeable by group

[Thu May 14 20:21:47 2009] [error] [client 98.240.00.125] Premature end of script headers: /home/xxx/public_html/wordsmatter/index.php
SoftException in Application.cpp:252: File "/home/xxx/public_html/wordsmatter/index.php" is writeable by group

BobRay, how is PHP configured with the web server? I assume you are running some sort of CGI interface here?

@opengeek: I’m not getting those errors since I changed the permission on the index.php files to 644 (from 666).  I now have nothing in any error log.

I do get js errors showing in FF from line 47 of login.js ("_ is not defined") and line 55 or utilities.js ("MODx.util.JSONReader.superclass is undefined").

I notice the most of the .js file permissions are set to 666.

I’m not sure how things are configured since it’s on Lunarpages with a somewhat limited cPanel and less information than I’d like. I can’t get in the manager to see phpinfo().  I’ll put up my own phpinfo page if nothing else works.

The lexicon_entries table looks fine -- all the login stuff is there.
core/cache permission setting is 755
I don’t think it’s PDO since the site worked fine before the upgrade.
PHP 4.4.9
MySQL 5.0.67

About clearing the  core/cache direstory: Can I delete everything there or are there files that should be preserved?

This is likely a PHP 4 issue with recent changes. Why are you hosting on PHP 4 again? 2.0 will BTW likely be the only version of Revo that supports PHP 4. At this time, it serves no practical purpose for us to continue development for PHP 4, while moving to strict PHP 5 will bring huge benefits.

And no, it’s definitely not PDO, since you are not using PDO (only in PHP 5.1+).

As for the cache, you can delete those files anytime; they should always be regenerated automatically.

This still seems like a permission issue. I’ll be you need to set all folders to 755 and all files to 644 before it will work properly. Sounds like a CGI setup where they do not allow write permissions for the group. Can you set 775/644 on the entire folder where you have modx installed? Executing something like this from SSH would do the trick, though be careful and make sure you run that on the proper directory.

I thought I was already on PHP5. My host has an annoying toggle for PHP5 that works via the .htaccess file. It doesn’t seem to have any effect.

It does seem like a permission problem, though, since I get 500 server errors if index.php is set to 666. Any idea why the file permissions get reset to 666 during setup?

Unfortunately, I don’t have SSH access so I think I’ll have to do them one at a time.

Quote from: BobRay at May 15, 2009, 12:12 PM

I thought I was already on PHP5. My host has an annoying toggle for PHP5 that works via the .htaccess file. It doesn’t seem to have any effect.

It does seem like a permission problem, though, since I get 500 server errors if index.php is set to 666. Any idea why the file permissions get reset to 666 during setup?

Unfortunately, I don’t have SSH access so I think I’ll have to do them one at a time.

Yes, because that’s needed on some sites in order for the installer to write to them. In the case of CGI though, it’s the opposite, you need to make sure only the owner can write to the files. The installer just needs a way to auto-determine the permissions it should set, or accept user input to indicate this.

OK, I am actually running PHP5 now (although it doesn’t show in cPanel) -- phpInfo() confirms it. PDO appears to be enabled. Server is running suPHP.

I’ve changed the permissions on all dirs to 755 and all  files to 644 and emptied the cache dir.
The front end still runs fine and my little phpinfo.php file runs fine.

Still getting the same non-functional Manager login screen.

I just tried uploading the entire core, connectors, and manager dirs (minus the config files) from the working local install -- no effect.

The Manager was working fine until I upgraded to the current build.  Is it possible that something in the new build won’t play nice with a relocated core and/or a renamed manager directory?

The source of the login screen is identical so it seems the problem may be in the js.  Firebug reports two js errors at line 55 of manager/assets/modext/util/util.js.

Arrrgggg!!!

This is making me nuts. I modified the config.inc.php file slightly and got things workng (temporarily). It appears that the install may not have correctly set some of the urls.

A bug in the top menu drop-downs was still showing so I decided to do another upgrade install. The install ran out of memory. It’s set at 32M and my attempts to up that to 64M don’t seem to have any effect. Is there a way of installing that will use less memory?

In addition, the install set all the files back to 666. I can’t find the setup code that’s doing that so I can change it. Can somebody point me to the code?