-
assigned issue to
Fusion catching error?
Issue #25
closed
where does this come from?
[LOG FusionCatchers17b] srun: Node Exited:vm6:ID436395
[LOG FusionCatchers17b] srun: error: vm6: task 0: Exited with exit code 1
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: Component returned error status: 1 (Generic error)
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: Exit status: 1
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: stdErr:
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: WARNING: Cannot restart automatically because the previous log file '/mnt/storageBig6/lilli/analyses/PMP/fusionGene/result_analyze/FusionCatchers17b/folder1/fusioncatcher.log' cannot be found!
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: The workflow will be restarted from the beginning with step 1!
[ERROR FusionCatchers17b] analyze.scala:126, Component FusionCatchers17b: Killed
[INFO FusionCatchers17b] Component finished with failure (COMPONENT-FINISHED-ERROR) (2016-06-29 14:47:43)
[INFO FusionCatchers17b] Current ready queue: (empty) (READY-QUEUE 0)
Comments (2)
-
-
- changed status to closed
- Log in to comment
It was a Lilli's process. She was running a pipeline on the old cluster and vm6 crashed at some point.