Closed wx2022 closed 2 years ago
Can you rename your FASTQs (to remove %
from them) and start over?
I think %
in the file name is the culprit?
Thanks Jin! When I tried to rename the FASTQs and start over, I saw the python version conflict error again. So I had to uninstall and reinstall the pipeline's conda envs. However, the pipeline's second conda env (encode-chip-seq-pipeline-macs2) wasn't installed correctly, and it gave me the following errors:
CondaVerificationError: The package for certifi located at /work/wx74/.conda/pkgs/certifi-2021.10.8-py37h06a4308_2 appears to be corrupted. The path 'lib/python3.7/site-packages/certifi-2021.10.8-py3.7.egg-info/not-zip-safe' specified in the package manifest cannot be found.
CondaVerificationError: The package for certifi located at /work/wx74/.conda/pkgs/certifi-2021.10.8-py37h06a4308_2 appears to be corrupted. The path 'lib/python3.7/site-packages/certifi/init.py' specified in the package manifest cannot be found.
CondaVerificationError: The package for certifi located at /work/wx74/.conda/pkgs/certifi-2021.10.8-py37h06a4308_2 appears to be corrupted. The path 'lib/python3.7/site-packages/certifi/main.py' specified in the package manifest cannot be found.
CondaVerificationError: The package for certifi located at /work/wx74/.conda/pkgs/certifi-2021.10.8-py37h06a4308_2 appears to be corrupted. The path 'lib/python3.7/site-packages/certifi/cacert.pem' specified in the package manifest cannot be found.
CondaVerificationError: The package for certifi located at /work/wx74/.conda/pkgs/certifi-2021.10.8-py37h06a4308_2 appears to be corrupted. The path 'lib/python3.7/site-packages/certifi/core.py' specified in the package manifest cannot be found.
ClobberError: This transaction has incompatible packages due to a shared path. packages: defaults/linux-64::libwebp-base-1.2.0-h27cfd23_0, defaults/linux-64::libwebp-1.2.0-h89dd481_0 path: 'bin/webpinfo' ...
When I did " bash scripts/uninstall_conda_env.sh" in the chip-seq-pipeline2 folder, only encode-chip-seq-pipeline was removed but not encode-chip-seq-pipeline-macs2. Do you know how to remove the encode-chip-seq-pipeline-macs2 completely? Thanks!
After removing the corrupted pkg, uninstalling and re-installing the pipeline's envs, I managed to fix the python version conflicts. After renaming my FASTQs without %, the pipeline ran successfully! Thanks so much again for your help, Jin! I appreciate it a lot!
That sounds great. I am closing this issue.
Describe the bug
The pipeline fails when doing cross correlation analysis. Please see the errors below:
==== NAME=chip.xcor, STATUS=RetryableFailure, PARENT= SHARD_IDX=1, RC=1, JOB_ID=402477 START=2022-02-04T03:58:57.092Z, END=2022-02-04T03:59:35.114Z STDOUT=/work/wx74/chip-seq-pipeline2-results/OP_1/test/chip/15cee7a3-e687-47fb-aaf2-8e022481ee9a/call-xcor/shard-1/execution/stdout STDERR=/work/wx74/chip-seq-pipeline2-results/OP_1/test/chip/15cee7a3-e687-47fb-aaf2-8e022481ee9a/call-xcor/shard-1/execution/stderr STDERR_CONTENTS= Traceback (most recent call last): File "/work/wx74/.conda/envs/encode-chip-seq-pipeline-spp/bin/encode_task_xcor.py", line 156, in
main()
File "/work/wx74/.conda/envs/encode-chip-seq-pipeline-spp/bin/encode_task_xcor.py", line 144, in main
args.chip_seq_type, args.exclusion_range_min, args.exclusion_range_max)
File "/work/wx74/.conda/envs/encode-chip-seq-pipeline-spp/bin/encode_task_xcor.py", line 105, in xcor
run_shell_cmd(cmd1)
File "/work/wx74/.conda/envs/encode-chip-seq-pipeline-spp/bin/encode_lib_common.py", line 359, in run_shell_cmd
raise Exception(err_str)
Exception: PID=193447, PGID=193447, RC=1, DURATION_SEC=20.2
STDERR=Loading required package: caTools
Error in pdf(file = iparams$output.plot.file, width = 5, height = 5) :
invalid 'file' argument 'H3K4me1%OP9_TGCGCAAT_1.trim_50bp.srt.filt.no_chrM.15M.cc.plot.pdf'
Execution halted
OS/Platform
conda 4.9.0
).Caper configuration file
Paste contents of
~/.caper/default.conf
.Input JSON file
Paste contents of your input JSON file.
Troubleshooting result
If you ran
caper run
without Caper server then Caper automatically runs a troubleshooter for failed workflows. Find troubleshooting result in the bottom of Caper's screen log.If you ran
caper submit
with a running Caper server then first find your workflow ID (1st column) withcaper list
and runcaper debug [WORKFLOW_ID]
.Paste troubleshooting result.