Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I cannot view, edit or clone custom rules. I can translate them, delete them or clone them. Default rules seem to behave fine. When I try to edit/view/clone custom rules, I see a 500 error. However, it seems to be inconsistent in-so-much-as about one time in ten editing/viewing works.
The host I use is Japanese, but the upshot of their error message is that "CGI or possible SSI is not behaving correctly."
Is it similar to this issue from a couple of years ago? https://drupal.org/node/1258284
Comments
Comment #1
cabralje CreditAttribution: cabralje commentedI am having the same problem.
Comment #2
jsquyres CreditAttribution: jsquyres commentedI'm also seeing this behavior.
Comment #3
rabeto CreditAttribution: rabeto commentedI have had the same problem since i updated my rules module
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Comment #4
matt.rad CreditAttribution: matt.rad commentedI have now also had every page, as well as custom rules, return the same error for a few hours then go away. Has this happened to anyone else?
Comment #5
tgshannon CreditAttribution: tgshannon commentedI'm also getting this problem. I was able to create a new rule but got an error when I added a condition in the second step. I couldn't figure out what when into the data selector field, and tried different options and would get the error. I then tried to edit a current rule and get the 500 internal error immediately.
Comment #6
fagoPlease make sure clearing caches runs through properly and try to find additional errors in the server log. If that all does not help please report your PHP version and how its run (apache mod-php, cgi, fcgi, ..)
Comment #7
fagoComment #8
tgshannon CreditAttribution: tgshannon commentedI cleared cache twice, and received the caches cleared message both times. Php version is 5.2.17 and php memory limit is 900M.
I'll have to get with the site owner and have her go through the server logs with support. The site is on a shared host, and is very slow at times. What server logs should she review with support?
error when trying to edit a rule:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@cololitnet.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.24 (Unix) mod_hive/3.6 mod_ssl/2.2.24 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.35 Server at cololitnet.com Port 443
Comment #9
gejo CreditAttribution: gejo commentedI'm getting this same error when trying to use Rules Forms Support module.
I've posted this issue there.
Comment #10
matt.rad CreditAttribution: matt.rad commentedUsing PHP Version 5.2.17/Apache
Caches clearing fine, and I am in the habit of clearing them frequently.
Comment #11
ataxia CreditAttribution: ataxia commentedI just upgraded Rules to 7.x-2.5, and now I can't edit any rules. This is a critical situation, as my customer needs updates by tomorrow. When I try to edit any rule, I get "ERROR 500 - INTERNAL SERVER ERROR".
This is the format of the URL that's causing the issue:
http://example.com/admin/config/workflow/rules/reaction/manage/3
I noticed that on my dev site (on which I haven't updated Rules) the URL is shown in an overlay:
http://devexample.com/#overlay=admin/config/workflow/rules/reaction/mana...
Also, the Recent Log Messages file is showing several Page Not Found errors with these Locations:
http://example.com/admin/config/workflow/rules/reaction/manage/cgi-sys/i...
http://example.com/admin/config/workflow/rules/reaction/manage/cgi-sys/i...
http://example.com/admin/config/workflow/rules/reaction/manage/cgi-sys/i...
http://example.com/admin/config/workflow/rules/reaction/manage/cgi-sys/j...
http://example.com/admin/config/workflow/rules/reaction/manage/cgi-sys/i...
Comment #12
evanmwillhite CreditAttribution: evanmwillhite commentedI too got a 500 error when I tried to clone and make inactive. I was able to successfully clone one (I think) but it is not appearing in the Rules UI. Here's the log entry for the 500 error:
Comment #13
tgshannon CreditAttribution: tgshannon commentedThe following is the error reported by the arvixe support staff when duplicating problem.
[Sun Oct 13 18:43:40 2013] [error] [client 76.30.23.192] Premature end of script headers: index.php, referer: https://cololitnet.com/users/arvixe
Comment #14
jami3z CreditAttribution: jami3z commentedI have the exact same issue as #11
Comment #15
jami3z CreditAttribution: jami3z commentedIf I disabled all my rules I was able to edit it. I then just enabled the rule I had issues and I was able to edit it with no issues. Maybe there was an issue with one of my other rules, strange. Will update if I come across anything else.
Comment #16
tgshannon CreditAttribution: tgshannon commentedI deleted the two rules I had, and cleared the cache. I added a rule and when I tried to add a condition check I get the 500 error.
I also cloned the site on my localhost (mac) and do not get the error.
Comment #17
katriencI had the same issue on a webserver running PHP 5.2
But the same site works very well on a webserver running PHP 5.3
When I put line 49-52 (rules/ui/ui.forms.inc) in comment the 500 error disappear.
Comment #18
tgshannon CreditAttribution: tgshannon commentedUpgrading to php 5.4 fixed the problem for me. I later changed to php 5.3.27 because 5.4 was causing some problems that had patches available, but 5.3 was easier to go to at this time.
Comment #19
ataxia CreditAttribution: ataxia commentedRE: #11
Upgrading PHP to 5.3.27 fixed this problem for me.
Comment #20
oosthupj CreditAttribution: oosthupj commentedI upgraded from Rules 7.x-2.3 to 7.x-2.6 and also got this 500 error. I had to revert as I had urgent rules to work on. Reverted back to Rules 7.x-2.3 and the 500 error is gone.
Using Php 5.2.17
I cannot change the php version as I am hosting my website at a hosting company not by myself.
Comment #21
peter.morlion CreditAttribution: peter.morlion commentedSame problem here. 7.x-2.6. However, I can edit 3 of my 4 rules. All rules have events, conditions and actions. Enabling or disabling doesn't help. The rule I can't edit is my most complex one (it has a lot of conditions, i.e. about 10).
Comment #22
mrtwo87 CreditAttribution: mrtwo87 commentedI was running into this issue as well. I also upgraded my PHP from 5.2 to 5.4 which fixed the problem.
**NOTE: I have shared hosting with Bluehost. I had upgraded the PHP to 5.4 a couple weeks prior to running into this issue. I know Bluehost was performing server maintenance a couple days ago and it must have reset my PHP back to 5.2 (only thing I can think of that changed). If you are on Bluehost, you can adjust your PHP configuration from your CPanel, in "PHP config" under the "Software/Services" heading.
Thanks for the helpful info everyone :)
Comment #23
matt.rad CreditAttribution: matt.rad commentedUpgrading to PHP 5.4 sorted this out for me too.
In case it is helpful to someone else, I found that my shared host allowed me to set the version of PHP I was running on my site by adding
AddHandler php5.4-script .php
to .htaccess.
I can't vouch for this being the recommended approach, but it worked and only took a second to organize.
Comment #24
danwonac CreditAttribution: danwonac commentedUpgrading PHP was not an option for me.
Downgrading to rules 7.x-2.3 from any higher version resolved the issue (all higher versions produced 500 errors). I didn't try downgrading webform rules.
Comment #25
tparc CreditAttribution: tparc commentedMaintainer(s), what more information is needed to resolve this?
This appears to be a major bug related to the latest version of rules and earlier versions of PHP. What has changed to have caused this?
Comment #26
fabul CreditAttribution: fabul commentedI can see this issue on production environment as well.
Unless Overlay Module is enabled, no overlay can be watched in the administration screen.
It works as if overlay wasn't enabled.
Wouldn't it be in consequence of PHP or Apache configuration ?
In development environment, Overlay works well and rules can be edited and cloned.
Comment #27
MostlyGhostly CreditAttribution: MostlyGhostly commentedI was having the same issue.
I upgraded PHP to 5.5 and it seems to be working fine now.
Comment #28
ivanhelguera CreditAttribution: ivanhelguera commentedI do have the issue in php 5.5 (ubuntu 14.04)
Comment #29
milos.kroulik CreditAttribution: milos.kroulik commentedIn my case, the cause of problem was activated xdebug, with
xdebug.max_nesting_level
set too low. Adding following to .htaccess file worked for me:Comment #30
manoloka CreditAttribution: manoloka commentedSame problem here happened all of the sudden, yesterday worked today Internal Server Error
I could get rid of the problem by downgrading all the way down to 7.x-2.3
Any ideas?
Comment #31
manoloka CreditAttribution: manoloka commented@milos.kroulik
I tried you solution but didn't work for me? Which .htaccess file you put it in? the root one? other?
Mine shows this now
Comment #32
milos.kroulik CreditAttribution: milos.kroulik commented@manoloka Yes, it was the root one.
Comment #33
TR CreditAttribution: TR commentedIf you continue to have this problem, please open a new issue and provide detailed steps to reproduce the issue on a clean site.