You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example protect.json file provided in this repo describes a run where the input reference files are on the local file system at `/home/ubuntu/protect-work/protect-reference-files/hg38-reference-files` and the input fastqs are in `/home/ubuntu/protect-work/samples/`.
507
+
The example protect.json file provided in this repo describes a run where the input reference files
508
+
are on the local file system at `/home/ubuntu/protect-work/protect-reference-files/hg38-reference-files`
509
+
and the input fastqs are in `/home/ubuntu/protect-work/samples/`.
510
+
511
+
# Troubleshooting
512
+
## Installation
513
+
#### 1. packaging related issues
514
+
If you see
515
+
516
+
Traceback (most recent call last):
517
+
File "<string>", line 1, in <module>
518
+
File "/mnt/dstew/protect/setup.py", line 6, in <module>
519
+
from packaging.version import LegacyVersion as _LegacyVersion
520
+
ImportError: No module named packaging.version
521
+
522
+
523
+
Then it is mostly due to a version of setuptools >= 39.0.1. The fix for this is to run the
524
+
following line before reattempting to install protect.
525
+
526
+
pip install packaging
527
+
528
+
## Errors during Runtime
529
+
### How to read and understand an error arising during/at the end of the run
530
+
Since ProTECT is written in TOIL, the error printed on a failed job is the logfile for the worker
531
+
that failed to execute the python function that was the failed job.
532
+
533
+
An example error is shown here with line numbers manually added at the beginning for annotation
534
+
purposes:
535
+
536
+
01: The job seems to have left a log file, indicating failure: 'merge_mhc_peptide_calls' g/f/jobO4yiE4
537
+
02: g/f/jobO4yiE4 ---TOIL WORKER OUTPUT LOG---
538
+
03: g/f/jobO4yiE4 INFO:toil:Running Toil version 3.8.0-4c83830e4f42594d995e01ccc07b47396b88c9e7.
539
+
04: g/f/jobO4yiE4 INFO:toil.fileStore:Starting job ('merge_mhc_peptide_calls' g/f/jobO4yiE4) with ID (972acf421c864831d756dec528bb9cc2a4d3c281).
15: g/f/jobO4yiE4 File "/home/ucsc/arjun/tools/protect_toil_clean/local/lib/python2.7/site-packages/protect/binding_prediction/common.py", line 566, in merge_mhc_peptide_calls
551
+
16: g/f/jobO4yiE4 raise RuntimeError('No peptides available for ranking')
552
+
17: g/f/jobO4yiE4 RuntimeError: No peptides available for ranking
553
+
18: g/f/jobO4yiE4 ERROR:toil.worker:Exiting the worker because of a failed job on host sjcb10st7
554
+
19: g/f/jobO4yiE4 WARNING:toil.jobGraph:Due to failure we are reducing the remaining retry count of job 'merge_mhc_peptide_calls' g/f/jobO4yiE4 with ID g/f/jobO4yiE4 to 0
555
+
20: g/f/jobO4yiE4 WARNING:toil.jobGraph:We have increased the default memory of the failed job 'merge_mhc_peptide_calls' g/f/jobO4yiE4 to 2147483648 bytes
556
+
557
+
* Line 1 tells you which function failed.
558
+
* Line 6 is where the actual error starts (the line starting with `Traceback`)
559
+
* Line 16 tells you the tool failed with a RuntimeError and contains the actual error message. In
560
+
this case, the tool found no peptides that were available for ranking.
561
+
* The line numbers will vary with different tools and dependin gon how jobs were scheduled, however
562
+
a rule of thumb is to look for the string `RuntimeError` (the most common error thrown by ProTECT)
563
+
or just `Error` and then read the error message.
564
+
565
+
### A note on non-deterministic errors with RADIA
566
+
It has been noticed that RADIA sometimes fails non-deterministically on one (or rarely more)
567
+
chromosome in a sample during a ProTECT run. The error is highly non-informative since we currently
568
+
do not store logs from tools (see BD2KGenomics/protect#275). The error looks similar to this:
569
+
570
+
Z/O/job1uH92D ---TOIL WORKER OUTPUT LOG---
571
+
Z/O/job1uH92D INFO:toil:Running Toil version 3.8.0-4c83830e4f42594d995e01ccc07b47396b88c9e7.
572
+
Z/O/job1uH92D INFO:toil.fileStore:Starting job ('run_filter_radia' Z/O/job1uH92D) with ID (0e8bb5ea5d785324b5abce7b384bf5b99140aa6c).
573
+
Z/O/job1uH92D WARNING:toil.fileStore:LOG-TO-MASTER: Job used more disk than requested. Please reconsider modifying the user script to avoid the chance of failure due to incorrec
574
+
tly requested resources. Job 'run_filter_radia' Z/O/job1uH92D used 104.10% (34.3 GB [36816449536B] used, 32.9 GB [35367908263B] requested) at the end of its run.
575
+
Z/O/job1uH92D Traceback (most recent call last):
576
+
Z/O/job1uH92D File "/home/ucsc/arjun/tools/dev/toil_clean/src/toil/worker.py", line 340, in main
Z/O/job1uH92D File "/home/ucsc/arjun/tools/protect_toil_clean/local/lib/python2.7/site-packages/protect/mutation_calling/radia.py", line 238, in run_filter_radia
Z/O/job1uH92D ERROR:toil.worker:Exiting the worker because of a failed job on host sjcb10st1
590
+
Z/O/job1uH92D WARNING:toil.jobGraph:Due to failure we are reducing the remaining retry count of job 'run_filter_radia' Z/O/job1uH92D with ID Z/O/job1uH92D to 0
591
+
592
+
The fix for this is to just rerun protect with the same jobstore (if you haven't specified
593
+
`--clean always`) with the `--restart` flag. I.e. run exactly the same command as the original run
594
+
with `--restart` appended at the end of the command.
0 commit comments