Hi,

I got this error installing/updating modules in all my Drupal sites. I asked my hosting provider (knownhost) but they said it could be a Drupal bug.

Could you help me with this?

Exception: Invalid checksum for file "<?php /** * @file * Create (manually or scheduled) and restore backups of your Drupal MySQL * d" : 40903 calculated, 0 expected in Archive_Tar->_error() (line 635 of /home/xxxxxx/public_html/modules/system/system.tar.inc).

Comments

webchick’s picture

Category: bug » support

Moving to a support request. What module are you trying to install? What version of PHP? etc.

cweagans’s picture

Priority: Major » Normal

Support requests are never major or critical.

arne.skaanes@acm.org’s picture

I get the same error when trying to update on my Synology server, but not on my 1and1 account (also a linux system)!?
They are both running the same site and the same version of Drupal (7.14)
I assume there must be some parameters to either PHP or apache.
Are there any Drupal- geniuses that may find the missing resource from the error message:

Invalid checksum for file " /** * JavaScript behaviors for the front-end display of webforms. */ (function ($) { Drupal.beh" : 44679 calculated, 0 expected
Trying to update Wbform from 7.x-3.17 to 7.x-3.18

It is not a critical problem, but it would be very timesaving to have it work when updating customers sites.

Nick Brown’s picture

I'm seeing the same issue when attempting to install or update modules. Running drupal 7.14 on a synology DS212+ running DSM 4.0. I can provide php/apache configuration information it wil help with determining the cause of the problem.

This might be related http://drupal.org/node/1475914

Version: 7.12 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.