Upgrade - error 500

Hi,

I just upgraded from 7.7 to 7.9
I get an error 500


/var/www/web95 # tail ../log/error.log 
#1 /var/www/web95/web/include/SugarTheme/SugarTheme.php(1268): SugarThemeRegistry::buildRegistry()
#2 /var/www/web95/web/include/language/en_us.lang.php(1202): SugarThemeRegistry::current()
#3 /var/www/web95/web/include/utils.php(1056): include('/var/www/client...')
#4 /var/www/web95/web/include/MVC/SugarApplication.php(357): return_application_language('fr_FR')
#5 /var/www/web95/web/include/entryPoint.php(170): SugarApplication::preLoadLanguages()
#6 /var/www/web95/web/index.php(47): require_once('/var/www/client...')
#7 {main}
  thrown in /var/www/web95/web/include/utils.php on line 1687
PHP message: PHP Stack trace:
PHP message: PHP   1. newrelic_exception_handler() UNKNOWN?:0" while reading response header from upstream, client: 176.181.224.41, server: crm.swap42.com, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/lib/php5-fpm/web95.sock:", host: "crm.swap42.com"

Seems like a newrelic issue - but I don’t remember setting up newrelic in there…
Anyone’s got an idea?

Even a small idea is welcome :slight_smile:

Tell us your versions of OS, database, web server, PHP - you should always start with that.

Then please check your other logs, especially upgradeWizard.log.

You get the error 500 when upgrading, or you get it all the time, after the failed upgrade?

Sorry
So here it is for environnemental things:


# uname -a
Linux  3.2.0-4-amd64 #1 SMP Debian 3.2.88-1 x86_64 GNU/Linux

Running with Nginx.
Nginx version: nginx/1.6.2

PHP 5.6.30-1~dotdeb+7.1 (cli) (built: Jan 21 2017 14:50:59)

Regarding other logs: suitecrm.log


Fri Jun 16 01:28:35 2017 [23925][9cca72e0-613d-b60f-469e-574c4df2d182][FATAL] pre_install
Fri Jun 16 01:29:08 2017 [23925][9cca72e0-613d-b60f-469e-574c4df2d182][FATAL] Exception in Controller: No valid themes are found on this instance

Side note : seems to me to issue - I made some modifications in the theme at the first install last year - but since I have already upgraded once and there was no issues - but I don’t know how to check this now.

And UpgradeWizard


Fri, 16 Jun 2017 01:28:40 +0300 [UpgradeWizard] - *** ERROR: Schema change script [/var/www/clients/client1/web95/web/cache/upgrades/temp/Nh0i76/scripts/65x_to__mysql.sql] could not be found!

...

Fri, 16 Jun 2017 01:28:43 +0300 [UpgradeWizard] - At updateVersions()... updating config table and sugar_version.php.
Fri, 16 Jun 2017 01:28:43 +0300 [UpgradeWizard] - *** ERROR: no sugar_version.php file location found! - cannot complete upgrade...

Ok… I don’t know…

Ok, we’re making progress.

Check config.php and config_override.php to see if you disabled SuiteP theme there. Re-enable it, otherwise 7.9 will never be able to install, it’s the only theme for that version.

Check if you have a file called sugar_version.php in your SuiteCRM root directory. Check if has appropriate ownership and permissions to be writeable.

This is what the contents of that file should look like on 7.7:
https://github.com/salesagility/SuiteCRM/blob/7.7.x/sugar_version.php

1 Like

Awesome!
:woohoo:

Working.
I restored the SuiteP theme and we’re up and running.

Thanks!

Great to hear that!

Can you please describe exactly what those entries looked like in your config.php and config_override.php? Where did you get that information from, about how to disable themes?

I can’t seem to find it but I’m thinking of opening an Issue with this, it seems more people are having your problem and at least a better error message should be given to the user…

As far as I remembered, I have disabled them using the web interface.
And if I properly remember I disabled them because I could not get the SuiteR theme I had selected to actually activate - so I basically disabled everything else.

(On a side note - current SuiteP is all over the place, I might have some residual CSS left somewhere - don’t see any other explanation…)

Try a quick repair and rebuild.

Then if the problem persists check your permissions on the files.

On tougher cases you might have manually clear some of the cache folder.

1 Like

fixed it!
thx :slight_smile: