Hi!
I just installed iClassify without a problem, it is running and
accessable but I get a rather strange error when trying to run the
icagent commands:
$ ./bin/icagent -s http://puppet02:3000 -d icagent/
/usr/lib/ruby/1.8/net/http.rb:2094:in `error!'': 500 "Internal
Server
Error " (Net::HTTPFatalError)
from ./bin/../lib/iclassify/client.rb:83:in `run_request''
from ./bin/../lib/iclassify/client.rb:64:in `post_rest''
from ./bin/../lib/iclassify/client.rb:42:in `update_node''
from ./bin/../lib/iclassify/agent.rb:52:in `update''
from ./bin/icagent:76
Thought I did something wrong so i querried Adams server and got kinda
the same result:
$ ./bin/icsearch -s http://www.hjksolutions.com:5004 -t test -a test
/usr/lib/ruby/1.8/net/http.rb:2094:in `error!'': 500 "Internal
Server
Error" (Net::HTTPFatalError)
from ./bin/../lib/iclassify/client.rb:83:in `run_request''
from ./bin/../lib/iclassify/client.rb:64:in `post_rest''
from ./bin/../lib/iclassify/client.rb:22:in `search''
from ./bin/icsearch:58
Anyone experienced this before (Adam? :-) )?
Thx for taking a peek!
Simon
Simon Mügge wrote:> I just installed iClassify without a problem, it is running and > accessable but I get a rather strange error when trying to run the > icagent commands: > > $ ./bin/icagent -s http://puppet02:3000 -d icagent/ > /usr/lib/ruby/1.8/net/http.rb:2094:in `error!'': 500 "Internal Server > Error " (Net::HTTPFatalError) > from ./bin/../lib/iclassify/client.rb:83:in `run_request'' > from ./bin/../lib/iclassify/client.rb:64:in `post_rest'' > from ./bin/../lib/iclassify/client.rb:42:in `update_node'' > from ./bin/../lib/iclassify/agent.rb:52:in `update'' > from ./bin/icagent:76I got the same one but running the server in development mode seems to work. "./script/server" instead of "./script/server -e production"
On 8/24/07, Francois Deppierraz <francois@ctrlaltdel.ch> wrote:> I got the same one but running the server in development mode seems to work. > > "./script/server" instead of "./script/server -e production"This is probably due to the fact that iClassify''s development is still pretty fast and furious. One major change is that ferret needs to be running as an independent server when you deploy to production (and presumably have multiple mongrel''s running iClassify.) Make sure you have acts_as_ferret installed from trunk (the "stable" branch has totally broken independent ferret server support,) most likely as a vendor plugin. (See the INSTALL file for the full command.) Once that''s done, you should be able to run ./script/ferret_start to have the independent ferret server start working. You could also disable the external ferret support (in theory, I have not tried it) by getting rid of the production source in the ferret_server.yml. Making all of this easier to do (as close to bullet-proof as possible, actually) is high on my list of priorities. I would love any feedback, patches, etc. :) Adam -- HJK Solutions - We Launch Startups - http://www.hjksolutions.com Adam Jacob, Senior Partner T: (206) 508-4759 E: adam@hjksolutions.com