Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello everyone
We started having a major issue after installing Entity 1.5 (from beta10) on Drupal 7.28
After downloading the module and running the update, we get the message shown on the attachement "Screen Shot 2014-05-20 at 2.15.08 PM.png"
After that, Drush does not work anymore and keep outputting the message "Segmentation fault"
Apache log was shows the following
[Tue May 20 22:33:53 2014] [notice] child pid 460 exit signal Segmentation fault (11)
[Tue May 20 22:34:00 2014] [notice] child pid 490 exit signal Segmentation fault (11)
[Tue May 20 22:34:03 2014] [notice] child pid 491 exit signal Segmentation fault (11)
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2014-05-20 at 2.15.08 PM.png | 14.82 KB | asiby |
Comments
Comment #1
Yorgg CreditAttribution: Yorgg commentedAre you sure its entity 1.5? I have copied a previous release back, cleared the caches but the issue remains the same.
Most parts of Drupal run but I can't create features or disable modules with drush dis.
Comment #2
damien_dd CreditAttribution: damien_dd commentedSame problem here:
Comment #3
damien_dd CreditAttribution: damien_dd commentedMore info about it.
ps: i've try again tryin to isolate the problem and still the same error.
Comment #4
damien_dd CreditAttribution: damien_dd commentedAlso crash on:
Comment #5
damien_dd CreditAttribution: damien_dd commentedOk, more infos about how and why.
So first try, i did this:
1.0-rc1 -> 1.0
It did not works.
I think this is because you need to update i18n module, in https://www.drupal.org/node/626176/release :
I did it, and i upgrade smoothly:
1.0-rc1 -> 1.0-rc2 -> 1.0-rc3 -> 1.0
And it works great.
Voila.
Comment #6
jnettikCan you clarify this a bit more? I've updated entity to 1.5 and i18n_translation is at 1.11 which is the most recent release. I'm still getting the same issue and I have both modules enabled.
Comment #7
TR CreditAttribution: TR commentedThis evidently doesn't affect many people, as there have been no other reports of this problem. It would be difficult for a module to do anything that could cause a segmentation fault - that most likely has something to do with your server resources. Anyway, closing this because there is not enough information to reproduce the problem.