Backups were saved into the directory /root/drush-backups/foo/20120406165612/modules/entity.                                   [ok]
The command could not be executed successfully (returned: Segmentation fault                                                          [error]
, code: <em class="placeholder">139</em>)

Comments

hass’s picture

Just run "drush up" if the DEV is outdated.

e2thex’s picture

it appear to happen in
http://drupalcode.org/project/entity.git/commit/654876282fecaf669e4e2152...
or at least that is what git bisect said

carn1x’s picture

Upgraded from 7.x-1.0-rc1 to latest dev (7.x-1.0-rc1+46-dev).

Site WSODs, and "drush cc all" gives:

$ drush cc all
Segmentation fault

"drush up" does nothing.

carn1x’s picture

As fago mentioned in another queue, I had to update entity AND i18n to new dev, which gets rid of the segfault.

See: #1447946: Recent entity API dev version requires a recent i18n dev version

hass’s picture

As E comes before I - the next update will WSOD thousands of sites and bring them offline. Entity API need to workaround for sure if this is really the readon. A system down is not acceptable. I know the sites I've updated had i18n installed, but it took me hours to discover Entity API as root cause.

iamEAP’s picture

This potentially affects people using non-dev modules. The latest Field Collection beta (4) relies on this dev version of Entity API.

If they happend to be using i18n as well, and not the latest dev, they'll experience this.

Also relevant: #1530018: Create a new stable release 7.x-1.5

Ace Cooper’s picture

Had the same problem, bashing my head for several hours.
Turned out that i18n was at fault. As soon as I updated to i18n-1.7 the "Segmentation fault" error went away (woohoo!).
Thank you, iamEAP.

tuwebo’s picture

#7 worked for me too.
Thanks Ace Cooper

martinbo’s picture

Thanks Ace Cooper and iamEAP, it really helped me!!

andrea.cavattoni’s picture

#7 works form me

slown’s picture

#7 worked for me too. Yeepah! Thx A Lot

alexander allen’s picture

Status: Active » Closed (fixed)

Marking as closed since various users reported the bug as fixed more than a year ago.

alexander allen’s picture

Status: Closed (fixed) » Fixed

Fixed status.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.