Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
By vladimirkomarek on
hello i have drupal 7.41
when i try to download and update modules from the reports/update page
after the progress bar start ii keep receiving this error:
"An error has occurred.
Please continue to the error page
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?render=overlay&id=809&op=do StatusText: error ResponseText:"
if i click "continue to the error page" i have this: "Fatal error trying to download."
so it doesnt let me update automatically the modules
do yoiu think i can fix this?
thanks
Comments
ps. in log
i have this:
"PDOException: in statistics_exit() (line 93 of /public_html/modules/statistics/statistics.module)."
=-=
pasting the above PDOException into google leads to https://www.drupal.org/node/1906626
ok found the solution
The issue is that the file modules/system/system.tar.inc is getting deleted on upload by your hosting provider's virus checker, due to the presence of the symlnk function in that script.
The solution is to raise a support ticket with your hosting provider to ask them to whitelist system.tar.inc, explaining that this file uses symlnk as part of the latest Drupal core files.
The workaround is to edit the file to comment out the code containing symlnk (or just change symlnk to something else such as sym3ln3k as suggested elsewhere). This will get updates working again, though it will fail if that small bit of code is ever executed.
thanks everyone
Hi,
Hi,
In Drupal 7, two methods are used to fetch update information. One uses a setting "update_max_fetch_time" which is set to 5 seconds by default. On each cron run - whether from the server's cron or triggered by a visitor - or page refresh of admin/reports/updates, this value is used. Not every module's status can be fetched within those 5 seconds.
If you use the 'Check manually' link from the 'Available updates' page (admin/reports/updates/check), a batch operation is used instead, which should process all modules. There are however also reports that this doesn't always work correctly (Failed to get available update data for [xx] projects message, you would then see the status of some modules in a grey box). You may also have to clear Drupal's cache first for this to work correctly.
The best thing to do is probably to set up a cron job to run each hour (for example). This will progressively keep the status of all modules updated.
Another workaround would be to override the "update_max_fetch_time" value and set it to e.g. 30 seconds (Drush method: drush vset update_max_fetch_time 30). But if a cron run is then triggered, this could lead to a long page loading time.
Thanks
Studiographene
well
i don't think this is related to my kind of problem
is it?
ok
fixed it:
The issue is that the file modules/system/system.tar.inc is getting deleted on upload by your hosting provider's virus checker, due to the presence of the symlnk function in that script.
The solution is to raise a support ticket with your hosting provider to ask them to whitelist system.tar.inc, explaining that this file uses symlnk as part of the latest Drupal core files.
The workaround is to edit the file to comment out the code containing symlnk (or just change symlnk to something else such as sym3ln3k as suggested elsewhere). This will get updates working again, though it will fail if that small bit of code is ever executed.
Dude thanks a lot for this
Dude thanks a lot for this idea (Y) i solved my problem by changing the symlink to ( Sym3lin3k ) and every thing is good now
i can updating normally with out error
really thanks ;)