GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- HP Apache-based PHP/mod_perl/mysql SIGSEGV
Operating System - HP-UX
1849660
Members
7709
Online
104044
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2005 05:04 AM
01-04-2005 05:04 AM
HP Apache-based PHP/mod_perl/mysql SIGSEGV
Hi All,
I´m experiencing a problem with the HP Apache-based Web server when I include both PHP and mod_perl modules. The problem is that the httpd child process dies with segmentation fault (11)
Here is a backtrace I obtained with gdb:
Program received signal SIGSEGV, Segmentation fault
si_code: 0 - SEGV_UNKNOWN - Unknown Error.
[Switching to thread 3 (system thread 22785)]
0xc6595c1c in _db_enter_+0x8c () from /opt/hpws/apache/modules/libphp4.so
(gdb) ba
#0 0xc6595c1c in _db_enter_+0x8c () from /opt/hpws/apache/modules/libphp4.so
#1 0xc6585e18 in mysql_ping+0x70 () from /opt/hpws/apache/modules/libphp4.so
#2 0xc60a1e18 in XS_DBD__mysql__db_ping+0x1a8 ()
from /opt/perl/lib/site_perl/5.8.0/PA-RISC1.1-thread-multi/auto/DBD/mysql/mys
ql.sl
#3 0xc5fe5a54 in XS_DBI_dispatch+0x20e4 ()
from /opt/perl/lib/site_perl/5.8.0/PA-RISC1.1-thread-multi/auto/DBI/DBI.sl
#4 0xc622e2d4 in Perl_pp_entersub+0x53c ()
from /opt/hpws/apache/modules/mod_perl.so
#5 0xc6225db4 in Perl_runops_standard+0x44 ()
from /opt/hpws/apache/modules/mod_perl.so
#6 0xc6193230 in S_call_body+0x58 () from /opt/hpws/apache/modules/mod_perl.so
#7 0xc6192eec in Perl_call_sv+0x4f4 ()
from /opt/hpws/apache/modules/mod_perl.so
#8 0xc6172e34 in modperl_callback+0x324 ()
from /opt/hpws/apache/modules/mod_perl.so
#9 0xc61735d4 in modperl_callback_run_handlers+0x394 ()
from /opt/hpws/apache/modules/mod_perl.so
#10 0xc6173758 in modperl_callback_per_dir+0x40 ()
from /opt/hpws/apache/modules/mod_perl.so
#11 0xc616c300 in modperl_response_handler_run+0x40 ()
from /opt/hpws/apache/modules/mod_perl.so
#12 0xc616c81c in modperl_response_handler_cgi+0x1ac ()
from /opt/hpws/apache/modules/mod_perl.so
---Type to continue, or q to quit---
#13 0x444f4 in ap_run_handler+0x74 ()
#14 0x44f68 in ap_invoke_handler+0xf0 ()
#15 0x3ce40 in ap_process_request+0x48 ()
#16 0x36594 in ap_process_http_connection+0x74 ()
#17 0x51bf4 in ap_run_process_connection+0x74 ()
#18 0x52154 in ap_process_connection+0x64 ()
#19 0x3e87c in process_socket+0xb4 ()
#20 0x3f5ac in worker_thread+0x1fc ()
#21 0xc5def6cc in dummy_worker+0x24 () from /opt/hpws/apache/lib/libapr-0.sl.9
#22 0xc0319f60 in __pthread_create_system+0x420 () from /usr/lib/libpthread.1
The problem affects only the application running with mod_perl. It doesn't matter if the PHP application is accessed before or not.
I also find odd that the problem is reported in libphp4.so even though no PHP code is being used.
I´ll appreciate your help in solving this.
Regards,
Mar
I´m experiencing a problem with the HP Apache-based Web server when I include both PHP and mod_perl modules. The problem is that the httpd child process dies with segmentation fault (11)
Here is a backtrace I obtained with gdb:
Program received signal SIGSEGV, Segmentation fault
si_code: 0 - SEGV_UNKNOWN - Unknown Error.
[Switching to thread 3 (system thread 22785)]
0xc6595c1c in _db_enter_+0x8c () from /opt/hpws/apache/modules/libphp4.so
(gdb) ba
#0 0xc6595c1c in _db_enter_+0x8c () from /opt/hpws/apache/modules/libphp4.so
#1 0xc6585e18 in mysql_ping+0x70 () from /opt/hpws/apache/modules/libphp4.so
#2 0xc60a1e18 in XS_DBD__mysql__db_ping+0x1a8 ()
from /opt/perl/lib/site_perl/5.8.0/PA-RISC1.1-thread-multi/auto/DBD/mysql/mys
ql.sl
#3 0xc5fe5a54 in XS_DBI_dispatch+0x20e4 ()
from /opt/perl/lib/site_perl/5.8.0/PA-RISC1.1-thread-multi/auto/DBI/DBI.sl
#4 0xc622e2d4 in Perl_pp_entersub+0x53c ()
from /opt/hpws/apache/modules/mod_perl.so
#5 0xc6225db4 in Perl_runops_standard+0x44 ()
from /opt/hpws/apache/modules/mod_perl.so
#6 0xc6193230 in S_call_body+0x58 () from /opt/hpws/apache/modules/mod_perl.so
#7 0xc6192eec in Perl_call_sv+0x4f4 ()
from /opt/hpws/apache/modules/mod_perl.so
#8 0xc6172e34 in modperl_callback+0x324 ()
from /opt/hpws/apache/modules/mod_perl.so
#9 0xc61735d4 in modperl_callback_run_handlers+0x394 ()
from /opt/hpws/apache/modules/mod_perl.so
#10 0xc6173758 in modperl_callback_per_dir+0x40 ()
from /opt/hpws/apache/modules/mod_perl.so
#11 0xc616c300 in modperl_response_handler_run+0x40 ()
from /opt/hpws/apache/modules/mod_perl.so
#12 0xc616c81c in modperl_response_handler_cgi+0x1ac ()
from /opt/hpws/apache/modules/mod_perl.so
---Type
#13 0x444f4 in ap_run_handler+0x74 ()
#14 0x44f68 in ap_invoke_handler+0xf0 ()
#15 0x3ce40 in ap_process_request+0x48 ()
#16 0x36594 in ap_process_http_connection+0x74 ()
#17 0x51bf4 in ap_run_process_connection+0x74 ()
#18 0x52154 in ap_process_connection+0x64 ()
#19 0x3e87c in process_socket+0xb4 ()
#20 0x3f5ac in worker_thread+0x1fc ()
#21 0xc5def6cc in dummy_worker+0x24 () from /opt/hpws/apache/lib/libapr-0.sl.9
#22 0xc0319f60 in __pthread_create_system+0x420 () from /usr/lib/libpthread.1
The problem affects only the application running with mod_perl. It doesn't matter if the PHP application is accessed before or not.
I also find odd that the problem is reported in libphp4.so even though no PHP code is being used.
I´ll appreciate your help in solving this.
Regards,
Mar
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP