workflow engine and opendeploy failing

hmm, not even sure where to start on this one.

We have an installation of Teamsite 5.5.2 and opendeploy 5.5.1. I know this is old, but the system was supposed to be replaced a while back, and in the mean time, we're stuck with supporting it.

In order to zip up some log files last Thursday we did a stop start on iw.server. Since then the system hasn't been reliable.

The symptoms are.

1) open deploy service fails. (iwodserverstatus gives 2Connection could not be established" error)
2) The workflow engine does not run any external task, although jobs do appear in the workflow.

Everything else seems okay, and users are happily editing content, but just can't do anything with it.

We've stopped and started both teamsite and opendeploy many times now, including rebooting the entire server. This does bring back functionality, but only for it to fail again after a few minutes.

During this time we successfully submit content, which runs workflows which calls external task which in turn runs delpoyments through iwodstart. All of this seem fine a doesn't fail half way through. By that, I mean that when it eventually fails, the last thing in all of our logs is the succesfully compleation of the previous job. The next one just doesn't appear because the workflow has refused to start running more external tasks.

I'm tearing my hair out over this one. I don't understand why the workflow would fail AND opendeploy would go done, these are separate services. There must be something else underlying this that I haven't figured out.

The server has been given the okay from the point of view of the hardware from our unix guys, and isn't running low on memory or diskspace. It's on average only got a 15% cpu utilisation.

Argghhh. I really don't know what to do. The last thing in the iwserver says that teamsite has started succesfully.

If I only had one log with an error message in it I'd have something to go on.

_any_ suggestions welcome,

Thanks, Rob

Find more posts tagged with

Comments

nipper

Sounds liek something happened to your external task script. You will need to try to run it from the command line to see what happens.

You can get the actual name from the WFT, run that, with a JOBID and TASKID of a job that is hung. Debug from there or post the results if you need help.

Andy

rob1234

Sounds liek something happened to your external task script. You will need to try to run it from the command line to see what happens.

You can get the actual name from the WFT, run that, with a JOBID and TASKID of a job that is hung. Debug from there or post the results if you need help.

Andy

but opendeploy was failing even if no jobs were running.

As it happens we restarted the services last night after add more monitoring on the server, and it has been okay since. It _seems_ to be okay, and has been running reliably all morning, I'm still non the wiser as to what was causing the problem though.

PankajK

Rob,

I had seen the external tasks hanging problem once, see if this support article helps:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=54739

OpenDeploy failing might be another issue.

- PK