Hi. For some reasons, I turned off SSL for Splunk REST API. Everything is fine, except the Splunk DB Connect app. jbridge is failing to start, after the SSL change: DEBUG Setting up java Environment: app=dbx, cfg_name=java, cfg_stanza=java, java_home=None DEBUG JAVA_HOME=C:\Program Files\Java\jre7 INFO Checking for obsolete java libraries in C:\Program Files\Splunk\etc\apps\dbx\bin\lib DEBUG Starting JavaBridgeServer... DEBUG Executing (native) CMD C:\Program Files\Java\jre7\bin\java.exe -cp ..... -Dsplunk.app.ctx=dbx com.splunk.bridge.JavaBridgeServer 1368 INFO Started JavaBridgeServer PID=3868 DEBUG win32 handler registered ERROR Java process returned error code 1! Error: initializing Splunk context... Exception in thread "main" com.splunk.config.SplunkConfigurationException: IO Error while reading configuration from Splunkd: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at com.splunk.config.rest.RESTAdapter.request(RESTAdapter.java:195) at com.splunk.config.rest.RESTAdapter.readConfig(RESTAdapter.java:203) ... at com.splunk.env.SplunkContext.getConfigStanza(SplunkContext.java:313) at com.splunk.env.SplunkContext.initialize(SplunkContext.java:128) at com.splunk.bridge.JavaBridgeServer.main(JavaBridgeServer.java:34) ... DEBUG JavaBridgeServer terminated Did I miss a config options for dbx app, which sets SSL to false? If there's no such options, is this case a known issue? Any suggested work around? ... View more

Hi, I'm trying to send data into splunk index, using splunkjs.Service.Index.submitEvent method, as shown in the example (look for "To add data directly to an index" paragraph). It works fine under FF and Chrome, but not in IE8. When trying to execute myindexes.item("test_index") , the myindexes is null. I verified that it is OK and non-null before the fetch callback is executed. In the console, I see an error saying "Error in parsing JSON" , without any additional data/params. Any ideas? Edit: I have no IE8 to reproduce it right now. When running in IE10 everything is working fine (like FF and Chrome). But, when choosing compatibility view (which simulates IE7), the problem does occur. This can be reproduced easily, no specific configuration is required. the code is very simple (almost purely copied from the example): var http = new splunkjs.ProxyHttp("/proxy"); // Create a Service instance and log in var service = new splunkjs.Service(http, { username: "admin", password: "changeme", scheme: "https", host: "localhost", port:"8089", version:"5.0" }); // Get the collection of indexes var myindexes = service.indexes(); // Get an index to send events to myindexes.fetch(function(err, myindexes) { var myindex = myindexes.item("main"); // Submit an event to the index myindex.submitEvent("A new event", { sourcetype: "mysourcetype" }, function(err, result, myindex) { console.log("Submitted event: ", result); }); }); The normal network traffic goes like this ("output_mode=json" is omitted for readability): (1) POST /proxy/services/auth/login request body contains username and password response contains a sessionKey (2) GET /proxy/services/data/indexes?count=0 response contains a list of indexes details (3) POST /proxy/services/receivers/simple?sourcetype=mysourcetype&index=main request body contains the text of the event to be indexed response contains a confirmation about the indexed event When fails, the network traffic stops after the first request. the response seems to be alright: {"sessionKey":"................................"} ... View more