After being forced to upgrade to PHP 5.3.10 due to security patches, my Drupal site started giving a 500 Internal Server Error. While debugging this problem, I was able to determine that by removing the VBO module the site functions correctly again. I have not been able to pinpoint the exact cause of the issue yet, but I will try to post an update if I uncover it.

I have not tried the 7.x module to see if it has the same behavior.

Comments

bojanz’s picture

bojanz commented

There's always an exact error behind an Error 500.
You will need to look at your error log and find out what it is, in order for us to be able to debug it.
Also, make sure you're running latest VBO (1.13)

bojanz’s picture

bojanz commented
Status: Active » Postponed (maintainer needs more info)
_doyle_’s picture

_doyle_ commented

We are currently running Drupal on IIS 7 w/ FastCGI. Here is what I get from the 500 Error, I also tried setting the ErrorReporting in IIS to "PassThrough" and tried turning on Debugging in the Drupal index.php file but all I receive is the WSOD. (URL because I just re-enabled the 6.x-1.13 module.)

Error Summary
HTTP Error 500.0 - Internal Server Error
C:\PHP\php-cgi.exe - The FastCGI process exited unexpectedly
Detailed Error Information
Module FastCgiModule
Notification ExecuteRequestHandler
Handler PHP_via_FastCGI
Error Code 0x000000ff
Requested URL https://localhost:443/index.php?q=admin/build/modules/list/confirm
Physical Path \index.php
Logon Method Anonymous
Logon User Anonymous

I turned on PHP logging as well and no errors seem to be generated on that end either.

Thanks,
John

bojanz’s picture

bojanz commented

There is nothing I can do in that case. I have nothing to work on.

_doyle_’s picture

_doyle_ commented

If I can find out any additional details, I will post them.

Thanks,
John

bojanz’s picture

bojanz commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Okay. Reopen the issue when you do.

ayalon’s picture

ayalon commented
Status: Active » Closed (cannot reproduce)

I have exactly the same problem with Zend Server Community Edition 5.6.0 (Php 5.3.9).

If the Views Bulk Operation Module is in the module folder, the server crashes.
ZendEnabler.log

[15.02.2012 13:29:01] Error: Read data error - unable to get read result. Code 109.
[15.02.2012 13:29:01] Error: Request for XXXXX/index.php: Unable to get the response from PHP process
[15.02.2012 13:43:17] Error: PHP process 3728 from the "application/x-httpd-php" pool has exited with status 255.

I was not able to find the exact error.

ayalon’s picture

ayalon commented
Status: Closed (cannot reproduce) » Active

I was able to trace this down, but I don't know why this is a problem with php 5.3.9

Because of the hook_init() of VBO all drupal pages are affected. The bug takes down the whole drupal site.

I was able to finde the code line that creates the WSOD, but I don't understand why

views_bulk_operations.module: Line 37

    case TAXONOMY_ACTION_DELETE:
      foreach ($context['fields'] as $field => $terms) {
        if (!is_array($node->{$field})) {
          continue;
        }
        if (empty($node->{$field})) {
          continue;
        }
        foreach ($terms as $term) {
          foreach ($node->{$field} as $k => $already) {
            if ($already['value'] == $term['value']) {
              //THIS UNSET CRASHES PHP 5.3.9
              //UNCOMMENTING SOLVED THE INIT CRASH
              //unset($node->{$field}[$k]);
            }
          }
          // Reset numerical IDs to make it continous
          $node->{$field} = array_values($node->{$field});
        }
      }
      break;

Maybe someone has an idea.

ayalon’s picture

ayalon commented

Ok i found it:
https://bugs.php.net/bug.php?id=48034

The file is exactly 8192 Bytes long.

Adding or uncommenting anything in the file solved the bug.

The bug has nothing directly to do with VBO but maybe someone has the same problem.

You can solve it by changing the file size.

bojanz’s picture

bojanz commented
Status: Closed (cannot reproduce) » Closed (works as designed)

That's a really odd PHP bug. Noted.

marktheshark’s picture

marktheshark commented
Status: Closed (works as designed) » Active

Sorry for reopening, but which file are you referring to in particular?

bojanz’s picture

bojanz commented
Status: Active » Closed (works as designed)

content_taxonomy.action.inc