Can't edit rules due to internal server error since 7.x-2.0-rc1

I am having the same problem.

I got everything set up locally and it worked fine, but once it was online I got the 500 error when I tried to edit the rules.

The problem is inconsistent though. At first I was able to edit some of the rules, but not others. So I deleted a "bad" rule and remade it and then I could edit it. When I tried to change the order of the conditions, it broke again.

When I gave up last night I wasn't able to edit any of the rules. When I sat down this morning, I could edit all of them ... until I tried making changes.

I was still trying to ascertain if the problem was with my transfer to the web, my web host, the Rules module or some other update, so thanks for posting this temporary solution mstrelan. With the beta version in place everything seems rock solid again.

I tried installing RC1 yesterday and was unable to do much.

Setting up a simple Rule with just an Event and a Condition, then trying to Edit it, would time out. No visible error message, simply a blank page.

Reverting to the last Beta 3 seems to work for me, thanks!

http://drupal.org/node/190124/release

Same here, subscribe

I confirm the same problem.

same issue here, any help will be much appreciated...

Subscribing.

same here

will there be a release with a fix?

Same problem here with a fresh install of Drupal 7.7 with Entity API 7.x-1.x-dev or 7.x-1.0-beta10, when trying to add a condition to a rule I get a

502 Bad Gateway

I'm on a Barracuda server. When downgrading to rules 7.x-2.0-beta3 evrything works fine.

Having the same issue. (But my server was give HTTP Error 500)

Downgrading as #9 also worked for me.

Nasty little knock on for me was the core.xxxxxx files were being created and store under public_html - these crippled the site.
(Something to watch out for if you are getting this problem...)

Two of the rules causing the problem...

{ "rules_redirect_to_regisrtation_page_wh" : {
    "LABEL" : "Redirect to regisrtation page when creating content",
    "PLUGIN" : "reaction rule",
    "ACTIVE" : false,
    "REQUIRES" : [ "rules" ],
    "ON" : [ "node_insert" ],
    "IF" : [
      { "user_has_role" : {
          "account" : [ "site:current-user" ],
          "roles" : { "value" : { "1" : "1", "2" : "2", "4" : "4", "5" : "5" } },
          "operation" : "OR"
        }
      }
    ],
    "DO" : [ { "redirect" : { "url" : "user" } } ]
  }
}

and

{ "rules_put_nid_into_field_download_code" : {
    "LABEL" : "Put NID into Field Download Code",
    "PLUGIN" : "reaction rule",
    "REQUIRES" : [ "rules" ],
    "ON" : [ "node_insert" ],
    "IF" : [
      { "node_is_of_type" : {
          "node" : [ "node" ],
          "type" : { "value" : { "mobile_friendly_page" : "mobile_friendly_page" } }
        }
      }
    ],
    "DO" : []
  }
}

I'm having the same issue with 7.x-2.0-rc1. :(

If I save a new rule after saving a node or before saving a node: Everything is fine. If I add a condition of content is type, I get the internal server error message after saving.

If I update to the dev version with fresh dev files (no updates seem required when calling update.php either), same issue.

Thanks for the assist in advance. :)

Subscribing

Subscribe

The same issue with the last 7.x-2.x-dev release. It only works with the last Beta 3...

sub

I'm getting this too, my server says "502 Bad Gateway" when trying to edit a rule. Sept 8th dev version.

I reported this issue as a 502 error in the Barracuda queue, but it looks like it's not a BOA-specific thing at this point. sub.

Same here, using 7.x-2.0-rc1. Only happens on the remote server. I haven't been able to get a look at the log (if any) yet to be able to provide more details. Will post it if/when I'm able to gt that extra information.

I'm also going to try my first git bisect, I'll post back if I can get anything meaningful out of that. The pain is, it only happens on the remote server...

subscribe

sub

Subcribe. 502 when trying to edit a rule.

subscribe

Small update, the 502-error was there initially, but disappeared a little later. And now it seems to work fine. Strange behavior.

Keep an eye out. The next time you run drush cc all, it will likely come back; that's been my experience anyway.

worked for me as well, is it something to do with only Logintabogan rules causing this error?

adding tag

#10 notes that core dumps were created, so this is probably the same as #1205834: Segmentation Fault

Presuming these reports are all segfaults, they may only occur in specific versions of PHP.

I've tried to reproduce this with the rule-exports provided, but so far no luck! :(

So looks like the error depends on a certain environment. Could you please provide the PHP and Drupal version you are experiencing the issue with? Then, please test whether the error applies to a clean install only having entity+rules installed.

Also, what are exact steps to reproduce?
- Create new rule
- Add condition
- That's it?

Thanks!

Also, please report if you are using any PHP extensions (apc, xdebug, ..)

System info for #10 - Cheers!

Apache version 2.2.17
PHP version 5.2.17
MySQL version 5.1.56
Architecture x86_64
Operating system linux
Shared IP Address 175.107.146.137
Path to sendmail /usr/sbin/sendmail
Path to Perl /usr/bin/perl
Perl version 5.8.8

mh86 was able to reproduce it on his local development environment and helped to identify the source (thanks!)

It seems that a simple method_exists() check triggers a PHP bug, probably another incarnation of https://bugs.php.net/bug.php?id=51425

Please try whether removing the check fixes the problem (see patch attached).

@fago - would it help if someone was able to PM you access to their server? Unfortunately I'm not able to for the sites that servers I have access to, but somebody else may be able to.

Thanks, but looks like we found the source already :)

seconded, 32 worked for me

I confirm, #32 worked for me.

#32 seems to have solved the problem for me, as well. Thanks!

ok, I've added a comment to it and committed #32.

In case anyone thinks they are still having this error after the fix committed above, make sure to check an issue with Entity that is easily confusable with this one: #1518062: Latest DEV cause segmentation fault in drush.

Updated component.

I had the same problem. Couldn't edit or clone and rule that had a redirect in it. I was using Rules 7.x-2.6. I went back to rules 7.x-2.0-beta3 and all is well.

I was getting an Internal Server Error when trying to add a condition for an Ubercart action (customer completes checkout). I wanted to add a condition that the order included a specific product. I would get the error UNLESS I first included a "Entity Includes Field" condition.

Hope this helps someone.

@mctwist #43: Can you clarify what you entered for Entity and Field? I'm a little confused by the "Entity has Field" screen.

Thanks!

I had the same problem. I was using Rules 7.x-2.6.

When I am trying to edit the following rule , I get Segmentation Fault.

The configuration in which the problem is occurring is:
Drupal core : 7.31
Rules : 2.7
Php Version : 5.2.6

When the rules module is reverted to version rules-2.0-beta3, I am able to edit the rules.

Rule :
 "rules_testrule3" : {
    "LABEL" : "testrule3",
    "PLUGIN" : "reaction rule",
    "OWNER" : "rules",
    "REQUIRES" : [ "rules", "comment" ],
    "ON" : { "comment_view--comment_node_ads" : { "bundle" : "comment_node_ads" } },
    "IF" : [
      { "text_matches" : { "text" : [ "comment:subject" ], "match" : "YYY" } },
      { "text_matches" : { "text" : [ "comment:subject" ], "match" : "YYY" } },
      { "text_matches" : { "text" : [ "comment:subject" ], "match" : "YYY" } }
    ],
    "DO" : [  ]
  }
}

Seems a number of people are experiencing an issue here.

After upgrading the rules module to 7.x-2.x-dev development version (PHP version 5.2.6, Drupal Core 7.31), I am able to edit the existing rules. I am also able to specify multiple OR conditions in a single rule and everything is working fine. So it looks like the current development version fixes this issue.

i couldn't trace the exact problem, but i suspect that it may be something about PHP 5.2 vs later versions. Rules 2.7 works without problems on a system running PHP 5.3, but on the PHP 5.2 system, it dies trying to call the buildContent() method on a RulesAbstractPluginUI object.

installing 2.x-dev fixes the problem for me as well.

disabling Extendable Object Faces API module solved it for me