[Bug 268318] www/apache24 with www/mod_php8{0,1,2,3?}: opcache + ASLR turned on crashes Apache
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 268318] www/apache24: dumps core when rotating logs"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 21 May 2024 10:31:31 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268318 --- Comment #98 from Marián Černý <majo-bugs.freebsd.org@cerny.sk> --- (In reply to Marián Černý from comment #97) I take back my previous comment. Just disabling ASLR does not work for me. It worked for few `service apache24 reload` calls, but then crashed at midnight when rotating logs. Now it crashes even with `service apache24 reload`. It was crashing with the following backtrace: # lldb --core httpd-26294.core httpd (lldb) target create "httpd" --core "httpd-26294.core" Core file '/tmp/httpd-26294.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'httpd', stop reason = signal SIGSEGV * frame #0: 0x0000000801670f90 libgd.so.6 frame #1: 0x00000008022b54f2 opcache.so`___lldb_unnamed_symbol1014 + 66 frame #2: 0x0000000802877586 libphp.so`___lldb_unnamed_symbol8134 + 22 frame #3: 0x0000000802858ee0 libphp.so`zend_llist_apply_with_del + 64 frame #4: 0x00000008027f8d47 libphp.so`php_module_startup + 2343 frame #5: 0x00000008029550e5 libphp.so`___lldb_unnamed_symbol9803 + 21 frame #6: 0x00000008029548c6 libphp.so`___lldb_unnamed_symbol9798 + 118 frame #7: 0x0000000000262271 httpd`ap_run_post_config + 81 frame #8: 0x000000000025d8a5 httpd`main + 2421 frame #9: 0x000000000025cd80 httpd`_start + 256 Moving LoadModule php_module to the top of the list seems to "fix" (workaround) the crash. Looks like some bogus pointers. Hard to tell who to blame. If i is a bug in apache or PHP (opcache is a suspect). Would be great if somebody who has experience with apache/PHP debugging on FreeBSD would have a look. I guess it should not be so hard to pinpoint the issue when it is a reproducible problem. I am on a path migrating from mod_php to php-fpm, however despite mod_php being deprecated I do not think it should crash (e.g. the bug might still be present there and cause different problems). -- You are receiving this mail because: You are the assignee for the bug.