Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD 5 hangs when deployment fails
tvaughan
Hi,
I'm running OD 5 with all the latest patches and hoo-haws on Solaris 2.8.
Has anyone else noticed that even with the -async flag on the iwodstart command, if you kick off a job that tries to deploy to some machine and the jobs fails for firewall reasons or a syntax error in your deployment XML, the iwodstart command won't cleanly exit?
I'll never get an error code out of that deployment, and furthermore, the next time I try to run that deployment (say, with a different filelist), it'll say "sorry, that deployment is already being run. Try again later."
Any tips out there to get a little bit better behaviour?
Thanks.
Tom
Find more posts tagged with
Comments
Migrateduser
Running with -async will only tell you that the deployment was launched, but not whether it ran successfully.
If you are getting the "deployment already running" message, then the deployment thread is still active. You can override that by specifying
-inst <unique_name> when starting the deployment job.
Todd Scallan
Senior Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
tvaughan
Ahhh. . . .the -inst flag. Thanks for the info.
Semi-troubling, however, is that if you use the -inst flag and the -async flag and you just blindly shoot off all these deployment events that don't complete and don't die, the lack of a non-zero return code means you can quite easily pile up dozens or hundreds of OD attempts before the next time the server is bounced.
Is there anyway, short of parsing log files, to tell the user that the deployment didn't actually go well?
Thanks,
Tom
Migrateduser
You could call a DNR script that gets triggered on deployment failure and sends a notification, such as an email. The DNR script could parse the in-memory log if you want to provide some details about the deployment job in the notification.
Or a user could look at which deployments are running/completed/failed via the Admin UI.
Todd Scallan
Senior Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com