# Quotes in config files v2.3.0 **URL:** \ **Category:** Logstash\ **Created:** [April 6, 2016, 3:59pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563 "2016-04-06T15:59:12Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 6, 2016, 3:59pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/1 "2016-04-06T15:59:12Z")
Hi all, When trying out my config on a windows laptop this seemed to work fine (v2.2.0 by the way): `input { s3 { credentials => ["XXXXXXXXXXXXXXXXXXXXXXXXXXXXX","XXXXXXXXXXXXXXXXXXXXXX"] bucket => "XXXXXX-logqueue" region => "eu-west-1" prefix => "logs/" codec => "json"{ charset => "ISO-8859-1"} type => "s3_logqueue" backup_to_bucket => "XXXXXX-archivedlogs" delete => "true" } }` But when i ran it on ubuntu, using v2.3.0 i had to remove the quotes around "json" otherwise it said plugin "json" not found. Is this likely to be a windows issue or could it be that the new version is taking the values literally and not ignoring the quotes? ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 6, 2016, 4:11pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/2 "2016-04-06T16:11:33Z")
Just tested 2.3.0 on windows and got the same error: `"Couldn't find any codec plugin named '\"json\"'. Are you sure this is correct? Trying to load the \"json\" codec plugin resulted in this error: no such file to load -- logstash/codecs/\"json\"", :level=>:error}` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 7, 2016, 12:02am UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/3 "2016-04-07T00:02:26Z")
Try 2.3.1, there are a few issues with 2.3.0. ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 7, 2016, 2:09pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/4 "2016-04-07T14:09:03Z")
Hi Mark, Probably a dumb question but where do i get 2.3.1 from? ---
**Author:** ![Alex\_6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_6/32/1330_2.png) [@Alex\_6](https://discuss.elastic.co/u/Alex_6)\ **Post date:** [April 7, 2016, 3:07pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/5 "2016-04-07T15:07:36Z")
[Github releases page](https://github.com/elastic/logstash/releases) 🙂 ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 7, 2016, 3:34pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/6 "2016-04-07T15:34:40Z")
Thanks 🙂 I'll give it a go ---
**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\ **Post date:** [April 7, 2016, 3:51pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/7 "2016-04-07T15:51:22Z")
2.3.1 is due to be released today 🙂 ---
**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\ **Post date:** [April 7, 2016, 3:51pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/8 "2016-04-07T15:51:37Z")
Note, that there may be some delays, but today is our target. ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 7, 2016, 3:55pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/9 "2016-04-07T15:55:39Z")
I'll try again once its released, as I might have built it wrong (always used the packaged version before), but i ran "rake bootstrap", then from the bin folder: ./logstash -f /etc/logstash/conf.d --configtest and got: `The given configuration is invalid. Reason: Couldn't find any codec plugin named '"json"'. Are you sure this is correct? Trying to load the "json" codec plugin resulted in this error: no such file to load -- logstash/codecs/"json" {:level=>:fatal}` So I think its still reading the quotes literally, not a major issue but it seems a bit odd 🙂 Cheers! ---
**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\ **Post date:** [April 7, 2016, 3:59pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/10 "2016-04-07T15:59:51Z")
Yes, this is a bug. Looking into it I can confirm this will have to wait for 2.3.2 or later, it will not be fixed in 2.3.1. I've opened up an issue here [https://github.com/elastic/logstash/issues/5061](https://github.com/elastic/logstash/issues/5061) ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 7, 2016, 4:00pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/11 "2016-04-07T16:00:42Z")
Thanks Andrew, I can just remove the quotes for now, it's not too much of a workaround ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 7, 2016, 4:04pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/12 "2016-04-07T16:04:34Z")
the charset could be an issue if it isn't reading that. Maybe I'll drop back to a 2.2 version for now 😄 ---
**Author:** ![colinsurprenant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colinsurprenant/32/14776_2.png) [@colinsurprenant](https://discuss.elastic.co/u/colinsurprenant)\ **Post date:** [April 7, 2016, 4:29pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/13 "2016-04-07T16:29:03Z")
@Alex_6 @StephenGoodall please note that the [https://github.com/elastic/logstash/releases](https://github.com/elastic/logstash/releases) are just repo tar.gz and not a proper release package. It is basically the same a cloning the repo at the release tag and you will have to build logstash to have something usable. ---
**Author:** ![colinsurprenant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colinsurprenant/32/14776_2.png) [@colinsurprenant](https://discuss.elastic.co/u/colinsurprenant)\ **Post date:** [April 7, 2016, 5:57pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/14 "2016-04-07T17:57:09Z")
FYI 2.3.1 is now released, see [https://www.elastic.co/blog/logstash-2.3.1-and-2.2.4-released](https://www.elastic.co/blog/logstash-2.3.1-and-2.2.4-released) - in particular anyone who installed 2.3.0 should **absolutely** upgrade to 2.3.1. Note that there is no change for the quoting, so @StephenGoodall removing the quotes around the codec name is the right thing to do at this point! Colin ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 8, 2016, 8:44am UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/15 "2016-04-08T08:44:57Z")
thanks @colinsurprenant I've upgraded to 2.3.1 for some testing, i will remove the quotes around the codec, but do you know if the charset specification will be picked up? so it will be like this: `input { s3 { credentials => ["XXXXXXXXXXXXXXXXXXXXX","XXXXXXXXXXXXXXXXXXXXXXX"] bucket => "XXX-logqueue" region => "eu-west-1" prefix => "logs/" codec => json { charset => "ISO-8859-1"} type => "s3_logqueue" backup_to_bucket => "XXX-archivedlogs" delete => "true" } }` ---
**Author:** ![colinsurprenant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colinsurprenant/32/14776_2.png) [@colinsurprenant](https://discuss.elastic.co/u/colinsurprenant)\ **Post date:** [April 8, 2016, 4:32pm UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/16 "2016-04-08T16:32:58Z")
@StephenGoodall yes, `charset => "ISO-8859-1"` is totally a valid syntax and if it doesn't work this is a bug. ---
**Author:** ![StephenGoodall](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@StephenGoodall](https://discuss.elastic.co/u/StephenGoodall)\ **Post date:** [April 12, 2016, 10:36am UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/17 "2016-04-12T10:36:56Z")
Great, Thanks Colin ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:02am UTC](https://discuss.elastic.co/t/quotes-in-config-files-v2-3-0/46563/18 "2017-07-06T05:02:48Z")