LDAP auth' module not installing SQL schema upon install of module to Drupal 6.1.2 on centOS 5.3

After deselecting the module in the modules list, try opening the "Uninstall" tab and uninstall the module from there. After that try installing it again.

Thank you for the reply.

I did uninstall it. I then went back to the list tab & enabled it again after & hit save. I checked the permissions allowed me to administrate it & they are correct. I then checked to see if it was installed & it was not. I must be missing something, or my DB must be wonky, or something. I sure hope it is not me. Perhaps I am misunderstanding something & perhaps I can clear it up by asking this question: at exactly what moment does the SQL schema get installed? What action causes that to fire off? The reason I ask is that the "ldapauth" table does not exist in our DB. If I run update.php it goes through clean. If I run update.php & manually choose version 6000 from the list of versions of modules installed (to update) & hit update, it goes through clean & says "no queries run". So I guess I have a module I am either not enabling, or not installing, or not using correctly. Since it wont install.

So sorry to bother you.

I do thank you very VERY much for you time getting me past this hurdle

Thank you.

Jason

One more tidbit. I just removed the entire module directory from inside of /sites/all/modules/ & then re-downloaded the module from the drupal.org site & run "tar zxvf filename". I then changed the owner of the directory & all items inside of it to be apache to make sure that apache2 had full permissions on it. I then went back to the modules page, and, get this, it is already enabled. I didn't check it. I then checked the SYSTEM table inside of the DB but I dont see its record in that table (as I would expect). So, it is enabled but not in the system.

It doesn't seem to want me to check that ever so important "enable" box for the very first time.

Second tidbit, here is the result of uninstalling the module (pls see attached screen grab)

Thanks!

Should I try to fix this, or should I just manually run the SQL query to create the table with all fields correctly & just move on. (I would need the SQL query, of course, to do this)

The table should be created when you enable the module in the modules list.

From you comments I'm suspicious that your system thinks that the module is already enabled and therefore does not fire the install hook. Try clearing the cache.

miglius: thanks for hanging in there with me. Sorry this is such a pain. So, I run a "delete from cache******"
on each of the few tables inside the DB, and here are those results:

mysql> delete from cache;
Query OK, 4 rows affected (0.01 sec)

mysql> delete from cache_block;
Query OK, 0 rows affected (0.00 sec)

mysql> delete from cache_filter;
Query OK, 0 rows affected (0.00 sec)

mysql> delete from cache_form;
Query OK, 24 rows affected (0.01 sec)

mysql> delete from cache_menu;
Query OK, 10 rows affected (0.01 sec)

mysql> delete from cache_page;
Query OK, 0 rows affected (0.01 sec)

mysql> delete from cache_update;
Query OK, 1 row affected (0.01 sec)

..... I then went to modules & checked to see if the checkbox was checked for LDAP & it was not. Good. That's nice. I checked it & hit save. I thought about it for a second & returned the page with no errors. I checked the log, no errors. I checked the DB for the "ldapauth" table, which ought to have just been created (empty) and it is not there.

What do you think? Should I just run the SQL query on its own. I am happy to. I just font want to get painted in to a corner. But I suspect that future updates to to the module might let the update SQL query run against it & maybe I'd be OK. Then again maybe I ought to find out why it is doing this.

What do you think?

Thanks again.

Jason

I just thought of something ...... how is it that I can adjust the settings inside the LDAP module (under "Administer" section) but nothing is logged to the log? no errors? those tabs & those fields are supposed to write to the DB, but clearly are not, since the table does not exist in the DB. Wouldn't it complain it could not save?

It's hard to say. Maybe your system is messed up. Are you using a fresh drupal install?

well, fresh, not perfectly fresh, but VERY new, yes, only a few modules in there, very small site, few pages, only 2 admin's & the other guy is pretty sharp, I dont think he jacked it up (I suppose its possible; but doubtful), and all other modules work as advertised, then I got to this one and we went sideways. I guess I can try a fresh install for a sub-domain or some such something unimportant & install it over there & see what happens. At least that way it's the same server, but not the public site, and I can see what happens. I can dup' the mySQL db & point it at that. I supposed, hell, if it works, I can dump the new "ldapauth" table from over there & bring it in here & maybe even carry on my way. Like I said earlier, just didn't want to paint over some issue to hack it in to place & have it come back & bite me on the heel in a few months or years.

I would like to humbly suggest that your otherwise VERY nice piece of code have far more logging inside of it, maybe even a debug level of logging. If you or I could remove the comment marks from a few choice lines of code to see what it was doing, we might be able to readily spot the issue. As is, I cant see anything at all in the drupal log. I know that this suggestion is 100% self-serving at this point since I am the one who is jammed up right now, but consider it, it might serve everyone or you well in the future also, who knows.

I will post my results back here for the drupal community to have record.

Before I let you go for now, and thank you again, any more tips, tricks, advice, things I can try?

Thanks again.

Cheers.

Jason Sjöbeck

My suggestion is to try a ldap_integration dev version on a virgin drupal install. If it's workin, then there is some problems on your particular install. If it's not, then open the bug reports.