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

Significant uptick in "Collision detected" log messages

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • core

      As of today (Jan 05) the builds of Jenkins core deployed in Code Valet are starting to log "Collision detected. timestamp=1515197742000, expected=1515193821000 "

      It's unclear to me why this is happening but this log message has never been spotted before in Code Valet and is starting to crop up on completely idle master instances.

      I think this might be a "canary" chirping that something is wrong with some recent changes in master but I haven't the slightest idea what they might be. Perhaps oleg_nenashev knows?

      See: https://canary.codevalet.io/issue/429176403

          [JENKINS-48830] Significant uptick in "Collision detected" log messages

          R. Tyler Croy created issue -
          R. Tyler Croy made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: core [ 21134 ]
          Key Original: INFRA-1465 New: JENKINS-48830
          Workflow Original: classic default workflow [ 225020 ] New: JNJira + In-Review [ 225021 ]
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]

          R. Tyler Croy added a comment -

          Oleg, I'm temporarily assigning this to you. Would you mind double-checking to see if any of the recent Remoting changes could be related to this?

          If not, feel free to re-assign it back and I'll keep hunting :-/

          R. Tyler Croy added a comment - Oleg, I'm temporarily assigning this to you. Would you mind double-checking to see if any of the recent Remoting changes could be related to this? If not, feel free to re-assign it back and I'll keep hunting :-/
          R. Tyler Croy made changes -
          Assignee Original: R. Tyler Croy [ rtyler ] New: Oleg Nenashev [ oleg_nenashev ]

          Oleg Nenashev added a comment -

          rtyler If you are using 2.98/2.99, update to 2.100 (https://groups.google.com/forum/#!topic/jenkinsci-dev/-VQ5YU0yYhg). Otherwise please provide...

          0) Jenkins version
          1) Full stacktrace of the issue
          2) System log for the timeframe of the issue
          3) If this happens on the agent, Remoting version and Remoting agent log

          P.S: I highly recommend using a https://github.com/jenkinsci/support-core-plugin/ for any remoting-related issues

          Oleg Nenashev added a comment - rtyler If you are using 2.98/2.99, update to 2.100 ( https://groups.google.com/forum/#!topic/jenkinsci-dev/-VQ5YU0yYhg ). Otherwise please provide... 0) Jenkins version 1) Full stacktrace of the issue 2) System log for the timeframe of the issue 3) If this happens on the agent, Remoting version and Remoting agent log P.S: I highly recommend using a https://github.com/jenkinsci/support-core-plugin/ for any remoting-related issues
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ] New: R. Tyler Croy [ rtyler ]

          R. Tyler Croy added a comment -

          After digging much deeper today, it looks like something serious with kubernetes went wrong outside of the context of Jenkins, so I'm going close this out.

          R. Tyler Croy added a comment - After digging much deeper today, it looks like something serious with kubernetes went wrong outside of the context of Jenkins, so I'm going close this out.
          R. Tyler Croy made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            rtyler R. Tyler Croy
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: