[JIRA] (JENKINS-39452) build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer

2016-11-08 Thread dave.bott...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Bottger closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39452  
 
 
  build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer   
 

  
 
 
 
 

 
Change By: 
 Dave Bottger  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39452) build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer

2016-11-08 Thread dave.bott...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Bottger commented on  JENKINS-39452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer   
 

  
 
 
 
 

 
 I don't have a good way to reliably recreate this, so I will trust your instincts and experience and chalk it up to a flaky connection between master and slave.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39452) build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer

2016-11-02 Thread dave.bott...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Bottger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39452  
 
 
  build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ted  
 
 
Components: 
 splunk-devops-plugin  
 
 
Created: 
 2016/Nov/02 6:13 PM  
 
 
Environment: 
 Jenkins ver. 1.658 , Splunk plugin 1.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Dave Bottger  
 

  
 
 
 
 

 
 We've sporadically been getting builds hanging, I just noticed that we simultaneously see log events for the LogConsumer. Could this be blocking the build? 2016-11-02 12:51:58.499-0500 [id=203] WARNING c.s.s.utils.LogConsumer#run: content length:314java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:209) at java.net.SocketInputStream.read(SocketInputStream.java:141) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:167) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271) at 

[JIRA] (JENKINS-39005) IOException: failed to send data,Bad Request incorrect index or invalid data format,Bad Request

2016-10-14 Thread dave.bott...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Bottger closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This was due to a misconfiguration on my part. The HTTP collector had rights to 'jenkins_statistic', not 'jenkins_statistics' . Emphasis on the 's' at the end. Thanks, I'm looking forward to working with this.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39005  
 
 
  IOException: failed to send data,Bad Request incorrect index or invalid data format,Bad Request   
 

  
 
 
 
 

 
Change By: 
 Dave Bottger  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed 

[JIRA] (JENKINS-39005) IOException: failed to send data,Bad Request incorrect index or invalid data format,Bad Request

2016-10-14 Thread dave.bott...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Bottger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39005  
 
 
  IOException: failed to send data,Bad Request incorrect index or invalid data format,Bad Request   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ted  
 
 
Components: 
 splunk-devops-plugin  
 
 
Created: 
 2016/Oct/14 9:27 PM  
 
 
Environment: 
 splunk-devops-plugin 1.1, cloudbees 1.658  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Dave Bottger  
 

  
 
 
 
 

 
 Splunk Enterprise, using a heavy forwarder to collect http. Getting this error:  WARNING c.s.s.utils.LogConsumer#run: content length:313java.io.IOException: failed to send data,Bad Request at com.splunk.splunkjenkins.utils.LogConsumer$1.handleResponse(LogConsumer.java:63) at com.splunk.splunkjenkins.utils.LogConsumer$1.handleResponse(LogConsumer.java:43) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:222) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:164) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:139) at com.splunk.splunkjenkins.utils.LogConsumer.run(LogConsumer.java:84) Caused by: com.splunk.splunkjenkins.utils.LogConsumer$SplunkClientError: incorrect index or invalid data format,Bad Request at com.splunk.splunkjenkins.utils.LogConsumer$1.handleResponse(LogConsumer.java:61) ... 5 more source=jenkins host=jenkins-master index=jenkins_statistics build_report.index=jenkins file.index=jenkins_artifact console_log.index=jenkins_console jenkins_config.enabled=true I am getting some data (index=jenkins, sourcetype=_json, source=jenkins) Any ideas?  
 

  
 
 
 
 

[JIRA] [active-directory] (JENKINS-16257) Active Directory Plugin - Credential exception tying to authenticate

2013-12-12 Thread dave.bott...@gmail.com (JIRA)














































Dave Bottger
 commented on  JENKINS-16257


Active Directory Plugin - Credential exception tying to authenticate















I have the same issue, but I suspect it is caused a different character(log below).
Could the same fix applied in JENKINS-12907 be used here?
https://github.com/jenkinsci/active-directory-plugin/commit/d7e074905585af53eb553a1fa05726853273c338



Dec 12, 2013 11:01:30 AM FINER hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider

Looking up group of CN=Bottger David (GARE/Chicago),OU=Americas,OU=User Accounts,DC=GIE,DC=Gimia,DC=com

Dec 12, 2013 11:01:30 AM WARNING hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser

Failed to retrieve user information for dbottger
javax.naming.NamingException: [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012 (DIR_ERROR), data 0
]; remaining name 'CN=Bottger David (GARE/Chicago),OU=Americas,OU=User Accounts,DC=GIE,DC=Gimia,DC=com





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.