ankiit / logstash

Automatically exported from code.google.com/p/logstash
0 stars 0 forks source link

Current gem (logstash-0.2.20110331121235) can't parse URI query strings #49

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. gem install logstash
2. Create a logstash.yaml config file with a URI with a query string, e.g. 
amqp://localhost/direct/nlog?durable_exchange=y&durable_queue=y
3. run logstash -f logstash.yaml

What is the expected output? What do you see instead?

Expected: running logstash.
Instead: 
/var/lib/gems/1.9.1/gems/logstash-0.2.20110331121235/lib/logstash/inputs/base.rb
:21:in `initialize': uninitialized constant LogStash::Inputs::Base::CGI 
(NameError)

What version of the product are you using? On what operating system?

logstash-0.2.20110331121235 on debian squeeze, under ruby1.9.1 (which is really 
1.9.2 -- thanks, debian!).

Please provide any additional information below.

Looks like the config system in git HEAD is completely different, and has been 
for some time before that 20110331 timestamp would indicate the gem was 
generated.  How does code make its way from git into the gem?

Original issue reported on code.google.com by d...@dis.org.nz on 1 Apr 2011 at 12:54

GoogleCodeExporter commented 9 years ago
Could you try adding a line in base.rb towards the top:

require 'cgi'

and see if that helps?

We've been hacking on logstash a lot in the master branch (jruby, new config 
system, etc). There is a pre-jruby branch (that is also pre-new-config-way) 
that we're building gems from right now for release.

Original comment by petefbsd on 1 Apr 2011 at 1:00

GoogleCodeExporter commented 9 years ago
That works.  How stable is the master branch, should I be using that instead?

Original comment by d...@dis.org.nz on 1 Apr 2011 at 1:02