• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Jenkins 1.522 on Ubuntu 13.04, nodes on solaris sparc, solaris x86 and redhat linux.

      Since we upgraded from Jenkins 1.520 to 1.522 the Clock Difference is broken on the Manage Nodes page. Master and all slaves are in sync but Jenkins reports something completely different. Master and any slave running on the same server as master is reported correctly.

      We have 3 Jenkins servers displaying the same symptoms.

          [JENKINS-18671] Clock Difference broken on Manage Nodes page

          Andréas Berg created issue -
          sogabe made changes -
          Link New: This issue is related to JENKINS-18438 [ JENKINS-18438 ]

          N added a comment -

          Same here, nodes from 3months ahead to 3 days behind.
          Upgraded from 1.519 to 1.522.

          N added a comment - Same here, nodes from 3months ahead to 3 days behind. Upgraded from 1.519 to 1.522.
          Andréas Berg made changes -
          Labels New: jenkins slave
          Andréas Berg made changes -
          Description Original: Since we upgraded from Jenkins 1.520 to 1.522 the Clock Difference is broken on the Manage Nodes page. Master and all slaves are in sync but Jenkins reports something completely different. Master and any slave running on the same server as master is reported correctly. New: Since we upgraded from Jenkins 1.520 to 1.522 the Clock Difference is broken on the Manage Nodes page. Master and all slaves are in sync but Jenkins reports something completely different. Master and any slave running on the same server as master is reported correctly.

          We have 3 Jenkins servers displaying the same symptoms.

          Same here: one node is 15 mins ahead, the other one is 4d 16h ahead.
          Is it possible that this is related to remote file system problems e.g. described in 10771?

          Marcel Beister added a comment - Same here: one node is 15 mins ahead, the other one is 4d 16h ahead. Is it possible that this is related to remote file system problems e.g. described in 10771?

          Andréas Berg added a comment -

          This issue appeared for us after upgrading from 1.520 to 1.522. I've never seen this behaviour before so I doubt its realted to #10771 as that issue has existed for almost two years.

          Andréas Berg added a comment - This issue appeared for us after upgrading from 1.520 to 1.522. I've never seen this behaviour before so I doubt its realted to #10771 as that issue has existed for almost two years.

          A manual refresh is done almost instantly, the time difference remains the same here.

          Marcel Beister added a comment - A manual refresh is done almost instantly, the time difference remains the same here.

          same here, time differences between "3 mo 7 days behind" to "43 years ahead" .

          Florian Doersch added a comment - same here, time differences between "3 mo 7 days behind" to "43 years ahead" .

          Marcel Beister added a comment - - edited

          @Andréas Berg: #10771 can have multiple reasons that lead to the same problem (remote-fs error) and differences in system time can lead to errors in network communication. Maybe there is also an error if the system just thinks that the system time is different, but I'm also not really convinced regarding that theory

          Marcel Beister added a comment - - edited @Andréas Berg: #10771 can have multiple reasons that lead to the same problem (remote-fs error) and differences in system time can lead to errors in network communication. Maybe there is also an error if the system just thinks that the system time is different, but I'm also not really convinced regarding that theory

            Unassigned Unassigned
            epkabeg Andréas Berg
            Votes:
            14 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: