Ah, thanks Daniel. That did it!
Sent from a phoneI'm guessing you installed via gem?The json gem people released a breaking change in 1.7.6 -> 1.7.7 in response to a DoS vulnerability. I'm presently working on a fix. In the meantime you can uninstall version 1.7.7 of json and install 1.7.6 instead.--Daniel DeLeoOn Tuesday, February 12, 2013 at 9:19 AM, Chris wrote:
Hi chefsan interesting problem has cropped up and i'm a bit stumped. The erroris here: https://gist.github.com/anonymous/4771363. This apparentlyhas started happening in the last week, but I know there have beenhosts that were newly built with 10.20.0 and are working fine.As a test for this host that i'm working on, i removed 10.20.0 and itsdependent gems and installed 10.12.0 and the client ran as expected(ie: new client registration and adding an item to the run_list). Ithen reinstalled 10.20.0 on top of 10.12.0 and ran right back intothis wall. I can't help but think there's something wrong with thisVM and it just needs to be rebuilt, but i'd like to make sure thisisnt a client bug first.--Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentpermitted by applicable law.
Archive powered by MHonArc 2.6.16.