Hello Matthew! >> I'm experiencing strange problems with libapache2-mod-auth-mysql. I >> personally experienced it only on one virtual host with Typo3 installed. >> But this may has nothing to say, maybe my customers did not complain >> yet. Here's what I get from the Apache2 error.log: >>> [Wed Aug 09 19:16:47 2006] [crit] [client x.x.x.x] configuration error: >>> couldn't check access. No groups file?: >>> /typo3/ext/phpmyadmin/modsub/thirdparty_db.gif, referer: >>> http://www.domain.tld/typo3/alt_menu.php > This isn't a message from m-a-mysql. From recollection, it comes from the > standard auth module.
Well but it has something to do with m-a-mysql?!? At least I'm using online m-a-mysql for securing directories. >> I don't get it every time I work in the backend of Typo3, just from time >> to time. Then I have to reload Apache2 and everything's fine again. Than >> it happens again, maybe one minute or even days later. > This is the weird bit. Perhaps m-a-mysql is failing to process for some > reason (MySQL server acting weird?) and declining, so it's falling back > to the standard auth module. Everything is ok with the MySQL server. Or let's say it this way: The MySQL server is mission critical because everything depends on it, e.g. Apache2, Postfix, SpamAssassin, AMaViS, Courier, etc. So I think I should see problems everywhere all the time. Forums like phpBB or Postfix produce many queries every second on the MySQL server, m-a-mysql only several queries per hour. > Very strange, though. If you turn the log level in Apache down to debug, > you should get a pretty comprehensive trace of what's being done; that > info might help pinpoint the cause of the trouble. I'll do that and click through the Typo3 backend and hope that the error accurs soon. As this is a live server with many paying customers on it I cannot do this very long. ;-) I'll be back with the result soon. >> I found a similar bug from 2004 on Google, bug # 287160, there the >> problem was with version 4.3.9-1, but I cannot see any clue. > That was originally, but the problem still exists in 4.3.9-2. I've got > to get around to fixing that, and I'd imagine that it'll solve the > problem for you too, actually. Can you try the fix described in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287160;msg=135 and see > if it does the job for you, too? Ah thank you for the link. But as written above: This is a live server and as our own policy we do not compile any packages. We only use "final" packages. Well, not the best idea to use a hybrid system with stable and unstable packages, but stable is sometimes really unusable for us. Regards, Martin
