I had resisted updating to the newest 8.x-3.x-dev commit for Libraries API because doing so causes the following error in the subsequent run of update.php:
Fatal error: require(): Failed opening required '/srv/bindings/***/code/modules/libraries/src/LibrariesServiceProvider.php' (include_path='.:/usr/share/pear:/usr/share/php') in /srv/bindings/21809783268e4af9b26f5a512b669115/code/vendor/symfony/class-loader/ApcClassLoader.php on line 110
The PHP error is:
[12-Oct-2017 15:55:10 UTC] PHP Fatal error: require(): Failed opening required '/srv/bindings/***/code/modules/libraries/src/LibrariesServiceProvider.php' (include_path='.:/usr/share/pear:/usr/share/php') in /srv/bindings/21809783268e4af9b26f5a512b669115/code/vendor/symfony/class-loader/ApcClassLoader.php on line 110
I am not sure why update.php is trying to access LibrariesServiceProvider.php, as that was removed in the current 8.x-3.x-dev that I tried updating to.
I can navigate away from the crashed update.php and back to my site, and it appears to be working, but then clearing the cache from the Drupal interface causes the same Fatal Error as above. I am able to clear the cache using drush, but it too throws a warning:
$ drush @pantheon.<MY-SITE> cr
PTY allocation request failed on channel 0
Cache rebuild complete. [ok]
But, even after doing so, the issues still persist with clearing cache from the Drupal interface and running update.php. So, this problem is preventing me from clearing cache or running any other updates.
This problem is now coming back to bite me, since the 8.x-3.x-dev (2016-Nov-13) commit is incompatible with the newest Drupal core release 8.4.0 (see #2915603). My inspection suggests that the newest 8.x-3.x-dev commit will work with 8.4.0, but I can't test it now because of this problem.
---------------------------------
EDIT: looks like this is related to: https://www.drupal.org/node/2851302
Comments
Comment #2
xem8vfdh commentedComment #3
xem8vfdh commentedComment #4
xem8vfdh commentedComment #5
xem8vfdh commentedComment #6
xem8vfdh commentedComment #7
xem8vfdh commentedComment #8
xem8vfdh commentedComment #9
xem8vfdh commentedComment #10
xem8vfdh commentedthe suggested solution here of simply running a full cache rebuild does not work for me. The drush cr ultimately completes and succeeds, but the problem persists. Trying to see if Pantheon can restart the container.
Comment #11
xem8vfdh commentedOnce Pantheon restarted the nginx server, the issue was resolved.
Comment #12
xem8vfdh commented