starting up solr automatically
Hey all,
I'm pretty new to solr. I'm installing it on an amazon linux (rpm based)
ec2 instance and have it running. I even have nutch feeding it pages from
a crawl. I'm very happy about that.
I want solr to start on a reboot and am following the instructions at
http://wiki.apache.org/solr/SolrJetty#Starting
I'm using solr 4.5.1 and when I check the jetty version I get this
java -jar start.jar --version
Active Options: [default, *]
Version Information on 17 entries in the classpath.
Note: order presented here is how they would appear on the classpath.
changes to the OPTIONS=[option,option,...] command line option will
be reflected here.
0:(dir) | ${jetty.home}/resources
1: 8.1.10.v20130312 | ${jetty.home}/lib/jetty-xml-8.1.10.v20130312.jar
2: 3.0.0.v201112011016 | ${jetty.home}/lib/servlet-api-3.0.jar
3: 8.1.10.v20130312 | ${jetty.home}/lib/jetty-http-8.1.10.v20130312.jar
4: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-continuation-8.1.10.v20130312.jar
5: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-server-8.1.10.v20130312.jar
6: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-security-8.1.10.v20130312.jar
7: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-servlet-8.1.10.v20130312.jar
8: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-webapp-8.1.10.v20130312.jar
9: 8.1.10.v20130312 |
${jetty.home}/lib/jetty-deploy-8.1.10.v20130312.jar
10:1.6.6 | ${jetty.home}/lib/ext/jcl-over-slf4j-1.6.6.jar
11:1.6.6 | ${jetty.home}/lib/ext/jul-to-slf4j-1.6.6.jar
12: 1.2.16 | ${jetty.home}/lib/ext/log4j-1.2.16.jar
13:1.6.6 | ${jetty.home}/lib/ext/slf4j-api-1.6.6.jar
14:1.6.6 | ${jetty.home}/lib/ext/slf4j-log4j12-1.6.6.jar
15: 8.1.10.v20130312 | ${jetty.home}/lib/jetty-util-8.1.10.v20130312.jar
16: 8.1.10.v20130312 | ${jetty.home}/lib/jetty-io-8.1.10.v20130312.jar
the instructions reference a jetty.sh script for version 6 and a different
one for 7. Does the version 7 one work with jetty 8? If not where can I get
the one for version 8?
BTW - this is just the standard install of solr from the gzip file.
thanks in advance for your help.
--
Eric Palmer
U of Richmond
Re: starting up solr automatically
thanks greg
I got it starting but the collection file is not avail. I will use the
script that you gave the url for and the env settings. Thanks
On Wed, Dec 4, 2013 at 4:26 PM, Greg Walters wrote:
> I almost forgot, you'll need a file to setup the environment a bit too:
>
> **
> JAVA_HOME=/usr/java/default
> JAVA_OPTIONS="-Xmx15g \
> -Xms15g \
> -XX:+PrintGCApplicationStoppedTime \
> -XX:+PrintGCDateStamps \
> -XX:+PrintGCDetails \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseParNewGC \
> -XX:+UseTLAB \
> -XX:+CMSParallelRemarkEnabled \
> -XX:+CMSScavengeBeforeRemark \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=50 \
> -XX:CMSWaitDuration=30 \
> -XX:GCTimeRatio=40 \
> -Xloggc:/tmp/solr45_gc.log \
> -Dbootstrap_conf=true \
> -Dbootstrap_confdir=/var/lib/answers/atlascloud/solr45/solr/wa-en-collection_1/conf/
> \
> -Dcollection.configName=wa-en-collection \
> -DzkHost= \
> -DnumShards= \
> -Dsolr.solr.home=/var/lib/answers/atlascloud/solr45/solr/ \
> -Dlog4j.configuration=file:///var/lib/answers/atlascloud/solr45/resources/log4j.properties
> \
> -Djetty.port=9101 \
> $JAVA_OPTIONS"
> JETTY_HOME=/var/lib/answers/atlascloud/solr45/
> JETTY_USER=tomcat
> JETTY_LOGS=/var/lib/answers/atlascloud/solr45/logs
> **
>
> On Dec 4, 2013, at 3:21 PM, Greg Walters wrote:
>
> > I found the instructions and scripts on that page to be unclear and/or
> not work. Here's the script I've been using for solr 4.5.1:
> https://gist.github.com/gregwalters/7795791 Do note that you'll have to
> change a couple of paths to get things working correctly.
> >
> > Thanks,
> > Greg
> >
> > On Dec 4, 2013, at 3:15 PM, Eric Palmer wrote:
> >
> >> Hey all,
> >>
> >> I'm pretty new to solr. I'm installing it on an amazon linux (rpm
> based)
> >> ec2 instance and have it running. I even have nutch feeding it pages
> from
> >> a crawl. I'm very happy about that.
> >>
> >> I want solr to start on a reboot and am following the instructions at
> >> http://wiki.apache.org/solr/SolrJetty#Starting
> >>
> >> I'm using solr 4.5.1 and when I check the jetty version I get this
> >>
> >> java -jar start.jar --version
> >> Active Options: [default, *]
> >> Version Information on 17 entries in the classpath.
> >> Note: order presented here is how they would appear on the classpath.
> >> changes to the OPTIONS=[option,option,...] command line option will
> >> be reflected here.
> >> 0:(dir) | ${jetty.home}/resources
> >> 1: 8.1.10.v20130312 |
> ${jetty.home}/lib/jetty-xml-8.1.10.v20130312.jar
> >> 2: 3.0.0.v201112011016 | ${jetty.home}/lib/servlet-api-3.0.jar
> >> 3: 8.1.10.v20130312 |
> ${jetty.home}/lib/jetty-http-8.1.10.v20130312.jar
> >> 4: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-continuation-8.1.10.v20130312.jar
> >> 5: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-server-8.1.10.v20130312.jar
> >> 6: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-security-8.1.10.v20130312.jar
> >> 7: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-servlet-8.1.10.v20130312.jar
> >> 8: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-webapp-8.1.10.v20130312.jar
> >> 9: 8.1.10.v20130312 |
> >> ${jetty.home}/lib/jetty-deploy-8.1.10.v20130312.jar
> >> 10:1.6.6 |
> ${jetty.home}/lib/ext/jcl-over-slf4j-1.6.6.jar
> >> 11:1.6.6 | ${jetty.home}/lib/ext/jul-to-slf4j-1.6.6.jar
> >> 12: 1.2.16 | ${jetty.home}/lib/ext/log4j-1.2.16.jar
> >> 13:1.6.6 | ${jetty.home}/lib/ext/slf4j-api-1.6.6.jar
> >> 14: 1.6.6 | ${jetty.home}/lib/ext/slf4j-log4j12-1.6.6.jar
> >> 15: 8.1.10.v20130312 |
> ${jetty.home}/lib/jetty-util-8.1.10.v20130312.jar
> >> 16: 8.1.10.v20130312 |
> ${jetty.home}/lib/jetty-io-8.1.10.v20130312.jar
> >>
> >> the instructions reference a jetty.sh script for version 6 and a
> different
> >> one for 7. Does the version 7 one work with jetty 8? If not where can I
> get
> >> the one for version 8?
> >>
> >> BTW - this is just the standard install of solr from the gzip file.
> >>
> >> thanks in advance for your help.
> >>
> >> --
> >> Eric Palmer
> >> U of Richmond
> >
>
>
--
Eric Palmer
Re: starting up solr automatically
Greg or anyone that can help, when I try to start jetty as a service
sudo service jetty start
I get this error
** ERROR: JETTY_HOME not set, you need to set it or install in a standard
location
same for
sudo service jetty stop
sudo service jetty check
etc
I have a file here and the permissions look right
ls -al /etc/default/
total 20
drwxr-xr-x 2 root root 4096 Dec 5 19:18 .
drwxr-xr-x 68 root root 4096 Dec 5 19:03 ..
-rwxr-xr-x 1 root root 317 Dec 5 19:18 jetty
the contents if the jetty file is
JAVA_HOME=/usr/lib/jvm/jre
JETTY_HOME=/home/ec2-user/solr/solr-4.5.1/example/
JETTY_USER=ec2-user
JETTY_LOGS=/home/ec2-user/solr/solr-4.5.1/example/logs
JAVA_OPTIONS="\
-Dsolr.solr.home=/home/ec2-user/solr/solr-4.5.1/example/solr/ \
-Xms1g \
-Djetty.port=8983 \
-Dcollection.configName=collection1 \
$JAVA_OPTIONS"
Any ideas what I should check?
Eric P
thanks in advance
On Thu, Dec 5, 2013 at 11:28 AM, Greg Walters wrote:
> Alan,
>
> Yes, that's intentional. There's two reasons for this:
>
> 1: We make schema changes frequently (more frequently than I like)
> 2: So far as I've noticed, it doesn't hurt anything and covers my butt
> when I've got to clear out all the solr related data from ZK while testing
>
> Thanks,
> Greg
>
> On Dec 5, 2013, at 5:53 AM, Alan Woodward wrote:
>
> > Hi Greg,
> >
> > It looks as though your script below will bootstrap a collection
> configuration every time Solr is restarted, which probably isn't what you
> want to do? You only need to upload the config once.
> >
> > Alan Woodward
> > www.flax.co.uk
> >
> >
> > On 4 Dec 2013, at 21:26, Greg Walters wrote:
> >
> >> I almost forgot, you'll need a file to setup the environment a bit too:
> >>
> >> **
> >> JAVA_HOME=/usr/java/default
> >> JAVA_OPTIONS="-Xmx15g \
> >> -Xms15g \
> >> -XX:+PrintGCApplicationStoppedTime \
> >> -XX:+PrintGCDateStamps \
> >> -XX:+PrintGCDetails \
> >> -XX:+UseConcMarkSweepGC \
> >> -XX:+UseParNewGC \
> >> -XX:+UseTLAB \
> >> -XX:+CMSParallelRemarkEnabled \
> >> -XX:+CMSScavengeBeforeRemark \
> >> -XX:+UseCMSInitiatingOccupancyOnly \
> >> -XX:CMSInitiatingOccupancyFraction=50 \
> >> -XX:CMSWaitDuration=30 \
> >> -XX:GCTimeRatio=40 \
> >> -Xloggc:/tmp/solr45_gc.log \
> >> -Dbootstrap_conf=true \
> >>
> -Dbootstrap_confdir=/var/lib/answers/atlascloud/solr45/solr/wa-en-collection_1/conf/
> \
> >> -Dcollection.configName=wa-en-collection \
> >> -DzkHost= \
> >> -DnumShards= \
> >> -Dsolr.solr.home=/var/lib/answers/atlascloud/solr45/solr/ \
> >>
> -Dlog4j.configuration=file:///var/lib/answers/atlascloud/solr45/resources/log4j.properties
> \
> >> -Djetty.port=9101 \
> >> $JAVA_OPTIONS"
> >> JETTY_HOME=/var/lib/answers/atlascloud/solr45/
> >> JETTY_USER=tomcat
> >> JETTY_LOGS=/var/lib/answers/atlascloud/solr45/logs
> >> **
> >>
> >> On Dec 4, 2013, at 3:21 PM, Greg Walters
> wrote:
> >>
> >>> I found the instructions and scripts on that page to be unclear and/or
> not work. Here's the script I've been using for solr 4.5.1:
> https://gist.github.com/gregwalters/7795791 Do note that you'll have to
> change a couple of paths to get things working correctly.
> >>>
> >>> Thanks,
> >>> Greg
> >>>
> >>> On Dec 4, 2013, at 3:15 PM, Eric Palmer wrote:
> >>>
> >>>> Hey all,
> >>>>
> >>>> I'm pretty new to solr. I'm installing it on an amazon linux (rpm
> based)
> >>>> ec2 instance and have it running. I even have nutch feeding it pages
> from
> >>>> a crawl. I'm very happy about that.
> >>>>
> >>>> I want solr to start on a reboot and am following the instructions at
> >>>> http://wiki.apache.org/solr/SolrJetty#Starting
> >>>>
> >>>> I'm using solr 4.5.1 and when I check the jetty version I get this
> >>>>
> >>>> java -jar start.jar --version
> >>>> Active Options: [default, *]
> >>>> Version Information on 17 entries in the classpath.
> >>>> Note: order presented here is how they would appear on the classpath.
> >>>> changes to the OPTIONS=[option,option,...] command line option will
> >>>> be reflected here.
> >>>> 0:(dir) | ${jetty.home}/resources
> >>>> 1: 8.1.10.v20130312 |
> ${jetty
Re: starting up solr automatically
some progress but getting this error now sudo service jetty start Starting Jetty: -bash: line 1: cd: /var/lib/answers/atlascloud/solr45: No such file or directory STARTED Jetty Thu Dec 5 19:50:09 UTC 2013 [ec2-user@ip-10-50-203-92 ~]$ java.lang.IllegalArgumentException: No such OPTIONS: jsp at org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:411) at org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:388) at org.eclipse.jetty.start.Main.start(Main.java:509) at org.eclipse.jetty.start.Main.main(Main.java:96) On Thu, Dec 5, 2013 at 2:28 PM, Greg Walters wrote: > Eric, > > If you're using the script from the gist I posted make sure you're > sourcing the jetty file at line 140. > > Thanks, > Greg > > On Dec 5, 2013, at 1:21 PM, Eric Palmer wrote: > > > Greg or anyone that can help, when I try to start jetty as a service > > sudo service jetty start > > > > I get this error > > ** ERROR: JETTY_HOME not set, you need to set it or install in a standard > > location > > > > same for > > sudo service jetty stop > > sudo service jetty check > > etc > > > > I have a file here and the permissions look right > > ls -al /etc/default/ > > total 20 > > drwxr-xr-x 2 root root 4096 Dec 5 19:18 . > > drwxr-xr-x 68 root root 4096 Dec 5 19:03 .. > > -rwxr-xr-x 1 root root 317 Dec 5 19:18 jetty > > > > the contents if the jetty file is > > JAVA_HOME=/usr/lib/jvm/jre > > JETTY_HOME=/home/ec2-user/solr/solr-4.5.1/example/ > > JETTY_USER=ec2-user > > JETTY_LOGS=/home/ec2-user/solr/solr-4.5.1/example/logs > > JAVA_OPTIONS="\ > > -Dsolr.solr.home=/home/ec2-user/solr/solr-4.5.1/example/solr/ \ > > -Xms1g \ > > -Djetty.port=8983 \ > > -Dcollection.configName=collection1 \ > > $JAVA_OPTIONS" > > > > Any ideas what I should check? > > > > Eric P > > > > thanks in advance > > > > > > > > On Thu, Dec 5, 2013 at 11:28 AM, Greg Walters >wrote: > > > >> Alan, > >> > >> Yes, that's intentional. There's two reasons for this: > >> > >> 1: We make schema changes frequently (more frequently than I like) > >> 2: So far as I've noticed, it doesn't hurt anything and covers my butt > >> when I've got to clear out all the solr related data from ZK while > testing > >> > >> Thanks, > >> Greg > >> > >> On Dec 5, 2013, at 5:53 AM, Alan Woodward wrote: > >> > >>> Hi Greg, > >>> > >>> It looks as though your script below will bootstrap a collection > >> configuration every time Solr is restarted, which probably isn't what > you > >> want to do? You only need to upload the config once. > >>> > >>> Alan Woodward > >>> www.flax.co.uk > >>> > >>> > >>> On 4 Dec 2013, at 21:26, Greg Walters wrote: > >>> > >>>> I almost forgot, you'll need a file to setup the environment a bit > too: > >>>> > >>>> ** > >>>> JAVA_HOME=/usr/java/default > >>>> JAVA_OPTIONS="-Xmx15g \ > >>>> -Xms15g \ > >>>> -XX:+PrintGCApplicationStoppedTime \ > >>>> -XX:+PrintGCDateStamps \ > >>>> -XX:+PrintGCDetails \ > >>>> -XX:+UseConcMarkSweepGC \ > >>>> -XX:+UseParNewGC \ > >>>> -XX:+UseTLAB \ > >>>> -XX:+CMSParallelRemarkEnabled \ > >>>> -XX:+CMSScavengeBeforeRemark \ > >>>> -XX:+UseCMSInitiatingOccupancyOnly \ > >>>> -XX:CMSInitiatingOccupancyFraction=50 \ > >>>> -XX:CMSWaitDuration=30 \ > >>>> -XX:GCTimeRatio=40 \ > >>>> -Xloggc:/tmp/solr45_gc.log \ > >>>> -Dbootstrap_conf=true \ > >>>> > >> > -Dbootstrap_confdir=/var/lib/answers/atlascloud/solr45/solr/wa-en-collection_1/conf/ > >> \ > >>>> -Dcollection.configName=wa-en-collection \ > >>>> -DzkHost= \ > >>>> -DnumShards= \ > >>>> -Dsolr.solr.home=/var/lib/answers/atlascloud/solr45/solr/ \ > >>>> > >> > -Dlog4j.configuration=file:///var/lib/answers/atlascloud/solr45/resources/log4j.properties > >> \ > >>>> -Djetty.port=9101 \ > >>>> $JAVA_OPTIONS" > >>>> JETTY_HOME=/var/lib/answers/atlascloud/solr45/ > >>>> JETTY_USER=tomcat > >>>> JETTY_LOGS=/var/lib/answers/atlascloud/solr45/logs > >>
Re: starting up solr automatically
Okay I changed the cd /var/lib/answers/atlascloud/solr45 to cd $JETTY_HOME and am getting the same error run the runcmd from the comand line I get the same error if I take the ,jsp off it runs and solr returns search results so I modified the script and removed the ,jsp option and it works. I'm assuming this may be differences in versions or something. Is there any harm if it works in not having ",jsp" as an option? Eric On Thu, Dec 5, 2013 at 2:51 PM, Eric Palmer wrote: > some progress but getting this error now > sudo service jetty start > Starting Jetty: -bash: line 1: cd: /var/lib/answers/atlascloud/solr45: No > such file or directory > STARTED Jetty Thu Dec 5 19:50:09 UTC 2013 > [ec2-user@ip-10-50-203-92 ~]$ java.lang.IllegalArgumentException: No such > OPTIONS: jsp > at org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:411) > at org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:388) > at org.eclipse.jetty.start.Main.start(Main.java:509) > at org.eclipse.jetty.start.Main.main(Main.java:96) > > > On Thu, Dec 5, 2013 at 2:28 PM, Greg Walters wrote: > >> Eric, >> >> If you're using the script from the gist I posted make sure you're >> sourcing the jetty file at line 140. >> >> Thanks, >> Greg >> >> On Dec 5, 2013, at 1:21 PM, Eric Palmer wrote: >> >> > Greg or anyone that can help, when I try to start jetty as a service >> > sudo service jetty start >> > >> > I get this error >> > ** ERROR: JETTY_HOME not set, you need to set it or install in a >> standard >> > location >> > >> > same for >> > sudo service jetty stop >> > sudo service jetty check >> > etc >> > >> > I have a file here and the permissions look right >> > ls -al /etc/default/ >> > total 20 >> > drwxr-xr-x 2 root root 4096 Dec 5 19:18 . >> > drwxr-xr-x 68 root root 4096 Dec 5 19:03 .. >> > -rwxr-xr-x 1 root root 317 Dec 5 19:18 jetty >> > >> > the contents if the jetty file is >> > JAVA_HOME=/usr/lib/jvm/jre >> > JETTY_HOME=/home/ec2-user/solr/solr-4.5.1/example/ >> > JETTY_USER=ec2-user >> > JETTY_LOGS=/home/ec2-user/solr/solr-4.5.1/example/logs >> > JAVA_OPTIONS="\ >> > -Dsolr.solr.home=/home/ec2-user/solr/solr-4.5.1/example/solr/ \ >> > -Xms1g \ >> > -Djetty.port=8983 \ >> > -Dcollection.configName=collection1 \ >> > $JAVA_OPTIONS" >> > >> > Any ideas what I should check? >> > >> > Eric P >> > >> > thanks in advance >> > >> > >> > >> > On Thu, Dec 5, 2013 at 11:28 AM, Greg Walters > >wrote: >> > >> >> Alan, >> >> >> >> Yes, that's intentional. There's two reasons for this: >> >> >> >> 1: We make schema changes frequently (more frequently than I like) >> >> 2: So far as I've noticed, it doesn't hurt anything and covers my butt >> >> when I've got to clear out all the solr related data from ZK while >> testing >> >> >> >> Thanks, >> >> Greg >> >> >> >> On Dec 5, 2013, at 5:53 AM, Alan Woodward wrote: >> >> >> >>> Hi Greg, >> >>> >> >>> It looks as though your script below will bootstrap a collection >> >> configuration every time Solr is restarted, which probably isn't what >> you >> >> want to do? You only need to upload the config once. >> >>> >> >>> Alan Woodward >> >>> www.flax.co.uk >> >>> >> >>> >> >>> On 4 Dec 2013, at 21:26, Greg Walters wrote: >> >>> >> >>>> I almost forgot, you'll need a file to setup the environment a bit >> too: >> >>>> >> >>>> ** >> >>>> JAVA_HOME=/usr/java/default >> >>>> JAVA_OPTIONS="-Xmx15g \ >> >>>> -Xms15g \ >> >>>> -XX:+PrintGCApplicationStoppedTime \ >> >>>> -XX:+PrintGCDateStamps \ >> >>>> -XX:+PrintGCDetails \ >> >>>> -XX:+UseConcMarkSweepGC \ >> >>>> -XX:+UseParNewGC \ >> >>>> -XX:+UseTLAB \ >> >>>> -XX:+CMSParallelRemarkEnabled \ >> >>>> -XX:+CMSScavengeBeforeRemark \ >> >>>> -XX:+UseCMSInitiatingOccupancyOnly \ >> >>>> -XX:CMSInitiatingOccupancyFraction=50 \ >>
Re: starting up solr automatically
thanks Greg and Timothy. Very helpful On Thu, Dec 5, 2013 at 3:42 PM, Tim Potter wrote: > Apologies for chiming in late on this one ... just wanted to mention what > I've used with good success in the past is supervisord ( > http://supervisord.org/). It's easy to install and configure and has the > benefit of restarting nodes if they crash (such as due to an OOM). I'll > also mention that you should consider configuring the OOM killer for your > JVM when using SolrCloud as an OOM'd process is like zombie in your > cluster, causing all kinds of malice. > > -XX:OnOutOfMemoryError="/home/solr/oom_killer.sh $x %p" > > But, whether you use that or not, definitely take a look at supervisord if > you're on Linux as it has been a great way to run SolrCloud in a good sized > cluster for me. > > Cheers, > > Timothy Potter > Sr. Software Engineer, LucidWorks > www.lucidworks.com > > > From: Greg Walters > Sent: Thursday, December 05, 2013 1:23 PM > To: solr-user@lucene.apache.org > Subject: Re: starting up solr automatically > > Eric, > > Sorry about that, the entire OPTIONS= part can be dropped. That's there to > support a war file that we deploy next to solr. > > Greg > > On Dec 5, 2013, at 1:51 PM, Eric Palmer wrote: > > > some progress but getting this error now > > sudo service jetty start > > Starting Jetty: -bash: line 1: cd: /var/lib/answers/atlascloud/solr45: No > > such file or directory > > STARTED Jetty Thu Dec 5 19:50:09 UTC 2013 > > [ec2-user@ip-10-50-203-92 ~]$ java.lang.IllegalArgumentException: No > such > > OPTIONS: jsp > > at org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:411) > > at org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:388) > > at org.eclipse.jetty.start.Main.start(Main.java:509) > > at org.eclipse.jetty.start.Main.main(Main.java:96) > > > > > > On Thu, Dec 5, 2013 at 2:28 PM, Greg Walters >wrote: > > > >> Eric, > >> > >> If you're using the script from the gist I posted make sure you're > >> sourcing the jetty file at line 140. > >> > >> Thanks, > >> Greg > >> > >> On Dec 5, 2013, at 1:21 PM, Eric Palmer wrote: > >> > >>> Greg or anyone that can help, when I try to start jetty as a service > >>> sudo service jetty start > >>> > >>> I get this error > >>> ** ERROR: JETTY_HOME not set, you need to set it or install in a > standard > >>> location > >>> > >>> same for > >>> sudo service jetty stop > >>> sudo service jetty check > >>> etc > >>> > >>> I have a file here and the permissions look right > >>> ls -al /etc/default/ > >>> total 20 > >>> drwxr-xr-x 2 root root 4096 Dec 5 19:18 . > >>> drwxr-xr-x 68 root root 4096 Dec 5 19:03 .. > >>> -rwxr-xr-x 1 root root 317 Dec 5 19:18 jetty > >>> > >>> the contents if the jetty file is > >>> JAVA_HOME=/usr/lib/jvm/jre > >>> JETTY_HOME=/home/ec2-user/solr/solr-4.5.1/example/ > >>> JETTY_USER=ec2-user > >>> JETTY_LOGS=/home/ec2-user/solr/solr-4.5.1/example/logs > >>> JAVA_OPTIONS="\ > >>> -Dsolr.solr.home=/home/ec2-user/solr/solr-4.5.1/example/solr/ \ > >>> -Xms1g \ > >>> -Djetty.port=8983 \ > >>> -Dcollection.configName=collection1 \ > >>> $JAVA_OPTIONS" > >>> > >>> Any ideas what I should check? > >>> > >>> Eric P > >>> > >>> thanks in advance > >>> > >>> > >>> > >>> On Thu, Dec 5, 2013 at 11:28 AM, Greg Walters < > greg.walt...@answers.com > >>> wrote: > >>> > >>>> Alan, > >>>> > >>>> Yes, that's intentional. There's two reasons for this: > >>>> > >>>> 1: We make schema changes frequently (more frequently than I like) > >>>> 2: So far as I've noticed, it doesn't hurt anything and covers my butt > >>>> when I've got to clear out all the solr related data from ZK while > >> testing > >>>> > >>>> Thanks, > >>>> Greg > >>>> > >>>> On Dec 5, 2013, at 5:53 AM, Alan Woodward wrote: > >>>> > >>>>> Hi Greg, > >>>>> > >>>>> It looks a
