Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 23943112AA for ; Thu, 18 Sep 2014 10:03:13 +0000 (UTC) Received: (qmail 76353 invoked by uid 500); 18 Sep 2014 10:03:13 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 76323 invoked by uid 500); 18 Sep 2014 10:03:13 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 76300 invoked by uid 99); 18 Sep 2014 10:03:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 10:03:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of daddywri@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 10:02:47 +0000 Received: by mail-qc0-f182.google.com with SMTP id i8so198814qcq.27 for ; Thu, 18 Sep 2014 03:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=NpaISIwyD3GojZJ4lJsuVzAtp8MoD7ljdcbXMt0UtFg=; b=sLG3VFCNZrCjxuAHN7NpZlTm7jEpEZO9d61eli90VabSZDLp0PIZ+K++PMcuRnQAbc pm0zI4ght+yvnbbbj3oJfMccWCN11jAR/UaRIJbEpSGaJKHJh8+VZorJeECnzQTvaRqa gAdDb9WPvERZKuQvaSE+MQfWFh7TYMbsEn4k2CRDBSTRNdVL9OHKdOdbfadWHxJCeG8j Zomk9E0v1QP4G7lcViELAslnfdxL4Xt5tTmBIGDlLB1KNCnrYGVXBueYyZ3YPeMiwQQp mvqsF6alC34g+T8StzOjHosYtkHNEilF4erYV5KnaMAn1cf8XTKGyFq7WuximywgPiU9 U//A== MIME-Version: 1.0 X-Received: by 10.236.8.69 with SMTP id 45mr2863160yhq.19.1411034565613; Thu, 18 Sep 2014 03:02:45 -0700 (PDT) Received: by 10.170.61.149 with HTTP; Thu, 18 Sep 2014 03:02:45 -0700 (PDT) In-Reply-To: <541AA4B0.5000004@usit.uio.no> References: <541AA213.5080206@usit.uio.no> <541AA4B0.5000004@usit.uio.no> Date: Thu, 18 Sep 2014 06:02:45 -0400 Message-ID: Subject: Re: [VOTE] Release Apache ManifoldCF 1.7.1, RC1 From: Karl Wright To: dev Content-Type: multipart/alternative; boundary=089e0163544c0ca0910503541646 X-Virus-Checked: Checked by ClamAV on apache.org --089e0163544c0ca0910503541646 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Erlend, MCF caches the robots.txt file in the database, which it considers valid for 1 hour. I'll look at the logs and thread dump and let you know if this is a locking issue or something else. Please stand by. Karl On Thu, Sep 18, 2014 at 5:24 AM, Erlend Gar=C3=A5sen wrote: > > I tried to restart the job dealing with www.duo.no on our test server, > but it does not seem to touch the robots.txt file at all. That's the reas= on > why it's able to continue. Both servers are set up to obey the rules of > such files. > > Erlend > > > On 18.09.14 11:12, Erlend Gar=C3=A5sen wrote: > >> >> I'm facing the same problems with robot.txt files using RC1, so maybe >> this is another issue we have to fix. Can you please try to fetch the >> host below? For some odd reason, it seems that MCF on our test server >> can handle it. >> >> This is exactly the same that happened when I started MCF (referring to >> my previous post) after I had deployed RC1: >> 09-18-2014 11:02:14.400 robots parse https:www.duo.uio.no:443 >> ERRORS 0 3 Unknown robots.txt line: '=3D=3D=3D=3D' >> >> No activity after this error. >> >> Here's the robots.txt file: >> https://www.duo.uio.no/robots.txt >> >> This is the content of manifoldcf.log after the startup: >> WARN 2014-09-18 11:02:14,401 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': '=3D=3D=3D=3D' >> WARN 2014-09-18 11:02:14,401 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': ' The contents of >> this file are subject to the license and copyright' >> WARN 2014-09-18 11:02:14,402 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': ' detailed in the >> LICENSE and NOTICE files at the root of the source' >> WARN 2014-09-18 11:02:14,402 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': ' tree and available >> online at' >> WARN 2014-09-18 11:02:14,402 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': ' >> http://www.dspace.org/license/' >> WARN 2014-09-18 11:02:14,402 (Worker thread '19') - Web: Unknown >> robots.txt line from 'https:www.duo.uio.no:443': '=3D=3D=3D=3D' >> >> E >> >> >> On 18.09.14 03:12, Karl Wright wrote: >> >>> Please vote on whether to release Apache ManifoldCF 1.7.1, RC1. >>> >>> This release fixes a number of critical issues, as well as a number of >>> user >>> priorities, most notably: >>> >>> - A bad Zookeeper support issue, which made locking support fail when >>> Zookeeper connections got lost and then restored; >>> - The Alfresco connector, which was nonfunctional in both MCF 1.6 and >>> 1.7; >>> - Solr Cloud support, which had ceased working due to changes to SolrJ; >>> - Non-null connector components caused failure; >>> - PostgreSQL queries not performing well. >>> >>> The complete list of included fixes can be found at: >>> >>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1. >>> 7.1-RC1/CHANGES.txt >>> >>> >>> The release candidate can be downloaded from: >>> >>> http://people.apache.org/~kwright/apache-manifoldcf-1.7.1 >>> >>> There is a tag at: >>> >>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.7.1-RC1 >>> >>> Thanks, >>> Karl >>> >>> >> > --089e0163544c0ca0910503541646--