intersectBed error: ${0%/*}/bedtools intersect "$@"

771 views
Skip to first unread message

pvz...@umich.edu

unread,
Dec 18, 2015, 6:24:48 PM12/18/15
to bedtools-discuss
Hi,
I am encountering an error when running: intersectBed -wa -s -c -a file1.bed -b file2.bed > output.bed, 
/usr/local/bin/intersectBed: line 2: 23109 Killed                  ${0%/*}/bedtools intersect "$@"

I tried running multiple times with different input files (also sorted files), and kept getting the same error, but with a different number after line 2: _____. 

Strangely enough, yesterday when I ran the same thing it seemed to work fine. 

Can you help?
Petra

Aaron Quinlan

unread,
Dec 21, 2015, 11:50:09 AM12/21/15
to bedtools...@googlegroups.com
Hi Petra,

Could you try running the following command, as unlike the intersectBed bash script you are using, it will run the actual bedtools executable and therefore hopefully give you deeper insight into the source of the problem:

bedtools intersect -wa -s -c -a file1.bed -b file2.bed > output.bed

Best,
Aaron

--
You received this message because you are subscribed to the Google Groups "bedtools-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bedtools-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

anton...@gmail.com

unread,
May 18, 2016, 8:16:26 AM5/18/16
to bedtools-discuss
I am confronted with the very same problem. If I use "intersectBed" I get an error message like this:

intersectBed -wo -a 1kb.bed -b ENCFF000STO.bam
/usr/bin/intersectBed: line 2: 19766 Killed                  ${0%/*}/bedtools intersect "$@"

Following Aron's advice, I get an even more cryptic error message:

intersect -wo -a 1kb.bed -b ENCFF000STO.bam
Killed

I am using bedtools v2.25.0.

Anton

anton...@gmail.com

unread,
Aug 18, 2016, 7:59:47 AM8/18/16
to bedtools-discuss
I was just wondering if anyone has info on this problem (bug?). I am still running into this problem with various input files. Right now I am using bedtools v2.26.0.

Anton

Ryan Dale

unread,
Aug 18, 2016, 8:56:39 AM8/18/16
to bedtools...@googlegroups.com

Any chance you are running this on a cluster? Some clusters show a "Killed" message like this when a job on an interactive node runs out of allocated memory. How does it work with smaller input files or more memory?

-ryan

liaomi...@gmail.com

unread,
Apr 23, 2018, 10:08:03 AM4/23/18
to bedtools-discuss
Hi Petra,

Have you solved this problem? I also met this problem for over one week and have no idea to handle it. If you have overcome the problem, may you please provide some advice? Thanks!

Mingzhi




在 2015年12月18日星期五 UTC-8下午3:24:48,pvz...@umich.edu写道:
Reply all
Reply to author
Forward
0 new messages