Thread

This question is related to a resolved thread.

I’ve put off upgrading this site because the last time didn’t go smoothly, but I could procrastinate no longer 😉

Unfortunately I’m experiencing that same situation as last time. 

I have other EE sites that upgrade without issue, not sure what’s so special about this site.  Anyways, sure would appreciate your help in sorting it out again.

cheers!
Jules

Hello JulesWebb,

Thank you for posting your question here on the ExpressionEngine forums.

Can you tell me a bit more about your situation? Paste in some errors? You marked this thread as similar to the other, but not sure if your are getting the same errors or not.

Thank you,

Can you tell me a bit more about your situation? Paste in some errors? You marked this thread as similar to the other, but not sure if your are getting the same errors or not.

Sorry I wasn’t clear enough. This is the same as the previous upgrade. The only difference is the error states 2.3.1 instead of 2.2.1

Please Stand By…
We are currently updating your ExpressionEngine installation.
Do not close your browser until the update routine is finished.
2.3.1

Hey JulesWebb,

Understood.

So you are stuck at the screen of waiting. Not fun.

Are you pretty comfortable with a command line? If I asked you to snoop through some logs, would you be okay with that? If not, can I ask you to request a few things from your hosting provider?

Typically, at least in my experience, when we sit at this screen for a long time there is some php errors that we are not being shown. Those tend to show up in access and/or error logs.

I would also love to know what version your install thinks it’s at. Can you look in the config.php file and see what version has been written to the file? As each update step completes, we write the version to that file. The last step completed ... that would be good to know.

Please let me know!

Cheers,

HI Shane

Are you pretty comfortable with a command line? If I asked you to snoop through some logs, would you be okay with that? If not, can I ask you to request a few things from your hosting provider?

Comfortable, well I don’t find it uncomfortable—-just realize I don’t know what I’m doing.  If you tell me where and what I will be happy to snoop;) Snoop to learn sounds good to me, lead on!

I would also love to know what version your install thinks it’s at. Can you look in the config.php file and see what version has been written to the file?

$config['app_version'] = "231";

Typically, at least in my experience, when we sit at this screen for a long time there is some php errors that we are not being shown. Those tend to show up in access and/or error logs.

Where do I look?

Hello JulesWebb,

It sounds like the update finished. Can you rename the installer folder and try to load up the Control Panel?

On the command line looking for something like this, depending on distro.

tail -f /var/log/apache/access /var/log/apache/error

While those are being tailed you could refresh that page to see what comes through.

To see those PHP errors you will enable debug.

Thank you,

I’m confused, the current version is 2.5.2 not 2.3.1

On the command line looking for something like this, depending on distro.

where do I go to look for this command line?

It sounds like the update finished. Can you rename the installer folder and try to load up the Control Panel?

OK, below are my results.

Parse error: syntax error, unexpected $end in /home/username/public_html/admin.php on line 82

/* admin.php file
 * --------------------------------------------------------------------
 *  Mandatory config overrides
 * --------------------------------------------------------------------
 */

               $assign_to_config['subclass_prefix'] = 'EE_';
               $assign_to_config['directory_trigger'] = 'D'; 
               $assign_to_config['controller_trigger'] = 'C'; 
line 82        $assign_to_config['function_trigger'] = 'M';

Hi Jules,

Right, 2.5.2 is the desired goal so 2.3.1 is wrong. I thought the debug would show us why we are getting hung up at 2.3.1.

I would roll back and do the update again.

Can you tell me how big your Database is?

Thank you,

Hi Shane

I restored the previous files and database tested that the site was functioning correctly and attempted another upgrade.  this time I’m only making it to 2.3.1

Please Stand By…
We are currently updating your ExpressionEngine installation.
Do not close your browser until the update routine is finished.
2.3.1

Can you tell me how big your Database is?

7.178 MB

I use an above the root install. I have tried upgrading from there and the traditional installation. Either way I get the same response.

When I revert my database I use the PHPmyadmin interface and drop all tables from the database and then import the backup copy. This method works for every other site I’ve upgraded.

I’m not getting any errors, or at least I’m not seeing any.

I’ve been following the intruction @ http://ellislab.com/expressionengine/user-guide/installation/update.html

I don’t see anything http://expressionengine.com/wiki/Troubleshooting_Upgrade_Errors that is relevant, though I realize I could unknowingly be 😉

Not sure what to try next, what do you suggest?

Hi JulesWebb,

Okay. I thought it might be triggering a large database upgrade, but you are no where near 150MB.

A couple of ideas.

Did you run the Server Wizard to make sure this server is compatible?

Did you have run the tail on the web logs to see what error is being thrown at that stage of the process?

I am sorry this has been such a pain!

I will be awaiting your reply.

Cheers,

Did you run the Server Wizard to make sure this server is compatible?

The server is compatible, it’s the same hosting service and setup I have my other EE sites on.

Did you have run the tail on the web logs to see what error is being thrown at that stage of the process?

Can you tell me how to do this?

Is it possible to find out how the issue was resolved last time? Someone from EE logged in and did the update for me, would there be any notes from that incident?

Hey JulesWebb,

I looked up your email and I did not see any other cases. Did you file a case with us using the same address?

Tail the logs on the command line with:

tail -f /var/log/apache/access /var/log/apache/error

Thank you,

Hi Shane

Below is the subject line from my support emails last year pertaining to the http://ellislab.com/forums/viewthread/193175/ thread

subject:“WebbDiva’s Technical Support Login Details {54573}”

Tail the logs on the command line with:

I don’t have root access to run this command. Is this something that I can request my hosting provider run?