I think that there's a problem with your system("Virtual timer expired"
as I said is very odd).
Without more info I only found relevant it[1][2].
Regards
[1]http://www.ruby-forum.com/topic/195414
[2]http://redmine.ruby-lang.org/issues/show/2103
Colin wrote:
If I execute the script on the server I get:
(in /pathTo/releases/20100303200303)
Generating Configuration to /pathTo/releases/20100303200303/config/
production.sphinx.conf
Virtual timer expired
I then manually created a tmp folder in my shared folder as per advice
from the Thinking Sphinx mailing group, the cap deploy still fails in
the same way but the script now outputs:
(in /pathTo/releases/20100303200303)
Generating Configuration to /pathTo/releases/20100303200303/config/
production.sphinx.conf
Loaded suite /usr/local/bin/rake
Started
Finished in 0.000146 seconds.
0 tests, 0 assertions, 0 failures, 0 errors
Virtual timer expired
On Mar 4, 8:29 am, "Rafael G." <[email protected]> wrote:
Hi Colin,
Could you execute this script on the server:
"sh -c 'if [ -d /pathTo/rails/releases/20100303182701 ]; then c
d /pathTo/rails/releases/20100303182701; else cd /pathTo/rails
/current; fi; rake RAILS_ENV=production thinking_sphinx:configure'"
It's very odd the "Virtual timer error"
Colin wrote:
Hi,
I'm trying to get Thinking Sphinx running on my production server, I'm
following the guidelines
here:http://freelancing-god.github.com/ts/en/deployment.html
I have added the 3 suggested tasks (http://pastie.org/852303) to my
deploy.rb but that is causing this output:http://pastie.org/852096
(failing at line 21).
I googled the error but it seems to arise in lots of different
scenarios, none of which seem related to Thinking Sphinx.
Any ideas?
Colin
--
Rafa
--
Rafa
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
