Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36227

Logstash plugin Global configure error

    Details

    • Similar Issues:

      Description

      As discussed with Rusty - The global configuration in the Jenkins interface is reporting “not found” errors for both the ElasticSearch URL and Port. I can connect to Elasticsearch from the command line on the Jenkins server to any one of the elasticsearch nodes in my cluster (using curl).

      No user name or password is required but even after uninstalling and deleting all the plugins config files these fields are populate.

      ERROR
      
      HTTP ERROR 404
      
      Problem accessing /configureTools/descriptorByName/LogstashInstallation/checkHost. Reason:
      
          Not Found
      Powered by Jetty://
      
      ERROR
      
      HTTP ERROR 404
      
      Problem accessing /configureTools/descriptorByName/LogstashInstallation/checkInteger. Reason:
      
          Not Found
      

      java version "1.7.0_101"

      The Jenkins version from the config file is:
      <version>2.11</version>

      The Logstash-plugin version is: 1.2.0

        Attachments

          Activity

          Hide
          sna55y Chris Broll added a comment -

          That looks promising, how do i get an hpi file?

          Show
          sna55y Chris Broll added a comment - That looks promising, how do i get an hpi file?
          Hide
          srotsch Stefan Rotsch added a comment -

          I assume "clone the repo and run 'mvn package'" is not the kind of answer you're expecting, so feel free to grab mine from Google Drive: https://drive.google.com/open?id=0Bzt-UfZNB3nyVEstUGhDdEljcG8

          Please be aware this is a custom build, so it might burn your house, kill your kitten, ... (you know the drill).

          Show
          srotsch Stefan Rotsch added a comment - I assume "clone the repo and run 'mvn package'" is not the kind of answer you're expecting, so feel free to grab mine from Google Drive: https://drive.google.com/open?id=0Bzt-UfZNB3nyVEstUGhDdEljcG8 Please be aware this is a custom build, so it might burn your house, kill your kitten, ... (you know the drill).
          Hide
          sna55y Chris Broll added a comment -

          That's exactly the kind of answer I was looking for, appreciate the link!

          Show
          sna55y Chris Broll added a comment - That's exactly the kind of answer I was looking for, appreciate the link!
          Hide
          sna55y Chris Broll added a comment -

          That has done the trick. I can confirm that the "host name" and "port" entry now no longer gives a 404.

          The UI is still populating the "user name" and "password" fields but when viewing jenkins.plugins.logstash.LogstashInstallation.xml they are empty.

          The build info is being indexed by elasticsearch.

          Show
          sna55y Chris Broll added a comment - That has done the trick. I can confirm that the "host name" and "port" entry now no longer gives a 404. The UI is still populating the "user name" and "password" fields but when viewing jenkins.plugins.logstash.LogstashInstallation.xml they are empty. The build info is being indexed by elasticsearch.
          Hide
          mwinter69 Markus Winter added a comment -

          with v2.0.0 you specify the complete URL for elasticsearch.

          Show
          mwinter69 Markus Winter added a comment - with v2.0.0 you specify the complete URL for elasticsearch.

            People

            • Assignee:
              Unassigned
              Reporter:
              sna55y Chris Broll
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: