Hi, This is most likely caused by some nested JSON in the input. Do you have a sample for that?
Regards, Botond On Thu, 23 Jun 2016 11:14:44 -0700 tombin <tombin.a...@gmail.com> wrote: > I have several instances in aws running nxlog without any issue. I have 1 > box that acts funny and does not parse the json log (that all the other > hosts are doing just fine with). The error I see in the log is: > > 2016-06-23 04:11:31 ERROR [expr.c:163/nx_expr_statement_execute()] > procedure 'parse_json' failed at line 8, character 17 in > /etc/nxlog.conf.d/client_log.conf. statement execution has been > aborted;[json.c:271/yajl_parse_map_key_cb()] tmpstr missing > > > The only difference here is this host is using a different ami than the > other machines, but I don't understand what is different about it. The OS > is all centos 7, and I've checked all the package versions I can think of. > > > yajl, libdbi, nxlog-ce, perl are all the same. Is there a library that I > should be checking on that would cause ctx->tmpstr being NULL for every son > string it parses ? ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
