Deployment Solution

Hi,

Has anyone encountered the scenario where rdeploy spontaneously restarts/repeats an imaging session within the same process session?

It was reported that,

1. RDeployT process reached nearly 100% and then dropped back to zero and continued again from there
2. The process did not exit
3. Automation did not reboot ;-)

Looking at the server logs is not revealing. I've in the past seen network glitches pause RDeploy but nothing like this.  The tasks are running within Linux automation and the DS server version is DS6.9SP4. This seems isolated to a single incident, and is not reproducible.

Kind Regards,
Ian./

Isn't there this "Automatically reschedule failed image tasks" Setting?

I'v had some image tasks fail at 100%.

@Edit: This should be seen in the history anyway, duh?

Hi Mistral,

I neglected to mention that this Rdeploy task is being executed in a script. We could see it start the script and launch RDeploy from our script logs. But from there it appears that to have restarted without even proceeding to the next line in the script.

Most odd...

Kind Regards,
Ian./

The only time I've ever seen something like this was when there was a file in the image that was either corrupt or had a very non standard file name (I'm afraid I can't remember which).

Rdeploy would always get to the same fixed % and then fail. I don't think it rebooted. There may have been an aggravating factor like it only happened through a firewall.

Hi Andy,

Unfortunately it's not reproducible, which isn't helpful. The image in question has been going down well for weeks, and has been successfully deployed since.

I was thinking that perhaps a network glitch somehow caused RDeploy to restart (without being externally told to do so).... there are no rdeploy logs on the server though...

Just wondered if anyone knew of a particular scenario which might trigger this (hithertoo unobserved) behaviour.

I might just have to log it under "Cosmic Rays"

I think i have seen it once or twice, but i used the built in image task (without the reschedule option). But after the image got deployed finally i didnt really care.

Hi Mistral -thanks. That confirms then that this can happen, even if we are not clear as to the why.

It was only a problem for our tech as it was a network imaging session which was taking a long time... and then to suddenly find it had re-started (and in front of the customer) did little to cheer him up..

Kind Regards,
Ian./