apache signal bus error (10)

[doug schmidt]

On Wed, Apr 28, 2010 at 4:26 PM, Greg Larkin <glarkin at freebsd.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> doug schmidt wrote:
>> On Wed, Apr 28, 2010 at 3:44 PM, Greg Larkin <glarkin at freebsd.org> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> doug schmidt wrote:
>>>> On Wed, Apr 28, 2010 at 1:44 PM, doug schmidt
>>>> <douglas.j.schmidt at gmail.com> wrote:
>>>>> On Wed, Apr 28, 2010 at 11:28 AM, doug schmidt
>>>>> <douglas.j.schmidt at gmail.com> wrote:
>>>>>> On Wed, Apr 28, 2010 at 10:23 AM, Greg Larkin <glarkin at freebsd.org> wrote:
>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>>> Hash: SHA1
>>>>>>>
>>>>>>> doug schmidt wrote:
>>>>>>>> On a 7.3-release box, I upgraded to php 5.3.2 + extensions. All seems
>>>>>>>> [Tue Apr 27 16:08:37 2010] [notice] child pid 37609 exit signal Bus error (10)
>>>>>>>>
>>>>>>> Check out this page:
>>>>>>> http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround
>>>>>> I'll give the script a try and see. If not, at least I know the
>>>>>> specific extension
>>>>>> and can test moving the order it is in.
>>>>>>
>>>>> I've tried using the script, then moving the session.so extension one
>>>>> after the other.
>>>>> Restarting apache each time and the same bus error.
>>>>>
>>>>> any other ideas?
>>>>>
>>>> I now have everything commented out in extensions.ini except for session.so
>>>> There is no bus error, so I'll test moving the extensions order some
>>>> more. Find it
>>>> sooner or later. Real pain, that the order on one box, does not matter
>>>> on another
>>>> box.
>>
>>> Do you get a core file anywhere from the Apache process?  It would be
>>> interesting to get a backtrace so you can figure out what module is
>>> causing the problem.
>>
>> Hi Greg,
>> Unfortunately, no core files anywhere.
>>
>> The problem looks like session.so and mysql.so
>>
>> With all extensions uncommented, session.so uncommented, mysql.so commented out
>> no bus error.
>>
>> All extensions uncommented, mysql.so uncommented, session.so commented out
>> no bus error.
>>
>> All extensions commented out, mysql.so commented out, session.so uncommented
>> no bus error.
>>
>> All extensions commented out, session.so commented out, mysql.so uncommented
>> no bus error.
>>
>> All extensions commented out, session.so and mysql.so uncommented
>> bus error.
>>
>> thanks.
>> doug
>
> Hi Doug,
>
> What happens if you swap the order of session.so and mysql.so and try
> the same tests?  From what I see on this page
> (http://forums.freebsd.org/archive/index.php/t-927.html), mysql.so
> should go before session.so.
>
> If that results in the same problems, that's when I start firing up the
> Apache process with truss to see what's called before the bus error.
> You can do that like so:
>
> truss -f -a -s 256 -o /tmp/apache.log /usr/local/sbin/httpd
>
> Then reproduce the bus error and stop the main Apache process.
> /tmp/apache.log may contain some clues about what the processes were
> doing before the crash, especially if you search for "php", "session" or
> "mysql" in the file.
>

Nice. we are in business. apc.so was in extensions.ini but the file was not
in the path. I installed pecl-APC. Also, there was a typo in extensions.ini
for pgsql

thanks for your help.
doug