Opened 6 years ago
Closed 6 years ago
#799 closed issue (handled)
error 134; ARB crashes when opening any database. *** buffer overflow detected ***: arb_ntree terminated
Reported by: | guest | Owned by: | westram |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ARB_NTREE | Version: | arb-6.0.2 |
Keywords: | error 134, unable to open any database, buffer overflow, arb_ntree | Cc: | vthiel@… |
Description (last modified by westram)
Hi.
Can anyone help me with this issue? I cannot open ANY database anymore…
After the program crashed when I filtered sequences by the 'keep sequences that are marked' function, ARB will not open any of my databases (including unchanged public SILVA databases) anymore.
I am using ARB version 6.0.2 on an 16-core machine (Intel Xeon® CPU ES-2697 v3 @ 2.60 GHz x 16), with 500 GB memory and Ubuntu 12.04 LTS (16-bit) OS.
I always get the following error message (see comment below).
Can you help me resolve this issue?
Thank you!!!
Change History (4)
comment:2 in reply to: ↑ description Changed 6 years ago by westram
Replying to guest:
Can anyone help me with this issue? I cannot open ANY database anymore… After the program crashed when I filtered sequences by the 'keep sequences that are marked' function, ARB will not open any of my databases (including unchanged public SILVA databases) anymore.
Does that mean arb did run w/o problems before?
I am using ARB version 6.0.2 on an 16-core machine (Intel Xeon® CPU ES-2697 v3 @ 2.60 GHz x 16), with 500 GB memory and Ubuntu 12.04 LTS (16-bit) OS.
Could you please attach the session log requested (at the end of the console output). For more privacy you may also send it via mail to devel@…
Ralf
comment:3 Changed 6 years ago by westram
- Owner changed from devel to westram
- Priority changed from blocker to normal
- Status changed from new to accepted
- Type changed from defect to issue
Assumed to be caused by broken properties.
comment:4 Changed 6 years ago by westram
- Resolution set to handled
- Status changed from accepted to closed
The problem described above was caused by a truncated arb property file.
Added followup-ticket #800 to provide better error-handling for the future.
Howto test + fix:
The properties are stored in the directory ~/.arb_prop/ To disable them for your account, you could rename them, e.g. from a console/terminal window using the commands cd ~ mv .arb_prop .arb_prop.20181106.broken If arb works w/o problems after the 2nd command, the reason was inside that directory. Another (less likely) cause might be the directory .arb_tmp (use same method). If renaming does not fix the problem, you may revert the namechange using cd ~ mv .arb_prop.20181106.broken .arb_prop If renaming does save the problem and you have a backup of the property files - say from yesterday or last week - you may want to restore that backup. Main properties (for arb main program) are stored in ~/.arb_prop/ntree.arb those of the arb sequence editor in ~/.arb_prop/edit4.arb ... The main suspect for the crash is ~/.arb_prop/ntree.arb, so simply renaming that file might as well work as a fix. The advantage would be, that the saved user properties for the rest of arb remain intact.