When publishing, we see items go to
Waiting for deployment and then remain there. In the content delivery logging, we can see that deployment is complete, and in the transport log on the CM we can see that the deployment appears to be successful.
On a working system, we can see that in the transport log, there are several polling attempts before finally a success status is reached, and the state file is remotely deleted. On our problematic system we see that success is reached on the first polling attempt. (Both behaviours could be normal, perhaps depending on timing.)
The problem is that even though we can see success reported in the transport log, the item remains in the publish queue at
Waiting for deployment. What is the cause likely to be?
Version: 2013 SP1 HR1
Update: The problematic system started out as a scale-out, but we've stripped it back down to a simpler scenario. So we have a single deployer, and we're conducting our tests with a single publisher running. The working systems have, as far as we can tell, the same version of everything installed. The transport runs over https when it leaves the CM, but the secure connection ends at a network device before it reaches the deployer application, so the deployer application sees plain-old HTTP coming in. As far as we can tell this is transparent to Tridion, although we're looking at confirming this. For the rest, as far as we know, the environments are very similar.
Update: As a test, we have configured the publisher from the working environment to use the database of the problematic environment. We can successfully publish this way. This seems to point clearly to a problem in CM rather than in CD.