Re: dbd syntax

["ernst schoen-rene" <ernstsr@xxxxxxxxx>]

I have solved this problem.  
I am running fedora64 on amd64.  
mod_dbd with mysql simply doesn't work on my install of apache 2.2.10.  I installed 2.2.11 and it works, but there are elements that I think are under-documented or poorly documented.
First, the DBDParams command for mysql requires that you put in a port or a socket, even if they are the defaults.  It does not require you to put in a database name.  The DBDParams can be delimited by a number of characters including a comma, space and '|', but it doesn't mention this in the documentation.
Secondly, the function in mod_authn_dbd that compares passwords compares the password your sql statement returns with an ENCRYPTED password.  It does say this once in the documentation, but all the sql examples do not indicate this.  There is no documentation about how to produce a password using the same encryption that apache uses.  I had to change the code for mod_authn_dbd to just compare unencrypted passwords.  For my application, encryption doesn't matter, and I think it's sort of silly to encrypt passwords that are transmitted in plain text anyway.  Documentation on how to produce an encrypted password in one's sql command would be useful.

On Fri, Dec 26, 2008 at 5:06 PM, ernst schoen-rene <ernstsr@xxxxxxxxx> wrote:

I don't want a dbname param, because different servers ask different databases for passwords.  However, it doesn't make a difference if I do add a dbname param.
  Also, I really only have limited skill in C and compiling and running the entire apache server under a debugger seems daunting. It seems that the error_log and mysql log should give me enough information to correct whatever configuration error I have and then I could go from there, but it doesn't. I also am running sites on this machine.  I had to move machines and just assumed that mod_auth_mysql would work with the current version of apache.
   I wish the system returned more information.  I'm working on setting it up to use apr_dbd_open_ex instead of apr_dbd_open to see if I can get any error information there, but this is way more than I'm really capable of. 

On Fri, Dec 26, 2008 at 4:53 PM, Nick Kew <nick@xxxxxxxxxxxx> wrote:

ernst schoen-rene wrote:

Ah, thanks.  That's good to know.  I still cannot get this damn thing to
connect to the database, and I've been sticking bits of debug code in
mod_dbd and apr-util to no avail.
I use this:
DPDParams "host=localhost user=someuser pass=somepass"

Don't you want to add a dbname parameter there?

Apart from that, you might need to try running with -X
under a debugger (gdb/dbx/whatever) or under dtrace/strace.
Consult your local hack if necessary.

--
Nick Kew

---------------------------------------------------------------------
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