httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Golubev <an...@engec.ru>
Subject Re[2]: apache 2.2 crashes at the start time in mod_dbd.c then preparing AuthDBDUserPWQuery
Date Thu, 20 Jul 2006 19:52:06 GMT
Hello Nick,

Here is here the minimal complete config, which crashes the server:

DBDriver mysql
DBDParams "dbname=Users user=auther passreplace=IrjkfN3"
DBDMin 1
DBDKeep 2
DBDMax 10
DBDExptime 60

ServerRoot /usr/local/apache

Listen 80

User nobody
Group nobody

ServerAdmin anton@virtweb.engec.ru
NameVirtualHost 85.142.33.11

<VirtualHost 85.142.33.11>
DocumentRoot /home/ivc2/public_html

    <Directory /home/ivc2/public_html>

        AuthType Basic
        AuthName 'ADMIN ZONE'
        AuthBasicProvider dbd

        AuthDBDUserPWQuery "select PASS from Users where LOGIN= %s"

    </Directory>

</VirtualHost>


Another backtrace:

(gdb) run -f /usr/local/apache/conf/httpd-mini.conf
Starting program: /usr/local/apache2_2/bin/httpd -f /usr/local/apache/conf/httpd-mini.conf
[Thread debugging using libthread_db enabled]
[New Thread -1208047936 (LWP 449)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208047936 (LWP 449)]
ap_dbd_prepare (s=0x0, query=0x9aa64f8 "select PASS from Users where LOGIN= %s", label=0x9aa64f8
"select PASS from Users where LOGIN= %s") at mod_dbd.c:149
149         prepared->next = svr->prepared;
(gdb) bt
#0  ap_dbd_prepare (s=0x0, query=0x9aa64f8 "select PASS from Users where LOGIN= %s", label=0x9aa64f8
"select PASS from Users where LOGIN= %s")
    at mod_dbd.c:149
#1  0x08080415 in authn_dbd_prepare (cmd=0xbfef6c70, cfg=0x9aa64f0, query=0x9aa64f8 "select
PASS from Users where LOGIN= %s") at mod_authn_dbd.c:70
#2  0x0807880b in invoke_cmd (cmd=0x80d30a0, parms=0xbfef6c70, mconfig=0x9aa64f0, args=0x9a937a0
"") at config.c:873
#3  0x08079075 in ap_walk_config (current=0x9a93758, parms=0xbfef6c70, section_vector=0x9aa5fb0)
at config.c:1141
#4  0x08070d09 in dirsection (cmd=0xbfef6c70, mconfig=0x9aa5a88, arg=0x9aa6256 "") at core.c:1865
#5  0x0807880b in invoke_cmd (cmd=0x80d0a80, parms=0xbfef6c70, mconfig=0x9aa5a88, args=0x9a93670
"/home/ivc2/public_html>") at config.c:873
#6  0x08079075 in ap_walk_config (current=0x9a93650, parms=0xbfef6c70, section_vector=0x9aa56f0)
at config.c:1141
#7  0x08071553 in virtualhost_section (cmd=0xbfef6c70, dummy=0x9a8efe8, arg=0x9a935e8 "85.142.33.11>")
at core.c:2206
#8  0x0807880b in invoke_cmd (cmd=0x80d0ab0, parms=0xbfef6c70, mconfig=0x9a8efe8, args=0x9a935e8
"85.142.33.11>") at config.c:873
#9  0x08079075 in ap_walk_config (current=0x9a935c8, parms=0xbfef6c70, section_vector=0x9a8df00)
at config.c:1141
#10 0x08079ace in ap_process_config_tree (s=0x9a4e570, conftree=0x9a932b8, p=0x9a430a8, ptemp=0x9a8b240)
at config.c:1743
#11 0x08067eeb in main (argc=3, argv=0xbfef6dd4) at main.c:621
(gdb)


I'm wondering how could I catch it with so many people luckily using
this feature around? Otherwise I would be proud to be the first one! :)


Greets,
Anton Golubev
ENGECON
St. Petersburg
Russia


Mime
View raw message