nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to know the time when the current deployment started

BlueWhale

Hello,

I would like to know if there are any deployments on the server that are running from the past few minutes (which are hanged). Are there any CLTs to find this out? I know that by using CLT iwodserverstatus, we'll get current deployments and deployment name but, it won't show when it started or how long it has been running.

Is there anyway to know the active deployments (iwodserverstatus) AND the time that they started?

Environment: OD 6.2, TS 6.7.1 on Windows 2003

Thanks in advance.

Find more posts tagged with

Comments

nipper

This is available from the OD Admin GUI, but not from the command line that I know of

BlueWhale

The main purpose of this is, I want to send an alert message email to the OD administrator if there is any deployment running for more than 10 mins (say).

Anyone has any idea how to achieve this?

Thanks.

ISCBorisB

The main purpose of this is, I want to send an alert message email to the OD administrator if there is any deployment running for more than 10 mins (say).

Anyone has any idea how to achieve this?

Thanks.

What's the Deployment Logistics? Workflow, Scheduled OD Scripts, Ad hoc manual Deployments, other?
Do you want to warn just once or become a "Nasty Aunt" and continue every 10 minutes?

BlueWhale

Deployments get invoked through a workflow (external task).

I would like to send the alert once for a particular instance of deployment, if it got hung.

nipper

You *should* have a timeout on the workflow task anyway.

You *should* have them on all external tasks.

ISCBorisB

Deployments get invoked through a workflow (external task).

I would like to send the alert once for a particular instance of deployment, if it got hung.

There are many possible ways to accomplish that.

For example, you may set your WF to transition to two concurrent tasks: Deployment External Task + Dummy Task with
"N minutes" timeout. Dummy then transitions to the mail Task that upon completion may loop back to Dummy, etc. After
Deployment is done you would have to *inactivate* Dummy Task