Matthew Runo wrote:
It seems that as soon as I get a commit, snapshooter goes wild.
I have 1107 running instances of snapshooter right now..
I suspect you've got pathing and/or permissions issues.
First try running snapshooter -v, and it will be louder. I've often had
to dig in deeper,
FYI, in additional to the -v option, the latest version of all the scripts
have a -V option which is equivalent to set -x.
Bill
On 7/20/07, Matthew Runo [EMAIL PROTECTED] wrote:
Just an FYI..
it seems that the generated scripts.conf file had DOS format
newlines. Once I did :set
Yes, I used that, and didn't see much else. But I did see that it was
trying to execute something on the blank line at the top of
scripts.conf, which eventually lead to the newlines.
++
| Matthew Runo
| Zappos Development
| [EMAIL
Also...
[EMAIL PROTECTED]:/home/mruno]$ sudo /opt/solr/bin/snapinstaller -M
search1.zappos.com -d /opt/solr/data -S /opt/solr/logs -u tomcat5 -v
: command not foundpts.conf: line 15:
: command not foundpts.conf: line 15:
started by mruno
command: /opt/solr/bin/snapinstaller -M
Also...
tomcat5 17003 0.0 0.0 3084 1456 ?S10:32 0:00 /bin/
bash /opt/solr/bin/snapshooter -u tomcat5 -d /opt/solr/data
tomcat5 17008 0.0 0.0 3084 1456 ?S10:32 0:00 /bin/
bash /opt/solr/bin/snapshooter -u tomcat5 -d /opt/solr/data
tomcat5 17013 0.0
It seems that as soon as I get a commit, snapshooter goes wild.
I have 1107 running instances of snapshooter right now..
++
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
