Hai Mathieu,
Thanks for using MonetDB, and sorry for the crash.
If possible, can you please give us the necessary data to reproduce the crash? They include:
- the schema
- a small set of (anonymised) data
- the queries
You can also compile MonetDB from source with the --enable-debug option, so that GDB can give you the exact line where the crash has happend, and the value of the variable/statement/function/etc that has caused the crash.
Regards,
Jennie
> _______________________________________________
> On Oct 15, 2015, at 17:50, Mathieu Raillard <mraillard@data-mat.fr> wrote:
>
> Hi all,
>
> We are using MoentDB since 6 months with quite good results.(thanks to the dev team for their good work)
>
> Unfortunately yesterday we came across an issue for which we can't find a solution.
> Our database crashed for an unknown reason (RAM was fine, Disk space was fine) and now each time we re-use the same table with a query we used during the crash, the database crash with a seg fault
>
> Query : select * from storage();
> OS Version : CentOS release 6.7 (Final)
> MonetDB Version : MonetDB Database Server Toolkit v1.1 (Jul2015)
>
> tail /var/log/messages :
> kernel: mserver5[9945]: segfault at 18 ip 00007f9e86fd534b sp 00007f9e862912e0 error 4 in lib_sql.so[7f9e86eb1000+182000]
>
> merovingian.log :
> database 'BI-DEV' (9972) was killed by signal SIGSEGV
>
> Log from gbd :
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffa24edc700 (LWP 4683)]
> 0x00007ffa25c1f34b in delta_bind_bat () from /usr/lib64/monetdb5/lib_sql.so
> (gdb) bt
> #0 0x00007ffa25c1f34b in delta_bind_bat () from /usr/lib64/monetdb5/lib_sql.so
> #1 0x00007ffa25b20fee in sql_storage () from /usr/lib64/monetdb5/lib_sql.so
> #2 0x00007ffa321aea45 in runMALsequence () from /usr/lib64/libmonetdb5.so.19
> #3 0x00007ffa321afe29 in callMAL () from /usr/lib64/libmonetdb5.so.19
> #4 0x00007ffa25b369f7 in SQLexecutePrepared () from /usr/lib64/monetdb5/lib_sql.so
> #5 0x00007ffa25b36efc in SQLengineIntern () from /usr/lib64/monetdb5/lib_sql.so
> #6 0x00007ffa321c87dd in runScenarioBody () from /usr/lib64/libmonetdb5.so.19
> #7 0x00007ffa321c886f in runScenario () from /usr/lib64/libmonetdb5.so.19
> #8 0x00007ffa321c9738 in MSserveClient () from /usr/lib64/libmonetdb5.so.19
> #9 0x00007ffa321ca816 in MSscheduleClient () from /usr/lib64/libmonetdb5.so.19
> #10 0x00007ffa32266e0f in doChallenge () from /usr/lib64/libmonetdb5.so.19
> #11 0x00007ffa31d2adcf in thread_starter () from /usr/lib64/libbat.so.12
> #12 0x00007ffa2f97da51 in start_thread (arg=0x7ffa24edc700) at pthread_create.c:301
> #13 0x00007ffa2f6ca93d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
>
>
> Any help to understand and correct what is going on would be nice.
>
> Regards
>
> Mathieu
> users-list mailing list
> users-list@monetdb.org
> https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list