It looks like find running under zsh is the problem. In this case it does
like the wildcard (*).
I don't really know zsh so I will have to spend some time to investigate.
Bill
On 10/30/06, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
Hi, Hoss,
Thanks for the reply!
For #2, I think I just need to setup the passwordless SSH with empty
passphase. right?
For #1:
I'm using the following Enterprise version:
Linux version 2.4.21-37a6 (gcc version 3.2.3 20030502 (Red Hat Linux
3.2.3-47))
I tried to run the find command
find /home/yjin/apps/solr-nightly/example/solr/data/ -name snapshot.*
-print
directly on my box and it gave the same result:
zsh: no matches found: snapshot.*
I'm not familiar with shell scripting, so any thoughts?
Thanks,
-Hui
On 10/30/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
>
> : Here's a problem I got. It says there's no match for snapshot.* found
on
> the
> : master box. This is wrong, there's one such file exists.
> :
> : - I then ran snappuller specifically on the snap file that's on the
> master:
> : ./bin/snappuller -n snapshot.20061023172655
> :
> : This time it worked. and running installer created the index
> successfully.
>
> It's possible that there may be a subtle bug in the logic for
determining
> hte latest snapshot on your OS, the relevent section of of snappuller
> is...
>
> # get directory name of latest snapshot if not specified on command line
> if [[ -z ${snap_name} ]]
> then
> snap_name=`ssh -o StrictHostKeyChecking=no ${master_host} "find
> ${master_data_dir} -name snapshot.* -print"|grep -v wip|sort -r|head -1`
> fi
>
> ...which OS are you running this on?
>
> : 2. when I ran snappuller, it kept asking me for passwords for at least
> three
> : four time. Is this because it's using SSH? I have sudo permission on
the
> : master box. This makes me think if it's a cron-job that calls up the
> : snappuller, how does the cron deal with this password prompts?
>
> to run in a cron, you would need to set up ssh keys for the uid the
crons
> will run as which have empty passphrases (so they can function without a
> passphrase prompt).
>
> Another posisble reason why the snappuller failed for you the first
time,
> is if you accidently misstyped your passphrase one of the times it asked
> you (it's not snapppuller asking you this, snappller is just executing
> ssh, and ssh is asking you directly) ... one of those times was the code
> snippet i included above, which makes an ssh call just to get the name
of
> hte most recent snapshot.
>
>
> -Hoss
>
>
--
Regards,
-Hui
