You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by realw5 <dr...@improvementdirect.com> on 2007/04/10 04:28:26 UTC
Solr Scripts.conf Parsing Error
Hello,
I'm having troubles getting replication to work using the supplied solr
scripts. I've been doing alot of digging today, going though all the bash
scripts that make all this happen using rsync. I'm pretty sure I've boiled
it down to the scripts.conf file. When I make my settings in this file and
try to run say rsyncd-enable, I get an error saying "no passwd for user
solr". But yet, when I pass in the argument -u solr, it works just fine! My
though is the scripts.conf file has bad line characters or something along
those lines, however when I check it out in VI, I see nothing odd.
Any help would be appeciated! This is my last step to an otherwise
successful solr setup.
Dan
my scripts.conf file:
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
user=solr
solr_hostname=localhost
solr_port=8080
rsyncd_port=18080
data_dir=
webapp_name=solr
master_host=
master_data_dir=
master_status_dir=
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
Sent from the Solr - User mailing list archive at Nabble.com.
Re: New docs need server restart after synchronization
Posted by galo <ga...@last.fm>.
Yep, all normal..
galo
Bill Au wrote:
> Did you check for error messages in the snappuller and snapinstaller
> log files sunder solr/logs? Distribution related errors will not show
> up in the tomcat logs.
>
> Bill
>
> On 4/16/07, galo <ga...@last.fm> wrote:
>> Hi there,
>>
>> I've been running an index on 3 nodes (master + 2 slaves) without
>> problems for a few weeks, snappuller and snapinstaller run every hour
>> normally, install the new index without errors etc.
>>
>> In the last couple of days it seems like I need to restart tomcat for
>> the new documents to appear in the slave indexes. New docs are updated,
>> commited and appear if I do a search on the master, but if after the
>> synchronization I search in the slaves they don't appear. If I restart
>> tomcat they do.
>>
>> I remember this happening while I was setting up the index and seeing an
>> error somewhere (something like it not being able to open a new searcher
>> if i remember well), but i'm pretty sure the configuration is ok, it's
>> been working for weeks normally and I haven't done any changes since
>> then..
>>
>> any ideas where i should look at? I can't see any error messages in the
>> tomcat logs or the scripts' !
>>
>> thanks,
>> galo
>>
>
--
Galo Navarro, Developer
galo@last.fm
t. +44 (0)20 7780 7080
Last.fm | http://www.last.fm
Karen House 1-11 Baches Street
London N1 6DL
http://www.last.fm/user/galeote
Re: New docs need server restart after synchronization
Posted by Bill Au <bi...@gmail.com>.
Did you check for error messages in the snappuller and snapinstaller
log files sunder solr/logs? Distribution related errors will not show
up in the tomcat logs.
Bill
On 4/16/07, galo <ga...@last.fm> wrote:
> Hi there,
>
> I've been running an index on 3 nodes (master + 2 slaves) without
> problems for a few weeks, snappuller and snapinstaller run every hour
> normally, install the new index without errors etc.
>
> In the last couple of days it seems like I need to restart tomcat for
> the new documents to appear in the slave indexes. New docs are updated,
> commited and appear if I do a search on the master, but if after the
> synchronization I search in the slaves they don't appear. If I restart
> tomcat they do.
>
> I remember this happening while I was setting up the index and seeing an
> error somewhere (something like it not being able to open a new searcher
> if i remember well), but i'm pretty sure the configuration is ok, it's
> been working for weeks normally and I haven't done any changes since then..
>
> any ideas where i should look at? I can't see any error messages in the
> tomcat logs or the scripts' !
>
> thanks,
> galo
>
Re: New docs need server restart after synchronization
Posted by Chris Hostetter <ho...@fucit.org>.
: logged correctly... on the master. I had copied scripts.conf from the
: master to all the slaves with solr_hostname=master and didn't replace
: with slave1 slave2 etc, so the commit was successful, but not on the
: slave. Dumb. Dumb.
ah ... glad we found the problem.
: Now that we are at it.. how's the best set up for multiple indexes on
: the same server? Atm I have a tomcat server runs on each machine with a
: separate webapp for each index for a few indexes (5 by now, will be many
: more)
personally? .. i run a seperate servlet container instance for every index
... but that's becuase i have the RAM to spare and it helps ensure things
that each index runs in heavy isolation -- a serious flaw in one index
might crash the port, or a bad config might cause OOMs but then only one
index goes down, the other are still running.
but it's really a question of what you are comfortable with, and how much
money you have to spend.
-Hoss
Re: New docs need server restart after synchronization
Posted by galo <ga...@last.fm>.
I was expecting to see the commit error which is the one that told me
before the configuration was not correct but the commit was made and
logged correctly... on the master. I had copied scripts.conf from the
master to all the slaves with solr_hostname=master and didn't replace
with slave1 slave2 etc, so the commit was successful, but not on the
slave. Dumb. Dumb.
Now that we are at it.. how's the best set up for multiple indexes on
the same server? Atm I have a tomcat server runs on each machine with a
separate webapp for each index for a few indexes (5 by now, will be many
more)
Something like
master: http://master:8080/index1, http://master:8080/index2
slave1: http://slave1:8080/index1, http://slave1:8080/index2
slave2: http://slave2:8080/index1, http://slave2:8080/index2
slave3: http://slave3:8080/index1, http://slave3:8080/index2
...
On each server I have a main solr directory and then one for each index
solr
solr-index1
solr-index2
The main directory (solr) holds all the shared folders, so inside
solr-index1 and solr-index2, bin, etc, lib, ext, webapp etc are links to
sorl/bin, solr/etc, solr/lib, etc. Obviously, conf, data and logs are
not shared. This is reasonably simple to set up and install on other
servers being the only real complain that i'd like to keep a single conf
folder shared across master and slaves for each index (schema.xml,
solrconfig.xml etc. should be the same and scripts.conf can be shared as
long as you use solr_hostname=localhost and the same port, which is my
case). Not a tragedy anyway.
How are you dealing with these situations, are there better ways than this?
Cheers,
galo
Chris Hostetter wrote:
> : problems for a few weeks, snappuller and snapinstaller run every hour
> : normally, install the new index without errors etc.
> :
> : In the last couple of days it seems like I need to restart tomcat for
> : the new documents to appear in the slave indexes. New docs are updated,
> : commited and appear if I do a search on the master, but if after the
> : synchronization I search in the slaves they don't appear. If I restart
> : tomcat they do.
>
> snappuller "notifies" the slaves that they should reopen the index by
> executing the bin/commit script ... if that fails it should log a message
> ... but maybe bin/commit is logging an error in it's log and exiting with
> a successful return code?
>
> do you see the "commit" log messages from Solr? do you see the /update
> requests in the slaves tomcat access logs?
>
>
>
>
>
> -Hoss
>
>
--
Galo Navarro, Developer
galo@last.fm
t. +44 (0)20 7780 7080
Last.fm | http://www.last.fm
Karen House 1-11 Baches Street
London N1 6DL
http://www.last.fm/user/galeote
Re: New docs need server restart after synchronization
Posted by Chris Hostetter <ho...@fucit.org>.
: problems for a few weeks, snappuller and snapinstaller run every hour
: normally, install the new index without errors etc.
:
: In the last couple of days it seems like I need to restart tomcat for
: the new documents to appear in the slave indexes. New docs are updated,
: commited and appear if I do a search on the master, but if after the
: synchronization I search in the slaves they don't appear. If I restart
: tomcat they do.
snappuller "notifies" the slaves that they should reopen the index by
executing the bin/commit script ... if that fails it should log a message
... but maybe bin/commit is logging an error in it's log and exiting with
a successful return code?
do you see the "commit" log messages from Solr? do you see the /update
requests in the slaves tomcat access logs?
-Hoss
New docs need server restart after synchronization
Posted by galo <ga...@last.fm>.
Hi there,
I've been running an index on 3 nodes (master + 2 slaves) without
problems for a few weeks, snappuller and snapinstaller run every hour
normally, install the new index without errors etc.
In the last couple of days it seems like I need to restart tomcat for
the new documents to appear in the slave indexes. New docs are updated,
commited and appear if I do a search on the master, but if after the
synchronization I search in the slaves they don't appear. If I restart
tomcat they do.
I remember this happening while I was setting up the index and seeing an
error somewhere (something like it not being able to open a new searcher
if i remember well), but i'm pretty sure the configuration is ok, it's
been working for weeks normally and I haven't done any changes since then..
any ideas where i should look at? I can't see any error messages in the
tomcat logs or the scripts' !
thanks,
galo
Re: Solr Scripts.conf Parsing Error
Posted by realw5 <dr...@improvementdirect.com>.
dos2unix did the trick! Thanks for everyones direction. I'm still a little
new to the whole linux world. Once I fixed that, all the scripts seemed to
work just find now, whoho!!
Dan
Venkatesh Seetharam wrote:
>
> you could use dos2unix command on linux or cygwin to remove these.
>
> On 4/13/07, realw5 <dr...@improvementdirect.com> wrote:
>>
>>
>> I think you're on to something, here was the output:
>>
>> # Licensed to the Apache Software Foundation (ASF) under one or more^M$
>> # contributor license agreements. See the NOTICE file distributed
>> with^M$
>> # this work for additional information regarding copyright ownership.^M$
>> # The ASF licenses this file to You under the Apache License, Version 2.0
>> ^M$
>> # (the "License"); you may not use this file except in compliance with^M$
>> # the License. You may obtain a copy of the License at^M$
>> #^M$
>> # http://www.apache.org/licenses/LICENSE-2.0^M$
>> #^M$
>> # Unless required by applicable law or agreed to in writing, software^M$
>> # distributed under the License is distributed on an "AS IS" BASIS,^M$
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.^M$
>> # See the License for the specific language governing permissions and^M$
>> # limitations under the License.^M$
>> user=solr^M$
>> solr_hostname=localhost^M$
>> solr_port=8080^M$
>> rsyncd_port=18080^M$
>> data_dir=^M$
>> webapp_name=solr^M$
>> master_host=^M$
>> master_data_dir=^M$
>> master_status_dir=^M$
>>
>> Question now is, what's the best solution to removing those characters?
>>
>> Dan
>>
>> Chris Hostetter wrote:
>> >
>> >
>> > : all the debug output. Here, is a snip of that. Note the "solr\r", yet
>> in
>> > my
>> > : .conf file I have only "user=solr". If I run the script using this
>> > command
>> >
>> > what does "cat -vet scripts.conf" tell you?
>> >
>> >
>> >
>> > -Hoss
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9988416
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Thanks,
> Venkatesh
>
> "Perfection (in design) is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away."
> - Antoine de Saint-Exupéry
>
>
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a10019213
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Scripts.conf Parsing Error
Posted by Bill Au <bi...@gmail.com>.
Or simply create a new copy of the file using vi locally on the system
where you are running solr. Don't cut and paste since you may include
the non-printing characters that way too. Simply type in the content
of the file.
Bill
On 4/14/07, Venkatesh Seetharam <vs...@gmail.com> wrote:
> you could use dos2unix command on linux or cygwin to remove these.
>
> On 4/13/07, realw5 <dr...@improvementdirect.com> wrote:
> >
> >
> > I think you're on to something, here was the output:
> >
> > # Licensed to the Apache Software Foundation (ASF) under one or more^M$
> > # contributor license agreements. See the NOTICE file distributed with^M$
> > # this work for additional information regarding copyright ownership.^M$
> > # The ASF licenses this file to You under the Apache License, Version 2.0
> > ^M$
> > # (the "License"); you may not use this file except in compliance with^M$
> > # the License. You may obtain a copy of the License at^M$
> > #^M$
> > # http://www.apache.org/licenses/LICENSE-2.0^M$
> > #^M$
> > # Unless required by applicable law or agreed to in writing, software^M$
> > # distributed under the License is distributed on an "AS IS" BASIS,^M$
> > # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > implied.^M$
> > # See the License for the specific language governing permissions and^M$
> > # limitations under the License.^M$
> > user=solr^M$
> > solr_hostname=localhost^M$
> > solr_port=8080^M$
> > rsyncd_port=18080^M$
> > data_dir=^M$
> > webapp_name=solr^M$
> > master_host=^M$
> > master_data_dir=^M$
> > master_status_dir=^M$
> >
> > Question now is, what's the best solution to removing those characters?
> >
> > Dan
> >
> > Chris Hostetter wrote:
> > >
> > >
> > > : all the debug output. Here, is a snip of that. Note the "solr\r", yet
> > in
> > > my
> > > : .conf file I have only "user=solr". If I run the script using this
> > > command
> > >
> > > what does "cat -vet scripts.conf" tell you?
> > >
> > >
> > >
> > > -Hoss
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9988416
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
> Thanks,
> Venkatesh
>
> "Perfection (in design) is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away."
> - Antoine de Saint-Exupéry
>
Re: Solr Scripts.conf Parsing Error
Posted by Venkatesh Seetharam <vs...@gmail.com>.
you could use dos2unix command on linux or cygwin to remove these.
On 4/13/07, realw5 <dr...@improvementdirect.com> wrote:
>
>
> I think you're on to something, here was the output:
>
> # Licensed to the Apache Software Foundation (ASF) under one or more^M$
> # contributor license agreements. See the NOTICE file distributed with^M$
> # this work for additional information regarding copyright ownership.^M$
> # The ASF licenses this file to You under the Apache License, Version 2.0
> ^M$
> # (the "License"); you may not use this file except in compliance with^M$
> # the License. You may obtain a copy of the License at^M$
> #^M$
> # http://www.apache.org/licenses/LICENSE-2.0^M$
> #^M$
> # Unless required by applicable law or agreed to in writing, software^M$
> # distributed under the License is distributed on an "AS IS" BASIS,^M$
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.^M$
> # See the License for the specific language governing permissions and^M$
> # limitations under the License.^M$
> user=solr^M$
> solr_hostname=localhost^M$
> solr_port=8080^M$
> rsyncd_port=18080^M$
> data_dir=^M$
> webapp_name=solr^M$
> master_host=^M$
> master_data_dir=^M$
> master_status_dir=^M$
>
> Question now is, what's the best solution to removing those characters?
>
> Dan
>
> Chris Hostetter wrote:
> >
> >
> > : all the debug output. Here, is a snip of that. Note the "solr\r", yet
> in
> > my
> > : .conf file I have only "user=solr". If I run the script using this
> > command
> >
> > what does "cat -vet scripts.conf" tell you?
> >
> >
> >
> > -Hoss
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9988416
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
--
Thanks,
Venkatesh
"Perfection (in design) is achieved not when there is nothing more to add,
but rather when there is nothing more to take away."
- Antoine de Saint-Exupéry
Re: Solr Scripts.conf Parsing Error
Posted by realw5 <dr...@improvementdirect.com>.
I think you're on to something, here was the output:
# Licensed to the Apache Software Foundation (ASF) under one or more^M$
# contributor license agreements. See the NOTICE file distributed with^M$
# this work for additional information regarding copyright ownership.^M$
# The ASF licenses this file to You under the Apache License, Version 2.0^M$
# (the "License"); you may not use this file except in compliance with^M$
# the License. You may obtain a copy of the License at^M$
#^M$
# http://www.apache.org/licenses/LICENSE-2.0^M$
#^M$
# Unless required by applicable law or agreed to in writing, software^M$
# distributed under the License is distributed on an "AS IS" BASIS,^M$
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.^M$
# See the License for the specific language governing permissions and^M$
# limitations under the License.^M$
user=solr^M$
solr_hostname=localhost^M$
solr_port=8080^M$
rsyncd_port=18080^M$
data_dir=^M$
webapp_name=solr^M$
master_host=^M$
master_data_dir=^M$
master_status_dir=^M$
Question now is, what's the best solution to removing those characters?
Dan
Chris Hostetter wrote:
>
>
> : all the debug output. Here, is a snip of that. Note the "solr\r", yet in
> my
> : .conf file I have only "user=solr". If I run the script using this
> command
>
> what does "cat -vet scripts.conf" tell you?
>
>
>
> -Hoss
>
>
>
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9988416
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Scripts.conf Parsing Error
Posted by Chris Hostetter <ho...@fucit.org>.
: all the debug output. Here, is a snip of that. Note the "solr\r", yet in my
: .conf file I have only "user=solr". If I run the script using this command
what does "cat -vet scripts.conf" tell you?
-Hoss
Re: Solr Scripts.conf Parsing Error
Posted by realw5 <dr...@improvementdirect.com>.
I have not run bash -x, however I have run rsyncd-enable with -V which shows
all the debug output. Here, is a snip of that. Note the "solr\r", yet in my
.conf file I have only "user=solr". If I run the script using this command
"./solr/bin/rsyncd-enable -u solr -V" everything works fine.
Also, if this helps, I'm running Red Hat ES 4.
[root@Solr1 apache-tomcat]# ./solr/bin/rsyncd-enable -V
+ ./solr/bin/rsyncd-enable -V
+ fixUser -V
]][ -z solr
++ whoami
]][ root != solr
+ sudo -u $'solr\r' ./solr/bin/rsyncd-enable -V
!udo: no passwd entry for solr
+ exit 1
++ echo -ne '\033]0;root@Solr1:/usr/local/apache-tomcat\007'
Dan
Bill Au wrote:
>
> What does your directory structure looks like? Have you tried running
> rsyncd-enable with "bash -x" to see how/what $user is set?
>
> Bill
>
> On 4/9/07, realw5 <dr...@improvementdirect.com> wrote:
>>
>>
>> Hello,
>> I'm having troubles getting replication to work using the supplied solr
>> scripts. I've been doing alot of digging today, going though all the bash
>> scripts that make all this happen using rsync. I'm pretty sure I've
>> boiled
>> it down to the scripts.conf file. When I make my settings in this file
>> and
>> try to run say rsyncd-enable, I get an error saying "no passwd for user
>> solr". But yet, when I pass in the argument -u solr, it works just fine!
>> My
>> though is the scripts.conf file has bad line characters or something
>> along
>> those lines, however when I check it out in VI, I see nothing odd.
>>
>> Any help would be appeciated! This is my last step to an otherwise
>> successful solr setup.
>>
>> Dan
>>
>> my scripts.conf file:
>> # Licensed to the Apache Software Foundation (ASF) under one or more
>> # contributor license agreements. See the NOTICE file distributed with
>> # this work for additional information regarding copyright ownership.
>> # The ASF licenses this file to You under the Apache License, Version 2.0
>> # (the "License"); you may not use this file except in compliance with
>> # the License. You may obtain a copy of the License at
>> #
>> # http://www.apache.org/licenses/LICENSE-2.0
>> #
>> # Unless required by applicable law or agreed to in writing, software
>> # distributed under the License is distributed on an "AS IS" BASIS,
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> # See the License for the specific language governing permissions and
>> # limitations under the License.
>> user=solr
>> solr_hostname=localhost
>> solr_port=8080
>> rsyncd_port=18080
>> data_dir=
>> webapp_name=solr
>> master_host=
>> master_data_dir=
>> master_status_dir=
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9943326
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Scripts.conf Parsing Error
Posted by Bill Au <bi...@gmail.com>.
As Chris as pointed out, there may be some non-printing character(s) in your
scripts.conf.
Bill
On 4/11/07, realw5 <dr...@improvementdirect.com> wrote:
>
>
> I have not run bash -x, however I have run rsyncd-enable with -V which
> shows
> all the debug output. Here, is a snip of that. Note the "solr\r", yet in
> my
> .conf file I have only "user=solr". If I run the script using this command
> "./solr/bin/rsyncd-enable -u solr -V" everything works fine.
>
> Also, if this helps, I'm running Red Hat ES 4.
>
>
> [root@Solr1 apache-tomcat]# ./solr/bin/rsyncd-enable -V
> + ./solr/bin/rsyncd-enable -V
> + fixUser -V
> ]][ -z solr
> ++ whoami
> ]][ root != solr
> + sudo -u $'solr\r' ./solr/bin/rsyncd-enable -V
> !udo: no passwd entry for solr
> + exit 1
> ++ echo -ne '\033]0;root@Solr1:/usr/local/apache-tomcat\007'
>
> Dan
>
>
> Bill Au wrote:
> >
> > What does your directory structure looks like? Have you tried running
> > rsyncd-enable with "bash -x" to see how/what $user is set?
> >
> > Bill
> >
> > On 4/9/07, realw5 <dr...@improvementdirect.com> wrote:
> >>
> >>
> >> Hello,
> >> I'm having troubles getting replication to work using the supplied solr
> >> scripts. I've been doing alot of digging today, going though all the
> bash
> >> scripts that make all this happen using rsync. I'm pretty sure I've
> >> boiled
> >> it down to the scripts.conf file. When I make my settings in this file
> >> and
> >> try to run say rsyncd-enable, I get an error saying "no passwd for user
> >> solr". But yet, when I pass in the argument -u solr, it works just
> fine!
> >> My
> >> though is the scripts.conf file has bad line characters or something
> >> along
> >> those lines, however when I check it out in VI, I see nothing odd.
> >>
> >> Any help would be appeciated! This is my last step to an otherwise
> >> successful solr setup.
> >>
> >> Dan
> >>
> >> my scripts.conf file:
> >> # Licensed to the Apache Software Foundation (ASF) under one or more
> >> # contributor license agreements. See the NOTICE file distributed with
> >> # this work for additional information regarding copyright ownership.
> >> # The ASF licenses this file to You under the Apache License, Version
> 2.0
> >> # (the "License"); you may not use this file except in compliance with
> >> # the License. You may obtain a copy of the License at
> >> #
> >> # http://www.apache.org/licenses/LICENSE-2.0
> >> #
> >> # Unless required by applicable law or agreed to in writing, software
> >> # distributed under the License is distributed on an "AS IS" BASIS,
> >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >> # See the License for the specific language governing permissions and
> >> # limitations under the License.
> >> user=solr
> >> solr_hostname=localhost
> >> solr_port=8080
> >> rsyncd_port=18080
> >> data_dir=
> >> webapp_name=solr
> >> master_host=
> >> master_data_dir=
> >> master_status_dir=
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
> >> Sent from the Solr - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9943338
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
Re: Solr Scripts.conf Parsing Error
Posted by realw5 <dr...@improvementdirect.com>.
I have not run bash -x, however I have run rsyncd-enable with -V which shows
all the debug output. Here, is a snip of that. Note the "solr\r", yet in my
.conf file I have only "user=solr". If I run the script using this command
"./solr/bin/rsyncd-enable -u solr -V" everything works fine.
Also, if this helps, I'm running Red Hat ES 4.
[root@Solr1 apache-tomcat]# ./solr/bin/rsyncd-enable -V
+ ./solr/bin/rsyncd-enable -V
+ fixUser -V
]][ -z solr
++ whoami
]][ root != solr
+ sudo -u $'solr\r' ./solr/bin/rsyncd-enable -V
!udo: no passwd entry for solr
+ exit 1
++ echo -ne '\033]0;root@Solr1:/usr/local/apache-tomcat\007'
Dan
Bill Au wrote:
>
> What does your directory structure looks like? Have you tried running
> rsyncd-enable with "bash -x" to see how/what $user is set?
>
> Bill
>
> On 4/9/07, realw5 <dr...@improvementdirect.com> wrote:
>>
>>
>> Hello,
>> I'm having troubles getting replication to work using the supplied solr
>> scripts. I've been doing alot of digging today, going though all the bash
>> scripts that make all this happen using rsync. I'm pretty sure I've
>> boiled
>> it down to the scripts.conf file. When I make my settings in this file
>> and
>> try to run say rsyncd-enable, I get an error saying "no passwd for user
>> solr". But yet, when I pass in the argument -u solr, it works just fine!
>> My
>> though is the scripts.conf file has bad line characters or something
>> along
>> those lines, however when I check it out in VI, I see nothing odd.
>>
>> Any help would be appeciated! This is my last step to an otherwise
>> successful solr setup.
>>
>> Dan
>>
>> my scripts.conf file:
>> # Licensed to the Apache Software Foundation (ASF) under one or more
>> # contributor license agreements. See the NOTICE file distributed with
>> # this work for additional information regarding copyright ownership.
>> # The ASF licenses this file to You under the Apache License, Version 2.0
>> # (the "License"); you may not use this file except in compliance with
>> # the License. You may obtain a copy of the License at
>> #
>> # http://www.apache.org/licenses/LICENSE-2.0
>> #
>> # Unless required by applicable law or agreed to in writing, software
>> # distributed under the License is distributed on an "AS IS" BASIS,
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> # See the License for the specific language governing permissions and
>> # limitations under the License.
>> user=solr
>> solr_hostname=localhost
>> solr_port=8080
>> rsyncd_port=18080
>> data_dir=
>> webapp_name=solr
>> master_host=
>> master_data_dir=
>> master_status_dir=
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9943338
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Scripts.conf Parsing Error
Posted by realw5 <dr...@improvementdirect.com>.
I have not run bash -x, however I have run rsyncd-enable with -V which shows
all the debug output. Here, is a snip of that. Note the "solr\r", yet in my
.conf file I have only "user=solr". If I run the script using this command
"./solr/bin/rsyncd-enable -u solr -V" everything works fine.
Also, if this helps, I'm running Red Hat ES 4.
[root@Solr1 apache-tomcat]# ./solr/bin/rsyncd-enable -V
+ ./solr/bin/rsyncd-enable -V
+ fixUser -V
]][ -z solr
++ whoami
]][ root != solr
+ sudo -u $'solr\r' ./solr/bin/rsyncd-enable -V
!udo: no passwd entry for solr
+ exit 1
++ echo -ne '\033]0;root@Solr1:/usr/local/apache-tomcat\007'
Dan
Bill Au wrote:
>
> What does your directory structure looks like? Have you tried running
> rsyncd-enable with "bash -x" to see how/what $user is set?
>
> Bill
>
> On 4/9/07, realw5 <dr...@improvementdirect.com> wrote:
>>
>>
>> Hello,
>> I'm having troubles getting replication to work using the supplied solr
>> scripts. I've been doing alot of digging today, going though all the bash
>> scripts that make all this happen using rsync. I'm pretty sure I've
>> boiled
>> it down to the scripts.conf file. When I make my settings in this file
>> and
>> try to run say rsyncd-enable, I get an error saying "no passwd for user
>> solr". But yet, when I pass in the argument -u solr, it works just fine!
>> My
>> though is the scripts.conf file has bad line characters or something
>> along
>> those lines, however when I check it out in VI, I see nothing odd.
>>
>> Any help would be appeciated! This is my last step to an otherwise
>> successful solr setup.
>>
>> Dan
>>
>> my scripts.conf file:
>> # Licensed to the Apache Software Foundation (ASF) under one or more
>> # contributor license agreements. See the NOTICE file distributed with
>> # this work for additional information regarding copyright ownership.
>> # The ASF licenses this file to You under the Apache License, Version 2.0
>> # (the "License"); you may not use this file except in compliance with
>> # the License. You may obtain a copy of the License at
>> #
>> # http://www.apache.org/licenses/LICENSE-2.0
>> #
>> # Unless required by applicable law or agreed to in writing, software
>> # distributed under the License is distributed on an "AS IS" BASIS,
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> # See the License for the specific language governing permissions and
>> # limitations under the License.
>> user=solr
>> solr_hostname=localhost
>> solr_port=8080
>> rsyncd_port=18080
>> data_dir=
>> webapp_name=solr
>> master_host=
>> master_data_dir=
>> master_status_dir=
>> --
>> View this message in context:
>> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9943328
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Scripts.conf Parsing Error
Posted by Bill Au <bi...@gmail.com>.
What does your directory structure looks like? Have you tried running
rsyncd-enable with "bash -x" to see how/what $user is set?
Bill
On 4/9/07, realw5 <dr...@improvementdirect.com> wrote:
>
>
> Hello,
> I'm having troubles getting replication to work using the supplied solr
> scripts. I've been doing alot of digging today, going though all the bash
> scripts that make all this happen using rsync. I'm pretty sure I've boiled
> it down to the scripts.conf file. When I make my settings in this file and
> try to run say rsyncd-enable, I get an error saying "no passwd for user
> solr". But yet, when I pass in the argument -u solr, it works just fine!
> My
> though is the scripts.conf file has bad line characters or something along
> those lines, however when I check it out in VI, I see nothing odd.
>
> Any help would be appeciated! This is my last step to an otherwise
> successful solr setup.
>
> Dan
>
> my scripts.conf file:
> # Licensed to the Apache Software Foundation (ASF) under one or more
> # contributor license agreements. See the NOTICE file distributed with
> # this work for additional information regarding copyright ownership.
> # The ASF licenses this file to You under the Apache License, Version 2.0
> # (the "License"); you may not use this file except in compliance with
> # the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> user=solr
> solr_hostname=localhost
> solr_port=8080
> rsyncd_port=18080
> data_dir=
> webapp_name=solr
> master_host=
> master_data_dir=
> master_status_dir=
> --
> View this message in context:
> http://www.nabble.com/Solr-Scripts.conf-Parsing-Error-tf3550726.html#a9912973
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>