On production, the public filesystem is a network file share (which is slower). As lower environments, the filesystem is local disk (as the environments are not clustered) the access is a lot faster. The reason why this would occur on only production happens on Acquia typically when you need to read and write to the shared filesystem a lot. The error is not so much that the database server is not alive, more so that PHP's connection to the database has been severed due to exceeding MySQL's wait_timeout value. PDOStatement::execute(): Error reading result set's header ĭatabase.inc:2227PDOException: SQLSTATE: General error: 2006 MySQL server has On production we were experiencing the error during import: PDOStatement::execute(): MySQL server has gone away database.inc:2227 The failure was only on production, whilst the other (lower environments) the ingestion worked as expected.
There can be updates to the existing imported articles as well, but typically they are only updated the day the article is ingested.įeeds was working well for over a few years, and then all of a sudden, the ingests started to fail.
The feed perhaps ingests a couple of hundred articles per day. Background on the use of Feedsįeeds for this site is being used to ingest XML from a third party source (Reuters). This is a short story on an interesting problem we were having with the Feeds module and Feeds directory fetcher module in Drupal 7.
0 kommentar(er)
