Symptom | task being sent to the MC do not run, they seem to vanish |
ERROR Message | In the MC logs you can find the error: no suitable FSS became alive |
Solution | synchronize the MC and OC clocks, e.g. using an ntp server. Also check the clock on the FSSs |
- The Workflow to FSS mapping table does not include the workflow that is being run or the FSS that this workflow was assigned to is not running.
- There is a time difference between the OC you are using to send the task and the MC. This will cause the task to either not run at all (if the time difference between the OC and MC is greater than the maxlatetime defined in the MC configuration file) or the task will run at a later time. In the first case the error message in the MC will be : no suitable FSS became alive. in the second case the workflow will run later.
