1 Reply Latest reply: Dec 28, 2010 2:10 PM by ilssac RSS

    Security Hotfix APSB10-04 Breaks our SOLR service

    ilssac Community Member
    ilssac Dec 17, 2010 8:35 AM

      We installed APSB10-04 when we built our new CF9 web servers this past spring.

       

      On our servers the Solr server has never worked.  The service will just immediately stop every time it is started with no notification or logging.

       

      Building a lab system a couple of weeks ago, I noticed that Solr stops working when applying the APSB10-04 Security Hotfix.

       

      I presume the problem is with the IP number in the properties node that we are instructed in the hot fix documentation.

      <Set name="Host"><SystemProperty naem="jetty.host" default="127.0.0.1"/></Set>

       

      The local loopback ip of 127.0.0.1 does not go anywhere on these servers.  But I also tried the boxes specific IP address to no good effect.

       

      Commenting out the line, and the Solr service will start just fine.  Added it with either 127.0.0.1 OR 10.104.106.39 and the Solr service will not start.

       

      Any suggestions appreciated

       

      Ian

      • 272 Views
      • Tags:
        • 1. Re: Security Hotfix APSB10-04 Breaks our SOLR service
          ilssac Community Member
          ilssac Dec 28, 2010 2:10 PM (in response to ilssac)

          I don't know how many times I looked at this, I even posted it here in the original post!  But there is a typo in this line:

           

          <Set name="Host"><SystemProperty naem="jetty.host" default="127.0.0.1"/></Set>

           

          Fixing "<SystemProperty naem" to "<SystemProperty name" fixed the problem on this server straight away.

           

          What was really missleading me was that both the development and production servers where suffering the same problem!  But it was a completely different and distinct typo on the production server causing the problem there.

           


          <Set name="port"><SystemProperty name="jetty.host" default="127.0.0.1"/></Set>

           

          Fixing '<Set name="port"' to '<Set name="host"' fixed the production server!

           

          Lesson Learned:  Cut and Paste WHENEVER POSSIBLE!