By BAlGaInTl on

I'm trying to upgrade my Drupal install from 7.30 to 7.32.

The upgrade seems to go well, but then when testing, the Dashboard and Content admin areas will not load. Other sections of the Admin area are loading just fine.

Any thoughts as to what could be causing this?

Thanks

Comments

John_B’s picture

John_B commented

Clear all caches. If it still does not work, look in the Apache error log for the most recent entries after trying to load those pages. The answer is probably there. There may also be something under Drupal's Reports > Recent Log Messages.

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

BAlGaInTl’s picture

BAlGaInTl commented

I've cleared the cache, and I have the same issue.

There is nothing that stands out in the Apache or Drupal logs. I'm not getting any new entries when I try to load either Dashboard or Content.

I've also tried different browsers.

I'm really at a loss here.

John_B’s picture

John_B commented

Do you maybe use an opcode cache which could be playing up? If possible, just restart Apache (and if you are using it, php fpm), then try to reload the missing pages?

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

BAlGaInTl’s picture

BAlGaInTl commented

I restarted apache a couple times...

Finally, I noticed that Dashboard was loading...

After loading content multiple times, and waiting, allowing it to time out several times, it is now loading as well.

Is it possible that I had to rebuild some type of cache that took so long the first time?

Anyway, the issue is solved for now, but I still don't know what the root cause was.

John_B’s picture

John_B commented

If you are using the native Drupal database cache backend, it is normally rebuilt immediately on a cache clear, with the proviso that certain tables (e.g. cache_bootstrap I think) do not get rebuilt by the 'Clear All Caches' button. In other words, I doubt it on a vanilla Apache + Drupal setup. On the other hand if you have an opcache, or if you have an object cache such as Memcache on the server, or other non-standard cache backends defined for Drupal, or a mis-configured HTML (e.g. Varnish) cache, any of these these can certainly be more problematic, and restarting services does not always clear cached data out of the server's memory, as it should, in my experience. You may even get logged-in pages reloaded by some browsers which have over-aggressive browser caching. Provided all your code is there, and there are no error messages in a working error log, there is a caching problem somewhere along the line, though sometimes it can be elusive finding where.

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