0 Replies Latest reply: Oct 15, 2013 9:01 PM by James.CAus
James.CAus Level 1 Level 1 (0 points)

We have 2 Xserves running Snow Leopard 10.6.8.

 

About a week ago I ran the Security Update 2013-04 on one of these servers.  This update included updating the PHP version from 5.3.15 to 5.3.26.

 

Since the update, the server that was updated has started regularly having crashed httpd processes (sometimes serveral per minute but sometimes only 1 every few minutes).  The server that was not updated has remained stable.

 

The CrashReporter log seems to indicate a problem with the Zend Engine memory management.  All the crash reports are pretty much the same.  Here is an example:

 

Process:     httpd [19097]
  Path:        /usr/sbin/httpd
   Identifier:  httpd
   Version:     ??? (???)
   Code Type:   X86-64 (Native)

   Parent Process:  httpd [49]

 

  Date/Time:   2013-10-16 14:41:32.555 +1100
  OS Version:  Mac OS X Server 10.6.8 (10K549)

  Report Version:  6

 

  Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

  Exception Codes: KERN_INVALID_ADDRESS at 0x0000000105cf5d10

  Crashed Thread:  0  Dispatch queue: com.apple.main-thread

 

  Thread 0 Crashed:  Dispatch queue: com.apple.main-thread

  0   libphp5.so                      0x0000000101323a7c _zend_mm_free_int + 41
  1   libphp5.so                      0x000000010131df2f zend_multibyte_read_script + 48
  2   libphp5.so                      0x000000010131e046 open_file_for_scanning + 207
  3   libphp5.so                      0x000000010131e32e compile_file + 139
  4   libphp5.so                      0x000000010119961d phar_compile_file + 844
  5   libphp5.so                      0x000000010133efa9 zend_execute_scripts + 253
  6   libphp5.so                      0x00000001012effb5 php_execute_script + 732
  7   libphp5.so                      0x00000001013bc15a php_handler + 1237
  8   httpd                           0x0000000100001e6b ap_run_handler + 90
  9   httpd                           0x0000000100002764 ap_invoke_handler + 354
  10  httpd                           0x00000001000304c7 ap_internal_redirect + 90
  11  mod_rewrite.so                  0x00000001003c4c11 handler_redirect + 202
  12  httpd                           0x0000000100001e6b ap_run_handler + 90
  13  httpd                           0x0000000100002764 ap_invoke_handler + 354
  14  httpd                           0x00000001000304c7 ap_internal_redirect + 90
  15  mod_rewrite.so                  0x00000001003c4c11 handler_redirect + 202
  16  httpd                           0x0000000100001e6b ap_run_handler + 90
  17  httpd                           0x0000000100002764 ap_invoke_handler + 354
  18  httpd                           0x00000001000304c7 ap_internal_redirect + 90
  19  mod_rewrite.so                  0x00000001003c4c11 handler_redirect + 202
  20  httpd                           0x0000000100001e6b ap_run_handler + 90
  21  httpd                           0x0000000100002764 ap_invoke_handler + 354
  22  httpd                           0x000000010002f9c4 ap_process_request + 103
  23  httpd                           0x000000010002c1a9 ap_process_http_connection + 116
  24  httpd                           0x00000001000134e3 ap_run_process_connection + 90
  25  httpd                           0x00000001000139b1 ap_process_connection + 91
  26  httpd                           0x0000000100036e0e child_main + 1257
  27  httpd                           0x0000000100036fcd make_child + 329
  28  httpd                           0x0000000100037253 perform_idle_server_maintenance + 498
  29  httpd                           0x000000010003777d ap_mpm_run + 1246
  30  httpd                           0x000000010000a49a main + 2878
  31  httpd                           0x00000001000014d0 start + 52

 

  Thread 0 crashed with X86 Thread State (64-bit):

    rax: 0x0000000105cf5d10  rbx: 0x0000000105cf5d10  rcx: 0x0000000000000000  rdx: 0x0000000000000001

    rdi: 0x0000000100a1c000  rsi: 0x0000000105cf5d20  rbp: 0x00007fff5fbfeb50  rsp: 0x00007fff5fbfeb10


r8: 0x00007fffffe0082c   r9: 0x0000000000000007  r10: 0x0000000000000001  r11: 0x0000000103128598

    r12: 0x0000000101a018e0  r13: 0x00000001001ff000  r14: 0x0000000000000000  r15: 0x0000000000000000

    rip: 0x0000000101323a7c  rfl: 0x0000000000000202  cr2: 0x0000000105cf5d10

 

  Binary Images:


0x100000000 -    0x10004cfef +httpd ??? (???) <37C41474-9EBF-99EA-BE6D-02009ECC563D> /usr/sbin/httpd

0x100080000 -    0x1000a8ff7  libpcre.0.dylib 1.1.0 (compatibility 1.0.0) <61E04B84-398D-0E87-7125-A668E797DE77> /usr/lib/libpcre.0.dylib

0x1000ad000 -    0x1000c5fe7  libaprutil-1.0.dylib 4.9.0 (compatibility 4.0.0) <EE4E295F-B414-930C-4CFA-0D2E1265A5FC> /usr/lib/libaprutil-1.0.dylib

0x1000d0000 -    0x1000eefff  libapr-1.0.dylib 4.8.0 (compatibility 4.0.0) <E2A33E20-2442-DDE8-11D4-6135D055567E> /usr/lib/libapr-1.0.dylib

0x10012e000 -    0x10012efff  mod_authn_file.so ??? (???) <166F0153-A12D-5B6D-42EF-0FEA32FF6C65> /usr/libexec/apache2/mod_authn_file.so

0x100132000 -    0x100132ff7  mod_authn_anon.so ??? (???) <CC7213A3-2E25-054D-288C-27D20A9E7FA9> /usr/libexec/apache2/mod_authn_anon.so

... etc ...

 

Which presents 2 obvious possible solutions:

1) Is this a known issue with the Security Update that can be easily fixed?  How?

2) Otherwise, is it possible to roll back the security update?  How?


Xserve, Mac OS X (10.6.8), Apache 2.0, PHP 5.3.26, Zend 2.3.0