Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Microsoft Windows Server 2003 R2
      Microsoft Windows 2008 server w/Tomcat
      Microsoft Windows XP SP3
      Microsoft Windows 7 x64 SP1
      Microsoft Windows Server 2012
    • Similar Issues:

      Description

      When I try to start Jenkins 1.540, it attempts to do so and eventually fails. When it fails, it tries to start again, which then fails. This repeats indefinitely. I've attached a log file from one such iteration.

      I am able to start 1.539 successfully. I've attached the log file from this as well.

        Attachments

        1. hs_err_pid1000.log
          17 kB
        2. hs_err_pid1788.log
          22 kB
        3. hs_err_pid35184.log
          24 kB
        4. hs_err_pid4584.log
          13 kB
        5. hs_err_pid4968.log
          20 kB
        6. hs_err_pid5660.log
          21 kB
        7. hs_err_pid5960.log
          21 kB
        8. jenkins.out.log
          0.8 kB
        9. jenkins 1.539.err.log
          40 kB
        10. jenkins 1.540.err.log
          27 kB

          Issue Links

            Activity

            Hide
            hx_unbanned Linards L added a comment - - edited

            Repeated update process.

            Now only updatable plugin was:

            Parameterized Trigger Plugin
            This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build.
            2.22 2.21

            Result is the same. First reboot is ok. Second - after updating plugin - total crash. Again back to v1.529.

            Show
            hx_unbanned Linards L added a comment - - edited Repeated update process. Now only updatable plugin was: Parameterized Trigger Plugin This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build. 2.22 2.21 Result is the same. First reboot is ok. Second - after updating plugin - total crash. Again back to v1.529.
            Hide
            danielbeck Daniel Beck added a comment -

            Linards L: The error you describe seems to be completely different from the original error. It looks like something's wrong with your (security realm?) configuration. What makes you think your error is the same as, or even just related to the original issue reported here?

            (Also, just in case you didn't know this: Every new comment and edit of a comment here gets send via email to everyone watching this issue, almost 70 people. 15 such notifications in two hours like the day before yesterday is a bit much. Maybe consider keeping the number of edits down.)

            Show
            danielbeck Daniel Beck added a comment - Linards L: The error you describe seems to be completely different from the original error. It looks like something's wrong with your (security realm?) configuration. What makes you think your error is the same as, or even just related to the original issue reported here? (Also, just in case you didn't know this: Every new comment and edit of a comment here gets send via email to everyone watching this issue, almost 70 people. 15 such notifications in two hours like the day before yesterday is a bit much. Maybe consider keeping the number of edits down.)
            Hide
            belpk K P added a comment -

            The issue by Linards L seems to be completely unrelated to the issue reported here.
            It would be better to create a different issue report for that, because "poluting" this issue with an unrelated issue is going to confuse people and makes it a mess to still see clearly through the issue comments, which isn't helping the original issue getting solved at all.

            Show
            belpk K P added a comment - The issue by Linards L seems to be completely unrelated to the issue reported here. It would be better to create a different issue report for that, because "poluting" this issue with an unrelated issue is going to confuse people and makes it a mess to still see clearly through the issue comments, which isn't helping the original issue getting solved at all.
            Hide
            hx_unbanned Linards L added a comment -

            Sorry for mess.

            Created new issue: https://issues.jenkins-ci.org/browse/JENKINS-21018

            Thanks again.

            Show
            hx_unbanned Linards L added a comment - Sorry for mess. Created new issue: https://issues.jenkins-ci.org/browse/JENKINS-21018 Thanks again.
            Hide
            danielbeck Daniel Beck added a comment -

            Marking as resolved again, as the user who reopened it appears to be affected by a different issue.

            Show
            danielbeck Daniel Beck added a comment - Marking as resolved again, as the user who reopened it appears to be affected by a different issue.

              People

              • Assignee:
                kohsuke Kohsuke Kawaguchi
                Reporter:
                kraai Matt Kraai
              • Votes:
                58 Vote for this issue
                Watchers:
                66 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: