[JIRA] [core] (JENKINS-31230) Jenkins job started by timer at an unexpected time

[db...@cloudbees.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is an issue tracker, not a support site. Furthermore, 1.596.x and 1.609.x are no longer supported, you need to show a bug exists on 1.625.x to get attention in this tracker. 
To get help, ask the jenkinsci-users mailing list, or in #jenkins on Freenode. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31230 
 
 
 
  Jenkins job started by timer at an unexpected time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [core] (JENKINS-31230) Jenkins job started by timer at an unexpected time

[ludovic.vercruy...@atos.net (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ludovic Vercruysse created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31230 
 
 
 
  Jenkins job started by timer at an unexpected time  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 28/Oct/15 1:39 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ludovic Vercruysse 
 
 
 
 
 
 
 
 
 
 
Dear, 
We are currently using Jenkins 1.596.3 and we have faced an issue with a job which was not started at the correct timestamp by the timer. 
The job is configured to be executed automatically on a daily basis at 7:30pm CEST. The job execution has been correctly triggered and the build has started at 7:30pm CEST, as expected. 
However, the logs of the build show the following error message: 

 

Looks like the node went offline during the build. Check the slave log for the details.
FATAL: channel is already closed
 

 
It seems that there has been a communication issue between our Jenkins master (hosted on a VM) and our Jenkins slave (a physical server) Therefore, the job has failed. 
At that time, we did not face any hardware issue on the servers. In the jenkins logs, except if I missed it, I did not find any reference of this communication issue, therefore, I cannot identify the root cause of this communication issue.