Closed (fixed)
Project:
Rules
Version:
7.x-2.0
Component:
Rules Core
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2012 at 18:56 UTC
Updated:
26 Sep 2012 at 16:58 UTC
Jump to comment: Most recent
Hi,
I have like 5 modules from the drupal commerce project that require me to have "drupal ui" enabled.
I am working on a bran new website and have no content yet.
I can enable "rules" no problem.
When I go to enable "Rules UI" i get a page cannot be displayed message.
Message from google chrome "Error 101 (net::ERR_CONNECTION_RESET): The connection was reset"
It produces no error logs at all. I have attempted to clear the cache but that did not help.
I have all my modules up to date as everything has been installed today.
How can I find out whats causing this error?
Thanks
Fi3nds
Comments
Comment #1
b9tribeca commentedI'm also having the same problem and I'm stuck on my project.
Comment #2
fagoPlease be sure to use the latest release or dev version. If the problem is still there try checking your error logs (drupal + server).
Comment #3
captainpants commentedI'm getting the same problem. No errors regarding the problem are popping up in the Drupal log but there is something in the Apache log. It's important to note that it may be the same problem present in this issue here.
Apache Log:
[Thu Feb 02 08:29:08 2012] [notice] Parent: child process exited with status 255 -- Restarting.
[Thu Feb 02 08:29:08 2012] [notice] Apache/2.2.21 (Win64) PHP/5.3.9 configured -- resuming normal operations
[Thu Feb 02 08:29:08 2012] [notice] Server built: Sep 24 2011 19:57:51
[Thu Feb 02 08:29:08 2012] [notice] Parent: Created child process 1240
[Thu Feb 02 08:29:09 2012] [notice] Child 1240: Child process is running
[Thu Feb 02 08:29:09 2012] [notice] Child 1240: Acquired the start mutex.
[Thu Feb 02 08:29:09 2012] [notice] Child 1240: Starting 64 worker threads.
[Thu Feb 02 08:29:09 2012] [notice] Child 1240: Starting thread to listen on port 80.
[Thu Feb 02 08:29:09 2012] [notice] Child 1240: Starting thread to listen on port 80.
Comment #4
DavilaG commentedSame for me, I cannot enable "Rules UI". It worked ok on my local dev environment using WAMP server but when I deployed to my site using IIS 7.5 with PHP 5.3, I get an error (details below), without logging any more detailed PHP error. I'm using a whole bunch of multilingual modules, but I guess it's not related to that since I already tried installing Rules and Rules UI alone without any luck.
Any help would be greatly appreciated.
HTTP Error 500.0 - Internal Server Error
C:\Program Files (x86)\PHP\v5.3\php-cgi.exe - The FastCGI process exited unexpectedly
Detailed Error Information
Module FastCgiModule
Notification ExecuteRequestHandler
Handler PHP53_via_FastCGI
Error Code 0x000000ff
Requested URL http://MAINSITENAME/index.php?q=admin/modules/list/confirm
Physical Path C:\inetpub\wwwroot\MAINSITENAME\index.php
Logon Method Anonymous
Logon User Anonymous
Comment #5
tiger65 commentedI am trying to evaluate Drupal Commerce in a WAMP localhost setting. I am working with Core 7.12+4-dev, Rules 7.x-2.0+15 and Commerce 7.x-1.2 which needs Rules UI enabled. I can't do anything more until this is fixed and I don't know how to fix it. Frustrating.
Thanks for listening.
Comment #6
tmcrisp commented+1
Comment #7
youssefr commented+1
This is my Apache error_log right after I click "save"
Comment #8
tiger65 commentedA colleague of mine found a work around that allows RulesUI to be enabled. There may be other issues as well.
Edit path "sites/all/modules/rules/rules_admin/rules_admin.module" and add a line of PHP code to it. He added "$crashFix = 1;" to the top of the file, before the declaration of the first function. YMMV
Comment #9
Anonymous (not verified) commented#8 worked on my fastcgi error on Win Serv 2008 R2, IIS 7.5, PHP 5.3.9 TS, Drupal 7.12, rules.7.x.2.x.
Same concern, "other issues?".
Comment #10
Anonymous (not verified) commented#8 worked but I don't like it. Where's the problem?
..
WAMP@W7@64bit
Comment #11
Misura commentedYep, #8 worked but I don't like it either. What is up with wamp? I am running the latest version and I hate that it does this for some modules.
Comment #12
youssefr commented+1
Comment #13
travis09 commented+1
Comment #14
JayMN commented+1
Comment #15
blainelang commentedI don't know what #8 does as I can not find any reference to this option in drupal or IIS documentation but it has allowed me to now enabled the rules_ui modules without IIS crashing. I only noticed this after updating to PHP 5.3 (from 5.2.x) and two of my previous local dev sites would not load. After manually disabling modules via the DB, I was able to isolate the root cause and get the site to load but trying to enable rules_ui would crash IIS. This on Windows 7 64-bit, IIS using fastcgi thread safe version of PHP 5.3.10
Comment #16
jay.lee.bio commentedI can also confirm that #8 fixed my version, 7.x-2.0, on Wamp. Can someone confirm that Rules UI can be enabled as is WITHOUT #8 on a live server?
Comment #17
Anonymous (not verified) commented#8 did not work for me
Comment #18
Sk1Zy commented#8 Fixed it for me.
Comment #19
earlofsandwich commentedThe problem seems to be related to the empty line on line 2 of the rules_admin.module.
If you simply delete line 2 the problem goes away. Adding $crashFix=1; on line 2 fixes it by making it not a blank line as far as I can tell.
Bizarre!
Comment #20
mike64 commented#19 Fixed it for me.
Comment #21
aouko commentedThis is actually because of the PHP "4096" bug. The fixes posted here work only because the size of the file is changed from 4096 bytes. See here: https://bugs.php.net/bug.php?id=61166
Comment #22
earlofsandwich commentedAwesome find bigtings - I always hate it when you have a fix that works but can't fathom why.
Comment #23
KrisG commented+1 for #21 and bigtings. I just added a full stop at the end of line 4 (* @file Rules Admin UI) and that stopped the crash when installing the module on Vista WAMP (VAMP?).
Comment #24
travis09 commented#19 Just removed the extra space from line 2 as suggested and now Rules UI is enabled and working. Simple but effective. Thanks earlofsandwich
Comment #25
kingfisher64 commented#19 works great.
Can hardly release a new version to delete two lines of whitespace, but the mod doesn't install without this.
Comment #26
fago#21: Wow, what a weird bug. Thanks for tracking it down.
Anyway, I've just committed the fix for #1319912: rebuilding the cache is slow due to integrityChecks which contained a change for rules_admin.module. Thus this should be fixed then too. Of course, it could coincidentally reappear anytime. There's nothing we can do about that.
Comment #27
Triumphent commented#8 worked for me. Thanks Tiger. :)
Comment #28
Rontero commented#21 fixed this for me.
For new pips -
the solution is
as follows:
Comment #29
Punk_UnDeaD> Edit rules_admin.module by deleting second (should by empty) line. Save the file;
simply change any character, just press the spacebar
or delete second or last blank line - it does not matter
Comment #31
magiainformatica commentedSame problem found in installing localization ...
Change dimension of file and problem magically disappears.
The reason is explained by adam.hammouda on May 7, 2012 at 10:13pm in his post that I copy here:
<<
Posted by adam.hammouda on May 7, 2012 at 10:13pm
Just wanted to chime in and mention that the issue is even more ridiculous than this. It's actually a PHP bug which triggers when an include/require'd file is of a certain size.
See e.g.:
https://bugs.php.net/bug.php?id=48034
https://bugs.php.net/bug.php?id=50982
For a few relevant PHP issues. This occurs when processing files with sizes that are exact multiples of 4096 bytes and causes PHP to segfault (!).
The reason your wordpad solution works is because wordpad re-formats the line feeds in the file from \n (unix style) to \r\n (windows style) upon save - which changes the files size from the problematic value of 53248 (exactly 52 KB). To verify this - you can simply edit the modules/locale/locale.admin.inc file and add or remove a character anywhere in the file. It will now work properly.
Please note that this bug appears to have been fixed in PHP 5.3.14 - so you might want to consider updating (I'm guessing this issue will be commonly run into by people running WAMP which is not up to 5.3.14 yet).
<<
Comment #32
drupauler commentedI've encountered the same problem.
I made the change in #28 which had no effect.
However I discovered by change that if I enabled the rules UI module whilst making another change, say, enabling or disabling the book module, it worked!
More worringly I now have to do the same thing enabling/disabling other modues.
I'm running the Acquia dev stack under winxp, with php539.
I'm a new around here, so any assistance would be most welcome!