<p>This is conjecture, but after watching this for almost six months here's my theory;</p>

<p>I think the jobs have to post their logs in sequential order. If you have multiple jobs, or even multiple runs of the same job that all push logs it will wait for them to complete in the order they were started. This can be troublesome if you have one hour-long build that started before a 10-minute job. The shorter one started second even if it finishes first, so will wait for the hour long one to finish before finishing itself.</p>

<p>There doesn't seem to be any fix for it, but we've learned to just ignore it and count the jobs as done if they're hanging at the logs phase.</p>

CC BY-SA 4.0
2018-06-26T12:58:00.947Z
2018-06-26T12:58:00.947Z
Alex
<p>Googling returns only this Q&amp;A:</p>

<p><a href="https://i.sstatic.net/g2a2d.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/g2a2d.png" alt="enter image description here"></a></p>

<p>It looks like that it is not a reported issue. Also combined with your remark, i.e.:</p>

<blockquote>
  <p>It always completes successfully, even with the delay.</p>
</blockquote>

<p>I wonder whether it is really an issue as I have seen a lot of logs and also weird messages while everything worked. What I do in such situation is talk with the developer of the code. In this case I would create an issue in the Jenkins bug tracker and discuss whether this is an issue and whether the developers should change the code that triggers this message.</p>

CC BY-SA 3.0
2018-04-26T21:00:06.007Z
2018-04-26T21:00:06.007Z
030
<p>We use the <a href="https://wiki.jenkins.io/display/JENKINS/AWS+CloudWatch+Logs+Publisher+Plugin" rel="nofollow noreferrer">AWS CloudWatch Logs Publisher</a> plugin on our Jenkins and most of the time the logs are sent within 2-5 seconds of the request being sent out. However, sometimes the step will hang for up to 5-10 minutes, with no errors in the console or in Jenkins' log. The job hangs with the following status message;</p>

<blockquote>
  <p>AWS CloudWatch Logs Publisher is waiting for a checkpoint on [...]</p>
</blockquote>

<p>It always completes successfully, even with the delay. </p>

<p>Has anyone seen this before? Is there anything I can do to prevent the step hanging? </p>

<jenkins><jenkins-plugins><amazon-cloudwatch>
AWS CloudWatch Logs Publisher plugin hangs on job completion
Alex
# AWS CloudWatch Logs Publisher plugin hangs on job completion

(Asked by: username_0 on 2018-01-08)

We use the [AWS CloudWatch Logs Publisher](https://wiki.jenkins.io/display/JENKINS/AWS+CloudWatch+Logs+Publisher+Plugin) plugin on our Jenkins and most of the time the logs are sent within 2-5 seconds of the request being sent out. However, sometimes the step will hang for up to 5-10 minutes, with no errors in the console or in Jenkins' log. The job hangs with the following status message;

> AWS CloudWatch Logs Publisher is waiting for a checkpoint on [...]

It always completes successfully, even with the delay.

Has anyone seen this before? Is there anything I can do to prevent the step hanging?

**Tags:** jenkins, jenkins-plugins, amazon-cloudwatch


---

## 2 answers

### Answer by username_0 on 2018-06-26. Score: 0 | Accepted answer

This is conjecture, but after watching this for almost six months here's my theory;

I think the jobs have to post their logs in sequential order. If you have multiple jobs, or even multiple runs of the same job that all push logs it will wait for them to complete in the order they were started. This can be troublesome if you have one hour-long build that started before a 10-minute job. The shorter one started second even if it finishes first, so will wait for the hour long one to finish before finishing itself.

There doesn't seem to be any fix for it, but we've learned to just ignore it and count the jobs as done if they're hanging at the logs phase.


---

### Answer by username_1 on 2018-04-26. Score: 0

Googling returns only this Q&A:

[![enter image description here](https://i.sstatic.net/g2a2d.png)](https://i.sstatic.net/g2a2d.png)

It looks like that it is not a reported issue. Also combined with your remark, i.e.:

> It always completes successfully, even with the delay.

I wonder whether it is really an issue as I have seen a lot of logs and also weird messages while everything worked. What I do in such situation is talk with the developer of the code. In this case I would create an issue in the Jenkins bug tracker and discuss whether this is an issue and whether the developers should change the code that triggers this message.


---

