Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • yuliu
    Junior Member
    • Jul 2012
    • 5

    bowtie error

    Hi,

    I integrate bowtie2 into my pipeline, sometimes I got an error message like:

    Warning: Could not open read file "/tmp/2423.unp" for reading; skipping...
    Error: Encountered internal Bowtie 2 exception (#1)

    then, bowtie will be termintated.

    My OS is the latest ubuntu.

    Does anyone can help me figure it out?

    Thanks

    -
  • ThePresident
    Member
    • Jun 2012
    • 72

    #2
    I know it sound crazy, but it happened to me: have you enough space on your HD?

    Comment

    • yuliu
      Junior Member
      • Jul 2012
      • 5

      #3
      space is not an issue. I used my pipeline to analyze 10 datasets. I got the error message when bowtie2 was processing the second dataset, then bowtie2 continued to the third one, and successfully processd all the following dataset.
      So space is not an issue.

      Comment

      • westerman
        Rick Westerman
        • Jun 2008
        • 1104

        #4
        Just to pound on the space issue some more, what is the size of your /tmp? This can be different that your normal hard drive space.

        It is quite possible that if the second dataset was large then when bowtie died on the second dataset because /tmp was full nothing got written to /tmp thus allowing bowtie to process the other datasets.

        Comment

        • yuliu
          Junior Member
          • Jul 2012
          • 5

          #5
          good points! Will check my size of /tmp.
          Thank you, thePresident & westerman!

          Cannot understand why bowtie moves the reads file to /tmp.

          Comment

          • bharat_iyengar
            Member
            • Dec 2012
            • 20

            #6
            i got this error while running bowtie (almost near end)

            Code:
            Error while flushing and closing output
            terminate called after throwing an instance of 'int'
            Aborted (core dumped)
            is it because of lack of memory space or anything??

            Comment

            • dlemas
              Junior Member
              • Jan 2013
              • 1

              #7
              I am new to bowtie; however when i downloaded the windows version and worked through the tutorial . . everything went well. I have since downloaded the linux source code and compliled it within cygwin and when I start to run the tutorial I get the following error:

              $ ./bowtie-build e_coli reads/e_coli_1000.fq
              Settings:
              Output files: "reads/e_coli_1000.fq.*.ebwt"
              Line rate: 6 (line is 64 bytes)
              Lines per side: 1 (side is 64 bytes)
              Offset rate: 5 (one in 32)
              FTable chars: 10
              Strings: unpacked
              Max bucket size: default
              Max bucket size, sqrt multiplier: default
              Max bucket size, len divisor: 4
              Difference-cover sample period: 1024
              Endianness: little
              Actual local endianness: little
              Sanity checking: disabled
              Assertions: disabled
              Random seed: 0
              Sizeofs: void*:4, int:4, long:4, size_t:4
              Input files DNA, FASTA:
              e_coli
              Error: could not open e_coli
              Total time for call to driver() for forward index: 00:00:00
              Command: ./bowtie-build e_coli reads/e_coli_1000.fq

              Basically, it does not read the e_coli file? Any thoughts or similar problem?

              Comment

              • westerman
                Rick Westerman
                • Jun 2008
                • 1104

                #8
                Originally posted by dlemas View Post

                Command: ./bowtie-build e_coli reads/e_coli_1000.fq

                Basically, it does not read the e_coli file? Any thoughts or similar problem?
                1) Whenever someone on the forum complains about a program not being able to read a file then the immediate suspicion is that the program is correct and the person made a mistake. In these cases if the person could include a 'ls -l' of the directory in question showing that the file exists, is readable and is of reasonable size then then rest of us could rule out the very likely human error.

                2) In your case, if I was to hazard a guess, I suspect that you have your command line parameters turned around. That 'reads/e_coli_1000.fq' should be first since it is the reference and 'e_coli' should be last since it is the base name of your output file.

                Comment

                Latest Articles

                Collapse

                • SEQadmin2
                  Proteomic Platforms: How to Choose the Right Analytical Strategy to Improve Detection and Clinical Applications
                  by SEQadmin2


                  Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.

                  The systematic characterization of the human proteome has
                  ...
                  07-20-2026, 11:48 AM
                • SEQadmin2
                  Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
                  by SEQadmin2



                  Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
                  ...
                  07-09-2026, 11:10 AM
                • SEQadmin2
                  Cancer Drug Resistance: The Lingering Barrier to Rising Survival
                  by SEQadmin2



                  Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

                  There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
                  07-08-2026, 05:17 AM

                ad_right_rmr

                Collapse

                News

                Collapse

                Topics Statistics Last Post
                Started by SEQadmin2, Yesterday, 12:17 PM
                0 responses
                11 views
                0 reactions
                Last Post SEQadmin2  
                Started by SEQadmin2, 07-23-2026, 11:41 AM
                0 responses
                11 views
                0 reactions
                Last Post SEQadmin2  
                Started by SEQadmin2, 07-20-2026, 11:10 AM
                0 responses
                23 views
                0 reactions
                Last Post SEQadmin2  
                Started by SEQadmin2, 07-13-2026, 10:26 AM
                0 responses
                37 views
                0 reactions
                Last Post SEQadmin2  
                Working...