Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-175

Wrong configuration could cause a core

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.0.3.GA, 1.1.0.Beta1
    • Fix Version/s: 1.0.4.GA, 1.1.0.Final
    • Component/s: None
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Just makes and the <Proxy/> stuff to httpd.conf and make a request to httpd and you get something like the following:
      [Tue Jul 06 11:46:06 2010] [notice] child pid 27522 exit signal Segmentation fault (11), possible coredump in /home/jfclere/APACHE-2.2.x

      Show
      Just makes and the <Proxy/> stuff to httpd.conf and make a request to httpd and you get something like the following: [Tue Jul 06 11:46:06 2010] [notice] child pid 27522 exit signal Segmentation fault (11), possible coredump in /home/jfclere/APACHE-2.2.x
    • Workaround Description:
      Hide

      Remove the:
      <Proxy balancer://mycluster>
      BalancerMember ajp://10.33.144.3:8009 loadfactor=1
      </Proxy>

      Show
      Remove the: <Proxy balancer://mycluster> BalancerMember ajp://10.33.144.3:8009 loadfactor=1 </Proxy>
    • Estimated Difficulty:
      Low

      Description

      1. That creates a core...
        <Proxy balancer://mycluster>
        BalancerMember ajp://10.33.144.3:8009 loadfactor=1
        </Proxy>
        ProxyPass / balancer://mycluster/

      Of course having entries describing the node is not what mod_cluster is done for....

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jfclere Jean-Frederic Clere
                Reporter:
                jfclere Jean-Frederic Clere
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: