After uploading the new files calling update.php i got following message:

Ein AJAX-HTTP-Fehler ist aufgetreten.
HTTP-Rückgabe-Code: 500
Im Folgenden finden Sie Debugging-Informationen.
Pfad: /update.php/start?id=197&op=do_nojs&op=do
Statustext: Internal Server Error
Antworttext:

The link to the error message doesnt work: i got only a blank page

Follogwing amin-pages didnt work:
/admin/config
/admin/reports/status
/admin/modules/uninstall

Uploading old version didnt work fully, because admin pages still dont work and if i call update.php there is still the outstanding update which caused the problem

image module

Saves the image style dependencies into form and view display entities.

On D8.0.1-2 i still faced some problem with modul in dev status, resulting in

"Entity/field definitions Mismatched entity and/or field definitions "

Content: Delete the URL-Alias field.
Taxonomy term: Delete the URL-Alias field.

(means that, that i have to delete these fields? how?)

What can i do to save my work, unfortunately it was a pordution site.

On my blank test site the update seemed to work well. No such problems fount ...

Comments

John_B’s picture

If you have backup, restore it. I assume you do not.

In this situation my first step would be to ensure you have drush on the server, because it makes things easier. Without it, one is pretty helpless. (Obviously you need the version of drush which supports D8, that is drush version 8). Then run a cache rebuild
drush cr
and watch for any messages.
Then I would put back the updated code with drush up.
Run
drush up
and see what happens.

Then take a look at the database log, if you have it enabled. Should be at reports > recent messages: if that page does not work, again you can use drush to read it,
drush watchdog-show
If you cannot find the error there, take a look at the server error log for the time when the error occurred.

As it is a production site you might want to take a copy of the site and work on that rather than working live. These steps are not likely to make the situation worse, but they might! In addition, I suspect the server was just not responsive enough to handle the update.

Viel Glück, aus Innsbruck.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

MartinMa’s picture

I have backuped before updating and have some older backups, but strange enough they dont work too ...

I dont have drush on my server. its a resseller system and support is not really good ...

John_B’s picture

Very tough working on Drupal without drush. Maybe take a copy onto a laptop or development server where you can have drush, and sort it out there.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

MartinMa’s picture

I installed drush with composer, but can't call drush ...

/usr/local/php5.5/bin/php ../bin/composer.phar global self-update

Changed current directory to /medjxcwh/.composer
Warning: This development build of composer is over 60 days old. It is recommended to update it by running "../bin/composer.phar self-update" to get the latest version. [just have done this]
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Removing pear/console_table (1.2.1)
- Installing pear/console_table (v1.3.0)
Downloading: 100%

- Removing symfony/process (v2.7.6)
- Installing symfony/process (v2.8.2)
Downloading: 100%

- Removing symfony/event-dispatcher (v2.7.6)
- Installing symfony/event-dispatcher (v2.8.2)
Downloading: 100%
......

- Updating drush/drush dev-master (37f051d => c0212b2)
Checking out c0212b2ea665ca8add4b0e337f6055a8572cf4f2

Writing lock file
Generating autoload files

but

:~/drupal.mediaweb.at > drush cr
-shell: drush: command not found

I dont know were drush was installed and how to use it ...

MartinMa’s picture

If I dont use the "global" argument, an older version is installed (just why?). And more strange: ctools and token deleted (token is used by pathauto)

~/drupal.mediaweb.at > /usr/local/php5.5/bin/php ../bin/composer.phar require drush/drush:dev-master
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Deleting modules/ctools/ - deleted
Deleting modules/token/ - deleted
- Removing composer/installers (v1.0.23)
- Installing composer/installers (v1.0.21)
Downloading: 100%
......
> Drupal\Core\Composer\Composer::vendorTestCodeCleanup
- Installing drush/drush (dev-master c0212b2)
Cloning c0212b2ea665ca8add4b0e337f6055a8572cf4f2

Removing token causes following problem (when i call update.php)

The website encountered an unexpected error. Please try again later.
Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "pathauto.generator" has a dependency on a non-existent service "token.entity_mapper". in Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processReferences() (line 58 of /medjxcwh/drupal.mediaweb.at/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php).

John_B’s picture

It is telling you that you need token because you do not have token, which pathauto depends on.

Removing token causes following problem

It should not have been possibly to uninstall token while pathauto is still installed. This is strange.

Perhaps you just deleted token without uninstalling it in the normal way? Simply deleting a module without correctly disabling (< drupal 8) or uninstalling (drupal 8) is a quick way to break a site. In that case, the first thing to do is put back a fresh copy of the code you deleted. After that you can work out what to do next.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

MartinMa’s picture

I reolved THIS.

But whatever I do, the problems of my first post sty, also if i restore from an older backup ... so its not the dateabase ... seems to be more a problem with composer and the libraries ...

Running composer drupal-update there is always one problem:

Drupal\Core\Composer\Composer::vendorTestCodeCleanup
- Updating jcalderonzumba/gastonjs dev-master (5e231b4 => 21bebb8)

[RuntimeException]
The .git directory is missing from /medjxcwh/drupal.mediaweb.at/vendor/jc
alderonzumba/gastonjs, see https://getcomposer.org/commit-deps for more i
nformation

John_B’s picture

In fact drush should not be inside your document root, and there is no reason to composer drupal-update inside doc root (or at all) AFAIK. Once drush is working just run drush up to update the site.

If you still want to debug that message, I wonder, did you build the site? If not, you should speak to the person who built the site. There is a suggested workaround here http://stackoverflow.com/questions/21012061/composer-error-while-updatin... but it should not be needed.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors