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; } } }

Deployment getting stuck.

VivekPolaris

Hi All,

While I am triggering a workflow, deploymnet is getting hang. It keeps showing the below status :

bash-3.2$ ./iwodserverstatus
OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server is alive.
1 deployment is currently active.
cjp_cbol_authoring_STAGING_deploy_WEB m66 SENDING

While checking the logs at source for all 4 servers, I could not find any fail or Error mesg so unable to troubleshoot the problem in deployment.

/pjfpgcb2/docs/jpgcb_dr on each target server is having permission to receive deploymnet from source and user="ujfpbg1" group="ujfpbg" also.

I am attaching the deplyment config file and Logs for reference.

Please suggest how to track the reason of deployment hang.

Thanks in advance for all the suggestions.

--------------------------
Base od : 7.2
Target OD : 731
TS : 6.7.2
--------------------------

Find more posts tagged with

Comments

ISCBorisB

Hi All,

While I am triggering a workflow, deploymnet is getting hang. It keeps showing the below status :

While checking the logs at source for all 4 servers, I could not find any fail or Error mesg so unable to troubleshoot the problem in deployment.

/pjfpgcb2/docs/jpgcb_dr on each target server is having permission to receive deploymnet from source and user="ujfpbg1" group="ujfpbg" also.

I am attaching the deplyment config file and Logs for reference.

Please suggest how to track the reason of deployment hang.

Thanks in advance for all the suggestions.

--------------------------
Base od : 7.2
Target OD : 731
TS : 6.7.2
--------------------------

Element "filters" can occur only once within Source "pathSpecification". Also, exclusion filters are incompatible
with inclusion filters. You may want to re-configure your "...WEBL" Configuration Path Specs.

Further, with problem of that nature you should analyze Target micro logs as well as source (Base) Logs.
Finally, if Target logs will not help, divide and conquer. Temporarily comment out target Nodes deploying to only
one Node at a time and try to narrow down the list of suspects.

Drill.zip

Adam Stoller

Also - while trying to debug a hanging deployment process - verify the available disk space on each of the target systems ...

Lack of disk space on the receivers is, unfortunately, something that OpenDeploy doesn't always deal with gracefully.