Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
Am Sat, 3 Feb 2018 14:04:17 +0100 Dimitry Andric schrieb: > On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > Dimitry Andric schrieb: > >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > >>> On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > performed > updates of the ports tree. Since Sunday, I receive segmenatation faults > (SIG 11) > when accessing the server, especially with setup of nextcloud, refdb, > phpldapadmin > and any other access with LDAP backend (all https). > ... > > Starting program: /usr/local/sbin/httpd -X > > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] > > (2)No such > > file or directory: AH00075: Failed to enable the 'httpready' Accept Filter > > [Sat Feb 03 > > 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such > > file or > > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP > > 101096 of > > process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process > > 59320] > > [New LWP 101103 of process 59320] > > [New LWP 101102 of process 59320] > > [New LWP 101110 of process 59320] > > [New LWP 101107 of process 59320] > > [New LWP 101098 of process 59320] > > [New LWP 101099 of process 59320] > > [New LWP 101108 of process 59320] > > [New LWP 101112 of process 59320] > > [New LWP 101101 of process 59320] > > [New LWP 101104 of process 59320] > > [New LWP 101097 of process 59320] > > [New LWP 101106 of process 59320] > > [New LWP 10 of process 59320] > > [New LWP 101100 of process 59320] > > [LWP 101096 of process 59320 exited] > > > > Thread 11 received signal SIGSEGV, Segmentation fault. > > [Switching to LWP 101108 of process 59320] > > 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so > > > > Run the "backtrace" command there, please. If it doesn't give any > function names, try setting WITH_DEBUG=1 in the environment, then > rebuilding the mod_php56 port (and optionally also the php56 and > apache24 ports themselves), to add debug info. > > -Dimitry > www/mod_php56: env WITH_DEBUG=1 make reinstall (prior to that, I had to "pkg delete" the port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as recommended and performing command sequence to enter gdb, run -X, the Apache 2.4 now crashes immediately and not when the URL is called by the browser triggering the fault. This is what I get then: bt #0 0x00080208b382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so #1 0x000802088e1a in ?? () from /usr/local/lib/php/20131226-zts/opcache.so #2 0x000802085f12 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so #3 0x000802085cf3 in zend_accel_script_optimize () from /usr/local/lib/php/20131226-zts/opcache.so #4 0x00080207a393 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so #5 0x0008020799d6 in persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.so #6 0x00080195d33c in zend_execute_scripts () from /usr/local/libexec/apache24/libphp5.so #7 0x0008018f47a3 in php_execute_script () from /usr/local/libexec/apache24/libphp5.so #8 0x0008019f1015 in ?? () from /usr/local/libexec/apache24/libphp5.so #9 0x002563d7 in ap_invoke_handler () #10 0x0029005d in ap_process_async_request () #11 0x0028ca2d in ap_process_http_connection () #12 0x0026e3b7 in ap_run_process_connection () #13 0x00080152827f in ?? () from /usr/local/libexec/apache24/mod_mpm_event.so #14 0x000801527e11 in ?? () from /usr/local/libexec/apache24/mod_mpm_event.so #15 0x0008005d2476 in ?? () from /lib/libthr.so.3 #16 0x in ?? () Backtrace stopped: Cannot access memory at address 0x7fffde1ef000 -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpPDWol2DJ2G.pgp Description: OpenPGP digital signature
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
Am Sun, 4 Feb 2018 12:28:54 +0100 "O. Hartmann" schrieb: > Am Sat, 3 Feb 2018 14:04:17 +0100 > Dimitry Andric schrieb: > > > On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > > > > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > > Dimitry Andric schrieb: > > >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > >>> On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > >>> > > > > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 > > and > > performed updates of the ports tree. Since Sunday, I receive > > segmenatation > > faults (SIG 11) when accessing the server, especially with setup of > > nextcloud, > > refdb, phpldapadmin and any other access with LDAP backend (all > > https). > > ... > > > Starting program: /usr/local/sbin/httpd -X > > > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] > > > (2)No such > > > file or directory: AH00075: Failed to enable the 'httpready' Accept > > > Filter [Sat Feb > > > 03 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No > > > such file or > > > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New > > > LWP 101096 > > > of process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of > > > process > > > 59320] [New LWP 101103 of process 59320] > > > [New LWP 101102 of process 59320] > > > [New LWP 101110 of process 59320] > > > [New LWP 101107 of process 59320] > > > [New LWP 101098 of process 59320] > > > [New LWP 101099 of process 59320] > > > [New LWP 101108 of process 59320] > > > [New LWP 101112 of process 59320] > > > [New LWP 101101 of process 59320] > > > [New LWP 101104 of process 59320] > > > [New LWP 101097 of process 59320] > > > [New LWP 101106 of process 59320] > > > [New LWP 10 of process 59320] > > > [New LWP 101100 of process 59320] > > > [LWP 101096 of process 59320 exited] > > > > > > Thread 11 received signal SIGSEGV, Segmentation fault. > > > [Switching to LWP 101108 of process 59320] > > > 0x000802300382 in ?? () from > > > /usr/local/lib/php/20131226-zts/opcache.so > > > > Run the "backtrace" command there, please. If it doesn't give any > > function names, try setting WITH_DEBUG=1 in the environment, then > > rebuilding the mod_php56 port (and optionally also the php56 and > > apache24 ports themselves), to add debug info. > > > > -Dimitry > > > www/mod_php56: env WITH_DEBUG=1 make reinstall (prior to that, I had to "pkg > delete" the > port www/mod_php56 first). When having mod_php56 rebuilt with DEBUG on as > recommended > and performing command sequence to enter gdb, run -X, the Apache 2.4 now > crashes > immediately and not when the URL is called by the browser triggering the > fault. This is > what I get then: > > bt > #0 0x00080208b382 in ?? () from > /usr/local/lib/php/20131226-zts/opcache.so > #1 0x000802088e1a in ?? () from > /usr/local/lib/php/20131226-zts/opcache.so > #2 0x000802085f12 in ?? () from > /usr/local/lib/php/20131226-zts/opcache.so > #3 0x000802085cf3 in zend_accel_script_optimize () > from /usr/local/lib/php/20131226-zts/opcache.so #4 0x00080207a393 in ?? > () > from /usr/local/lib/php/20131226-zts/opcache.so #5 0x0008020799d6 in > persistent_compile_file () from /usr/local/lib/php/20131226-zts/opcache.so #6 > 0x00080195d33c in zend_execute_scripts () > from /usr/local/libexec/apache24/libphp5.so #7 0x0008018f47a3 in > php_execute_script () from /usr/local/libexec/apache24/libphp5.so #8 > 0x0008019f1015 in ?? () from /usr/local/libexec/apache24/libphp5.so #9 > 0x002563d7 in ap_invoke_handler () #10 0x0029005d in > ap_process_async_request () #11 0x0028ca2d in > ap_process_http_connection () #12 > 0x0026e3b7 in ap_run_process_connection () #13 0x00080152827f in > ?? () > from /usr/local/libexec/apache24/mod_mpm_event.so #14 0x000801527e11 in > ?? () > from /usr/local/libexec/apache24/mod_mpm_event.so #15 0x0008005d2476 in > ?? () > from /lib/libthr.so.3 #16 0x in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffde1ef000 > > I forgot to mention, that I already have rebuilt www/apache24 via portmaster -df and I also have rebuild all php ports/modules installed including php56 itself (but without debugging, it takes a while on that box). -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpGqL2iZgMnS.pgp Description: OpenPGP digital signature
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > Am Tue, 30 Jan 2018 00:09:07 +0100 > Dimitry Andric schrieb: >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: >>> On 29 Jan 2018, at 19:39, O. Hartmann wrote: Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and performed updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG 11) when accessing the server, especially with setup of nextcloud, refdb, phpldapadmin and any other access with LDAP backend (all https). ... > Starting program: /usr/local/sbin/httpd -X > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] > (2)No such file > or directory: AH00075: Failed to enable the 'httpready' Accept Filter [Sat > Feb 03 > 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file > or > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP > 101096 of > process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process > 59320] > [New LWP 101103 of process 59320] > [New LWP 101102 of process 59320] > [New LWP 101110 of process 59320] > [New LWP 101107 of process 59320] > [New LWP 101098 of process 59320] > [New LWP 101099 of process 59320] > [New LWP 101108 of process 59320] > [New LWP 101112 of process 59320] > [New LWP 101101 of process 59320] > [New LWP 101104 of process 59320] > [New LWP 101097 of process 59320] > [New LWP 101106 of process 59320] > [New LWP 10 of process 59320] > [New LWP 101100 of process 59320] > [LWP 101096 of process 59320 exited] > > Thread 11 received signal SIGSEGV, Segmentation fault. > [Switching to LWP 101108 of process 59320] > 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so Run the "backtrace" command there, please. If it doesn't give any function names, try setting WITH_DEBUG=1 in the environment, then rebuilding the mod_php56 port (and optionally also the php56 and apache24 ports themselves), to add debug info. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
Am Sat, 3 Feb 2018 11:43:25 +0100 "O. Hartmann" schrieb: > Am Tue, 30 Jan 2018 00:09:07 +0100 > Dimitry Andric schrieb: > > > On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > > > > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > >> > > >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > > >> performed > > >> updates of the ports tree. Since Sunday, I receive segmenatation faults > > >> (SIG 11) > > >> when accessing the server, especially with setup of nextcloud, refdb, > > >> phpldapadmin > > >> and any other access with LDAP backend (all https). > > >> > > >> The message on console is: > > >> > > >> pid 23108 (httpd), uid 80: exited on signal 11 > > >> pid 32283 (httpd), uid 80: exited on signal 11 > > >> pid 21286 (httpd), uid 80: exited on signal 11 > > >> pid 10292 (httpd), uid 80: exited on signal 11 > > >> > > >> I do not see anything else! Neither in the log (no matter what log level > > >> I switch > > >> on) nor elsewhere. > > >> > > >> Configuration hasn't changed. > > >> > > >> What the ... is up with the system? How can I dig into the problem? > > > > > > Try debugging httpd, e.g.: > > > > > > sudo /usr/local/sbin/httpd -X > > > > I meant "sudo gdb /usr/local/sbin/httpd -X", sorry. > > > > -Dimitry > > > > I see this: > > > Starting program: /usr/local/sbin/httpd -X > [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] > (2)No such > file or directory: AH00075: Failed to enable the 'httpready' Accept Filter > [Sat Feb 03 > 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file > or > directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP > 101096 of > process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process > 59320] > [New LWP 101103 of process 59320] > [New LWP 101102 of process 59320] > [New LWP 101110 of process 59320] > [New LWP 101107 of process 59320] > [New LWP 101098 of process 59320] > [New LWP 101099 of process 59320] > [New LWP 101108 of process 59320] > [New LWP 101112 of process 59320] > [New LWP 101101 of process 59320] > [New LWP 101104 of process 59320] > [New LWP 101097 of process 59320] > [New LWP 101106 of process 59320] > [New LWP 10 of process 59320] > [New LWP 101100 of process 59320] > [LWP 101096 of process 59320 exited] > > Thread 11 received signal SIGSEGV, Segmentation fault. > [Switching to LWP 101108 of process 59320] > 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so > > I also filed a bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225499 -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpOPdBRdj9lt.pgp Description: OpenPGP digital signature
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
Am Tue, 30 Jan 2018 00:09:07 +0100 Dimitry Andric schrieb: > On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: > >> > >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > >> performed > >> updates of the ports tree. Since Sunday, I receive segmenatation faults > >> (SIG 11) when > >> accessing the server, especially with setup of nextcloud, refdb, > >> phpldapadmin and any > >> other access with LDAP backend (all https). > >> > >> The message on console is: > >> > >> pid 23108 (httpd), uid 80: exited on signal 11 > >> pid 32283 (httpd), uid 80: exited on signal 11 > >> pid 21286 (httpd), uid 80: exited on signal 11 > >> pid 10292 (httpd), uid 80: exited on signal 11 > >> > >> I do not see anything else! Neither in the log (no matter what log level I > >> switch > >> on) nor elsewhere. > >> > >> Configuration hasn't changed. > >> > >> What the ... is up with the system? How can I dig into the problem? > > > > Try debugging httpd, e.g.: > > > > sudo /usr/local/sbin/httpd -X > > I meant "sudo gdb /usr/local/sbin/httpd -X", sorry. > > -Dimitry > I see this: Starting program: /usr/local/sbin/httpd -X [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file or directory: AH00075: Failed to enable the 'httpready' Accept Filter [Sat Feb 03 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file or directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP 101096 of process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process 59320] [New LWP 101103 of process 59320] [New LWP 101102 of process 59320] [New LWP 101110 of process 59320] [New LWP 101107 of process 59320] [New LWP 101098 of process 59320] [New LWP 101099 of process 59320] [New LWP 101108 of process 59320] [New LWP 101112 of process 59320] [New LWP 101101 of process 59320] [New LWP 101104 of process 59320] [New LWP 101097 of process 59320] [New LWP 101106 of process 59320] [New LWP 10 of process 59320] [New LWP 101100 of process 59320] [LWP 101096 of process 59320 exited] Thread 11 received signal SIGSEGV, Segmentation fault. [Switching to LWP 101108 of process 59320] 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgp6VqYXNDlzN.pgp Description: OpenPGP digital signature
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: >> >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and >> performed >> updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG >> 11) when >> accessing the server, especially with setup of nextcloud, refdb, >> phpldapadmin and any >> other access with LDAP backend (all https). >> >> The message on console is: >> >> pid 23108 (httpd), uid 80: exited on signal 11 >> pid 32283 (httpd), uid 80: exited on signal 11 >> pid 21286 (httpd), uid 80: exited on signal 11 >> pid 10292 (httpd), uid 80: exited on signal 11 >> >> I do not see anything else! Neither in the log (no matter what log level I >> switch on) nor >> elsewhere. >> >> Configuration hasn't changed. >> >> What the ... is up with the system? How can I dig into the problem? > > Try debugging httpd, e.g.: > > sudo /usr/local/sbin/httpd -X I meant "sudo gdb /usr/local/sbin/httpd -X", sorry. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > performed > updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG > 11) when > accessing the server, especially with setup of nextcloud, refdb, phpldapadmin > and any > other access with LDAP backend (all https). > > The message on console is: > > pid 23108 (httpd), uid 80: exited on signal 11 > pid 32283 (httpd), uid 80: exited on signal 11 > pid 21286 (httpd), uid 80: exited on signal 11 > pid 10292 (httpd), uid 80: exited on signal 11 > > I do not see anything else! Neither in the log (no matter what log level I > switch on) nor > elsewhere. > > Configuration hasn't changed. > > What the ... is up with the system? How can I dig into the problem? Try debugging httpd, e.g.: sudo /usr/local/sbin/httpd -X then "run", and see if you can get a backtrace. -Dimitry signature.asc Description: Message signed with OpenPGP
