"There was a problem checking available updates ..." for Drupal, modules or themes

This issue does not seem to be related to the functionality of this module. Therefore, closing this issue. See http://drupal.org/support for support channels.

Feel free to re-open this issue if I'm mistaken. Thanks.

I get this issue too.

I have this issue with D7.4 now, did you guys find any answer, please

Similar problem with Windows XP, Apache, Drupal 7x. I am moving the thread from 'Administration menu' to here, core/update.module.

Let's start from the beginning: Administration > Modules page gives warning message "No update information available. Run cron or check manually."

• run cron (.../?q=admin/reports/status/run-cron&destination=admin/modules): cron runs, returns to admin/modules page, displays "Cron ran successfully." but also beneath that the warning messages "There was a problem checking available updates [that is the link to .../?q=admin/reports/updates] for Drupal. See the available updates [link to .../?q=admin/reports/updates/update] page for more information and to install your missing updates.
• q=admin/reports/updates and q=admin/reports/updates/update both: blank page (probably will not help much but attached are their html sources)
• check manually (.../?q=batch&op=start&id=8): Get the page with "Checking available update data" and the progress bar, "Initializing.", waits too long, and hangs.

Any idea or solution?
How can I help the coders to debug or trace?

Upgraded to 7.10, still facing the same problem.

I get this error too on almost every site I install. Use 7.10 version right now. Very annoying! I want to be sure everything is up to date before delivering a site to a client.

I am also getting this error and have been with every version of Drupal 7 I've installed. This error happened before I installed any extra modules and continues to happen no matter what I do. There are no error reports other than the message at the top of the page saying it was unable to find updates.

When I run cron manually, it still says that it can't find available updates and offers for me to check manually. When I do, it says it "Failed to find updates for 14 projects"

Possibly check any folder permission in your public_html folder or the like. :)

I've always had this problem too on my Windows 7 (ultimate 64bit) machine too with D7. I don't seem to get any problems on my unix servers managing the same sites though.

It is a problem, as diagnosing an error following a recent update of 17 modules (which crashed out with "Fatal error: Maximum execution time of 60 seconds exceeded in C:\xampp\htdocs\peachy\includes\database\database.inc on line 2139") is now a pain the backside. If I clear the cache, rebuild permissions, close the browser/wait 5 minutes or whatever then click on admin/modules/update I get a random list of modules (out of the 17) that still need upgrading or none at all bar the message "All of your projects are up to date" which I know is untrue.

@lesseen; could you (or anyone else please) elaborate on what you mean by "check any folder permission in your public_html folder or the like". What are we checking for and what else might be "or the like"?

Nailing this would be great - and great for Drupal! :)

I've checked my folder permissions and that didn't help. To do that, you can either right click on the folders in your ftp directory then select permissions, or you can do the same within your control panel with the host. My permissions are set to full read/write/executable and still the problem exists.

What does your status page tell you? :)

Hi leseen, sorry, I've been away for a week. I get admin notice message stating:

"One or more problems were detected with your Drupal installation. Check the status report for more information."

On my admin/reports/status page itself there are various messages which can not be correct too:

***
"Drupal core update status - No available releases found" whereas Drupal 7.15 has just released.
"Module and theme update status - No available releases found"
"There was a problem checking available updates for your modules or themes. See the available updates page for more information and to install your missing updates."
***

On my admin/reports/updates page I get a long list (roughly 80% of the total) stating, for example;

"backup_migrate 7.x-2.4 - No available releases found"

See grab attached.

On my dev server (unix) the exact same site (db and code) works fine.

Q

sounds good:) ok hit this right of the top, http://example.com/admin/reports/status this is the default exit page after running 'cron' as well.

This seems to be a server side hosting config issue possible:)

Not sure,

Also one note:/ is your cron failing? Also check your http://example.com/admin/reports/dblog (log)

I was having the exact same issues in a multi-site setup. I changed my temporary directory (/admin/config/media/file-system) from '/tmp' to 'tmp'. Problem went away.

I am seeing this since updating from 7.15 to 7.16. Prior to that, there were no problems.
Manual check on available updates shows that everything is up to date.

I also had this problem with a new install of 7.16. Following rwilson0429's advice to change the temporary directory from /tmp to tmp solved the problem. Quite how rwilson0429 discovered this is another matter.

If you have custom modules or features, that will cause this to happen. You can fix it using one of the two methods here:

www.pixelite.co.nz/article/remove-custom-drupal-modules-and-themes-updat...

For what it is worth... I had a site with over a hundred modules, but only ~6 contrib modules had available update information, all the other contrib modules just said "No available releases found". I tried many things but eventually discovered that I could resolve the issue by truncating the cache_update table that seemed to have been corrupted or stale.

Drush sqlq "truncate cache_update;"

This is also referenced as a solution here

It seems that upgrade Drupal core to 7.51 removes this bug. Please confirm.

#19 worked for me with Drupal 7.56
Thanks @dooug !

#19 IS the solution!

Patch #19 looks good to me. Its works fine. Thanks @dooug.