8

On a T2013SP1 environment which was working perfectly well for a long time, I suddenly get all publish items stuck at 'Waiting for Deployment' state.

I checked in the (linux based) deployer logs and there are no errors, and indeed the content is published to the broker database and *.state.xml files are created in the deployer temp directory stating that deployment is successful. It seems that somehow the publisher is unable to poll for these (however there are no errors or useful information in the publisher/transport logs).

Restarting the publisher service on the CM box and deployer process on the Linux box does not help, even when I clear the publishing queue and deployer temp directory - when I publish something new I get the same behaviour.

  • Is there anything in the Publisher logs? I've had permission issues in the past (that have prevented the state files from being deleted) that were reported by the Publisher. – Jonathan Williams Apr 5 '16 at 14:41
5

I had a similar issue with one of my deployers. It was working fine and all of a sudden it left the publishing transactions in "Deploying" state. The deployer was deploying properly (checked the broker and things were correctly published) and leaving the instruction for the transport service to update the state of the transaction. However, the transport service won't pickup such instruction file hence the publishing transaction remained as "Deploying".

What I did to troubleshoot the issue was:

  1. Check the deployer logs (which should be fine as it is doing its job correctly)
  2. Check the transport logs (and Event Viewer inthe CMS Server)

In my case, I found some logs complaining about a key marked for deletion trying to be updated (some DB problem). I triple-checked everything and all was properly setup.

After trying the common problem solvers, such as restarting the transport service (and the Publisher) as well as the deployers, the transactions still remained as "Deploying". At that point, my last resort was to restart the CMS server, as for some reason, the transport service was stuck and unable to get the status updates from the deployer and restarting the service itself wasn't enough.

After restarting the CMS server (where the transport service runs), publishing started to work just fine again.

I know this answer doesn't explain the reason for the issue, but there are things in a windows server that sometimes can't be explained :).

I hope this helps and as any Help Desk / Support guy would say, restart the server and call me back if the error persist.

  • Indeed - a CMS server restart (coupled with a deployer temp folder cleandown and restart) fixed it... A bit of a mystery though. – Will Price Apr 5 '16 at 15:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.