Vincent Stoessel wrote: > > But no message like "Midgard: serving page" or "Midgard: serving blob"? > > the word "blob" does not appear in my error log, (OK, I did just clear > that log. i will keeping checking)
When LogLevel is set to debug, one of these two messages must appear or Midgard will have decided not to serve the request. It will log the cached page it is serving. Any messages between the translate_handler line and this message (inclusive) are interesting to me. > compliled the new version : still says it's trying to connect to localhost. > I used -Smydbserver Ah, that was only in display. I've fixed it. > [debug] select_db.h(87): [client ] Midgard: select_database reused open (midgard) > [debug] select_db.h(33): [client ] Midgard: select_database kept current database >midgard > [debug] mod_midgard.c(699): [client ] Midgard: regenerating > /var/midgardCache/hit/88.php: no cache entries > [debug] mod_midgard.c(996): [client ] Midgard: serving page >/var/midgardCache/hit/88.php > [debug] mod_midgard.c(851): [client ] midgard_translate_handler(latin1, > http://www.hitlist.com:80/images/fp6.jpg) > [debug] select_db.h(87): [client ] Midgard: select_database reused open (midgard) > [debug] select_db.h(33): [client ] Midgard: select_database kept current database >midgard > [debug] mod_midgard.c(699): [client ] Midgard: regenerating > /var/midgardCache/hit/88.php: no cache entries > [debug] mod_midgard.c(996): [client ] Midgard: serving page >/var/midgardCache/hit/88.php This was the line I was looking for. Page 88 is your rootpage, then? For the life of me, I can't find what causes this. I know how it gets to the root page: at the start of the uri parse it will assume the rootpage is found, but the first non-match against the uri should invalidate that. Looking into it. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
