Have you tried running the script manually on the server by copying/pasting the script body/text from within the template to the host via the SSH terminal? Does the SSH session close? I've only seen an similar to this a couple of times. In most cases the issue was traced back to the script not executing properly on the host. You should be able to see that when running the script manually, as stated above. In other cases the issue was with the SSH daemon leaking connections. This had gone unnoticed in the environment because prior to SAM people rarely SSH'd into the server, and now SAM was creating 5-10 SSH connections to the server every five minutes. The resolution in that case I believe was to upgrade the SSH daemon on the server.
↧