From owner-freebsd-ports-bugs@freebsd.org Wed Jul 15 23:24:45 2015 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D68599A232C for ; Wed, 15 Jul 2015 23:24:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 99A9E1D60 for ; Wed, 15 Jul 2015 23:24:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6FNOjnZ014906 for ; Wed, 15 Jul 2015 23:24:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 201455] textproc/apache-solr does not start after upgrade from 4.10.4 to 5.2.1 Date: Wed, 15 Jul 2015 23:24:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: paul@gromit.dlib.vt.edu X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 23:24:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201455 paul@gromit.dlib.vt.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul@gromit.dlib.vt.edu --- Comment #1 from paul@gromit.dlib.vt.edu --- As of Solr 5, the startup mechanism has changed dramatically. In the "Major Changes from Solr 4 to Solr 5" page, https://cwiki.apache.org/confluence/display/solr/Major+Changes+from+Solr+4+to+Solr+5 there is a "Solr is a Standalone Server" section that explains that Solr 5 is meant to be a standalone Java application now. It now includes a bin/ directory in the distribution that has a "solr" script that is used to start, stop, and otherwise interact with Solr 5. This bin/ directory (along with the example server/ directory) are missing from the current installed FreeBSD textproc/apache-solr port. Furthermore, in the "Upgrading from Older Versions of Solr" section of the "Upgrading Solr" page, https://cwiki.apache.org/confluence/display/solr/Upgrading+Solr it says the following: "Solr has internally been upgraded to use Jetty 9. See SOLR-4839 for full details, but there are a few key details all Solr users should know when upgrading: - It is no longer possible to run "java -jar start.jar" from inside the server directory. The bin/solr script is the only supported way to run Solr. This is necessary to support HTTP and HTTPS modules in Jetty which can be selectively enabled by the bin/solr scripts. - The way SSL support is configured has been changed. Please refer to the Enabling SSL section in the Solr Reference Guide for complete details." So, running via "start.jar" likely won't fix the issue in a proper way. (The start.jar JAR file is in the missing server/ directory of the Solr 5.2.1 distribution.) I did test starting and stopping Solr 5 via the bin/solr script provided in the distribution and it did appear to work for me. That might be a good starting point for updating the rc.d script. Note, however, I haven't checked the bin/solr script for dependencies. At the very least, it appears to use bash and implies it also needs curl... -- You are receiving this mail because: You are the assignee for the bug.