We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23478
    • 133 Posts
    Thanks very much for giving me some help wink

    Quote from: sottwell at Dec 08, 2006, 01:53 AM

    piwaille, this appears to be related to spiders crawling your site. They do this at regular intervals. In my case, it was the Inktomi search engine spider causing most of my problems,

    well ... I remember I did noticed Inktomi crawling my site wink
    I did search (not every but many) log with inktomi around 7:00 PM (before and after)... they all received an answer 200 = ok
    And I may have missed something ... but it crawled only the forum

    Quote from: sottwell at Dec 08, 2006, 01:53 AM

    because of a bug in the TemplateSwitcher plugin (well, actually it is in the messageQuit function, but the TemplateSwitcher was calling it when it really didn’t need to). Get your error logs and your access logs for that time period, and find out what files are getting a 500 error response at that exact time. They will look like what I posted earlier.

    all the 500 error I finded is due by a normal visitor :
    AGrenoble-257-1-72-152.w86-211.abo.wanadoo.fr www.parapentiste.info - [07/Dec/2006:14:54:05 +0100] "GET /forum/ HTTP/1.1" 500 610 "-" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X; fr) AppleWebKit/418.9 (KHTML, like Gecko) Safari/419.3"
    AGrenoble-257-1-72-152.w86-211.abo.wanadoo.fr www.parapentiste.info - [07/Dec/2006:14:54:18 +0100] "GET /forum/ HTTP/1.1" 200 12500 "-" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X; fr) AppleWebKit/418.9 (KHTML, like Gecko) Safari/419.3"
    

    He retryed and it work fine (answer = 200) ... and it is a MODx page shocked
    (but I may have not find all the 500 page althoug I use a search engine)

    Quote from: sottwell at Dec 08, 2006, 01:53 AM
    Are you using the TemplateSwitcher plugin?
    I’m not using it...
    I’ve got my one template based on liquidthemes !

    I gonna remove that plugin and see if it’s getting better wink
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      You can remove it if you like or just disable it, but if that’s not causing the problem then it’s something else. You’ve made double-sure that your configuration sets the not found and unauthorized pages to valid document IDs?

      Otherwise, what I did to track down the cause of my problems was to search the server error logs for the exact time of the event log messages, then find the same time in the access logs.

      This had an interesting side-effect of showing where all my broken image links were! Now I don’t have any more 404 errors because of bad links to background images in my CSS and silly stuff like that.

      I have often wished that the event log messages were a bit more informative.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 23478
        • 133 Posts
        Quote from: sottwell at Dec 08, 2006, 04:30 AM

        You can remove it if you like or just disable it, but if that’s not causing the problem then it’s something else. You’ve made double-sure that your configuration sets the not found and unauthorized pages to valid document IDs?
        removed ... and still the problem sad

        I don’t know how many errors ... since I have 858 pages and the last page is a lost connexion to database (but each every other error I’ve looked at was a "Too many forward..."
        configuration set is good ... these are 4 forum’s page I come here and eahc time I do receive taht answer and eahc time I give the page’s ID


        Quote from: sottwell at Dec 08, 2006, 04:30 AM

        Otherwise, what I did to track down the cause of my problems was to search the server error logs for the exact time of the event log messages, then find the same time in the access logs.
        I’ve already posted the apache log since I didn’t saw anything...
        I don’t know what to do more >:(
          • 23478
          • 133 Posts
          Well ...
          I do really thought this is a bug into SMF ...
          I think that now have the proof cool

          Into my SMF pages I do include that page : http://www.parapentiste.info/brevedujour.php
          it almost alwas work ... but no always !
          In SMF error log, I do have a lot of error where SMF tells me it can’t include that page !
          And almost every time it works.
          this page code is :
          <?php
          $path = dirname(__FILE__);
          include_once($path.'/modxapi.php');
          $modx = new MODxAPI();
          // connect to db and load settings
          $modx->connect();
          $modx->getSettings();
          //$html = $modx->getChunk('gabarit_defaut');
          // Menu-StyleSheet
          $html = $modx->runSnippet('Ditto', array(
          									'startID' => '2' ,
          									'summarize' => '1' ,
          									'displayArchive' => '0',
          									'total' => '20' ,
          									'commentschunk' => '' ,
          									'tpl' => 'forum_breve' ,
          									'paginate' => '0' ,
          									'alwaysshow' => '1'
          										));
          $html .= '<font size="2" face="Times New Roman"><a href="/breves.html">Voir les autres brêves</a></font>';
          
          $html = $modx->rewriteUrls($html);
          
          echo $html;
          ?>
          


          he 2 errors are correlated !

          I don’t know what cause the "too many forward attempts issue" but it appens from time to time !
            • 22303 MODX Staff
            • 10,725 Posts
            Sorry, but that’s most likely a problem with the "unofficial" MODxAPI add-on, which I will not support with 0.9.5 -- please publish any further requests for support on this issue to the support thread for that add-on to see if you can get the original author to support it.
              • 23478
              • 133 Posts
              Quote from: OpenGeek at Dec 12, 2006, 08:33 AM

              Sorry, but that’s most likely a problem with the "unofficial" MODxAPI add-on,

              I dont think so huh

              I reported my first problem on 17 november ...
              I’ve made test with MODxAPI since 14/11 but I haven’t publish any page using this before yesterday ... and the probability that s/o finds my sample page looks much too narrow as theyr was absolutly no link toward them.

              The only change (yesterday) is that I’ve puted that part into the index of my forum that make ~80.000 pages/week (that why I do have those 858 pages of "Too many forward attempts")
              Before yesterday, I did only receive ~50 pages of that error once or twice a week ... but MODx (without any MODxAPI published) was only servicing ~300 pages/week.
                • 22303 MODX Staff
                • 10,725 Posts
                I’m not following what you are saying at all. If you started using the MODxAPI add-on on 11/14/2006 and the first problem showed up on 11/17/2006, sure sounds related to me.
                  • 23478
                  • 133 Posts
                  Quote from: OpenGeek at Dec 12, 2006, 09:12 AM

                  I’m not following what you are saying at all. If you started using the MODxAPI add-on on 11/14/2006 and the first problem showed up on 11/17/2006, sure sounds related to me.

                  well I may miss one explanation : MODxAPI is only a php script that acts as an external librairy. Ther is not snippet to add, no plugins within MODx ...
                  it’s only full external.
                  So, when it is not called, I can not see how it could interact with MODx behavior.
                    • 23478
                    • 133 Posts
                    Hello

                    I’ve spent a part of the night thinking about all that.. I think I may have found a possible explanation.

                    First … You have to know that we are at the limit of our hosting (but we can’t afford a bigger one now). So I think we do overwhelmed our SQL engine. This is not a problem with SMf which is very robust … but listen that scenario:
                    When a visitor ask for a document (either index?id= or index), MODx trys to retrive that document with either the `id` or the `alias` index.
                    When retreived, you look at permission then you treat it (you look if it is alerady cached or you parse it)….
                    Now … imagine my SQL that is jammed. You ask for the document but you receive no answer (since SQL as gone away or is not responding). How do you treat it ? I think you may try to handle it as if it was either a 404 or a 401 ? (seems to be a 404 when I look at my logs)
                    Handling a 404 (or a 401) you try to
                    1/ look in database which docid is suitable for MODx’ answer
                    2/ retreive that doc form DB
                    3/ parse the doc …
                    but what if the SQL is still jammed ? You even can’t retreive the "not found" handler and your enter your infinite loop sad

                    So .. the conclusion now seems :
                    * my hosting is the primary cause
                    * MODx can’t handle thing when something goning wrong (sorry, I’ve made too much industriall application where it is normal that robustness is evident)

                    what can be done ?
                    - first, I hop the next OO database motor will be more robust … I’ve allready given some clue
                    - then You have to review how you handel db-query answer … not saying "yes" isn’t saying "no"… when you receive no document for one request … this is not (allways) bescause your facing a 404 but you may are facing a SQL error !
                    - When you’re facing a SQL error,
                    - you should avoid every error log that only jam the DB engine more.
                    - You could send (I the webmaster decided to) an email for telling the situation
                    - You should retreive from files (not from DB) the correct text to display (Sorry unable to complete the request there was a problem with DB engine) that could be translated
                    - You event could display a static HTML file
                    All that possibilities should be placed into a configuration file (not DB)
                      • 22303 MODX Staff
                      • 10,725 Posts
                      <self-censorship>
                      pre-coffee reply removed
                      </self-censorship>

                      Please, remove the MODxAPI you are using and if the problem still persists, feel free to post some more about it. And again there is no infinite loop! It stops after the 3rd loop max per request to avoid just such flooding. Whatever is happening is a problem with your configuration or with a missing file that is being expected very often. I wouldn’t be surprised if it was a rewrite rule conflict causing an infinite loop if that’s what you are still experiencing...