I finally got around to upgrading from 1.5.2 to 1.6.3 today, followed every instruction to a t, and even double checked cuz I didn’t want any problems.

I checked the main web site, the part that the customers see, and it is working, so at least that part of it worked out correctly.

BUT,,,,, got a bit of a problem when I try to go to the ee admin control panel.

Yes, I am going to the correct directory, I had it bookmarked and even manually typed it in, and I keep getting the following error.

------------------------------------------------------------------------

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, {my email address} and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
Apache/2.0.51 (Fedora) Server at www.{mywebsite}.com Port 80

-------------------------------------------------------------------------

ok, so why does the main web site work and the admin panel won’t?????

I need to make a post, so this is urgent,

Thanks in advance for helping to get this fixed.

Jim.

I looked around on the web site and found an error log.  From looking at the time stamps, this appears to be the error that the server is recording.

[Sat May 03 13:44:08 2008] [error] [client {my ip address}] Premature end of script headers: php-script

and, from the config.php file AFTER the update, we have this line which I believe shows the update ran “successfully”

$conf[’app_version’] = “163”;

Now, I did notice that the next line for license number is blank,,,, could that be the issue?

BTW-----
I compared the “new” config.php to the old one, and there is a big difference.
The new one has just 51 lines, while the old one has 207

Hi, Jim,

Yes, the config file should be much shorter, as most of those values were moved into the database.

I’d recommend trying to re-upload you files, as it sounds like perhaps some file corruption from the transfer process.

Lisa,

Thanks for the reply, but that did not work.

I even re-downloaded the file, unzipped it, and tried a second time.

It is really odd how the weblogs will show up, and I can even view my user profile, but the control panel will not load.

So,,,,,, what’s next?

Searching around- it could possibly be a memory error.  What’s your php memory and any chance you can increase it to see if there’s any improvement?  If not- any other errors in the log that might give us a hint?  And double check file/folder permissions, see if anything looks odd there.

Robin,

Thanks for the reply.  I checked the error log and there is nothing in it to give a clue as to the problem, just the line that says:

[Sun May 04 07:12:53 2008] [error] [client {my ip address}] Premature end of script headers: php-script

I sent your comments to my web host tech support, because they are the ones that deal with the server memory, so I figured I would give them a chance to respond.

The issue is that I have a post that I MUST make today, and without a control panel I can not make that post.  Right now it is 9:30am CST.  If this issue is not fixed by 1pm CST I will have to rollback to my backup and restore the 1.5.2 version, and who knows when I will get another chance to try to upgrade it again.

Jim.

Hm- real quick, you could try uploading an htaccess file- or editing a current one- see if you can override memory that way:

That’s way high and should eliminate the possibility.  Assuming it’s allowed to override.

I edited the one in the root “html” directory,

Following this line: 
php_flag register_globals off

I added your line:
php_value memory_limit 64M

no change when I tried to access the control panel, same errors popped up, so either it is not a memory problem, or the line was not allowed to do anything.

I reverted back to the original .htacess file after this did not work.

Dang- I’ll bump to the crew for more ideas now.  If it’s a php error, I’d expect mention in the logs.  Bad/corrupt file via upload would also have been a good ‘first guess’- though I’d expect a php error in that case.  But Lisa already had you re-upload.  Should have caught anything odd there.

Do you have any extensions installed?  Wonder if something odd is going on there.

no extensions that I am aware of.

I will email you a couple of screen shots that show the configuration as shown in the web site admin panel.

Not seeing anything there that gives a hint.  Can you put:

In a text file- call it info.php or something- and upload.  Check the php memory that way.

I sent you the link to that page since it has so much info.

PS. I noticed that it said memory limit 8M, so I put the htaccess file back in the root with the line for memory limit of 64M.

It doesn’t look like that htaccess line is having any effect as the info still shows 8M.

I’d definitely get the php memory upped- say 32MB for a start.  Server guys should be able to do it no trouble.  Let’s see if that does the trick.

The good news.......

The web host informed me where the setting is at, and he went ahead and boosted it up to 64M.

Just took a look at the php info page,

memory_limit 64M 64M

----------------------------------------

Now the bad news..........

still no control panel, same results :(

since this is being worked on I am going to give it a little more time, but I am quickly running out of time and if we can’t get it fixed will need to rollback to the previous version I had on there.

well, I guess a Sun is not the best of days to try to resolve something like this.  I am out of time, so I will just rollback to the previous version.

I appreciate the effort that was put into trying to resolve this, I guess it just was not meant to be.

Dang- sorry Jim.  I still don’t know why you’d get that error- and no php errors- post upgrade.  And we know it isn’t a memory limit any more.

Next time you want to upgrade, what I’d do is create a second database- copy over the current one.  Upload the system folder for the new files but leave the old folder up and live.  Copy over needed files from ‘live’- including config.php- though tweak the config so it points sto the copied db.  Put up a renamed copy of index.php- indexnew.php or something- make sure the config reflects that.

Then run the update on the new db- using the new system folder.  Should be able to keep the old site running- and upgrade a copy.  If you run into the problem on the upgrade again- we can trouble shoot it again.  Without having to interrupt the live site.  Once it’s all good- easy enough to switch the upgrade into place.

Yell when you want to try it- we still haven’t got a good grasp on the server error, but I’m hoping one of the ‘big guns’ will spot it.

Thanks Robin,
I will post up when I get a chance and the time to try it again.