More progress. I can now see traffic going out and coming back from the sql server for authentication requests but they are failing some how and I still get a seg fault when this happens. What type of "(encrypted password)" does this support? Is there a way to set it so it automatically succeeds just as a test? Thanks. Danie Qian wrote: > > ----- Original Message ----- From: "Daniel Campbell" <campbell@xxxxxxx> > To: <users@xxxxxxxxxxxxxxxx> > Sent: Tuesday, November 20, 2007 10:48 PM > Subject: Re: dbd mysql segmentation fault in 2.2.6 > > >> Well I take that back some what. It still seg faults but only once >> per request instead of a continuous loop. Oh well....I keep plugging >> away at it...any more tips would be greatly appreciated... >> >> Daniel Campbell wrote: >>> FINALLY, I found the problem and it was so simple.....I could shoot >>> myself. I forgot DBDPersist off in the conf file. This was causing >>> the seg faults. >>> > > Looks like you are missing one option in your configuration: --enable-dbd > > To take advantage of dbd you actually need to turn DBDPersist on and > use --with-mpm=worker configuration option. But for now try adding > --enable-dbd option first to see if it gets rid of your errors. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server > Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|