Hello Sjoerd, It turns out the crash in partly my fault as I ended up with the a repeated foreign constraint during a merge which monetdb accepts in the schema but then crashes during an insert into the table. I fixed the problem in our schema and everything is working fine again. I have made a small repro below. The last insert causes SIGSEGV. UUIDs also work fine through mapi which is our primary interface to the database. The question is since the problem is caused only through incorrect syntax do you want it filed as a bug? Doug CREATE TABLE exchange ( pk_symbol VARCHAR(16) NOT NULL, name VARCHAR(128) NOT NULL, CONSTRAINT exchange_pk PRIMARY KEY (pk_symbol) ); CREATE TABLE entity ( pk_uuid UUID NOT NULL, name VARCHAR(128) NOT NULL, industry VARCHAR(64), category VARCHAR(64), subcategory VARCHAR(64), CONSTRAINT entity_pk PRIMARY KEY (pk_uuid) ); CREATE TABLE instrument ( pk_uuid UUID NOT NULL, symbol VARCHAR(32) NOT NULL, fk_exchange VARCHAR(16) NOT NULL, fk_entity_uuid UUID NOT NULL, CONSTRAINT instrument_pk PRIMARY KEY (pk_uuid), -- INCORRECT DOUBLE CONSTRAINT CONSTRAINT instrument_exchange_fk FOREIGN KEY (fk_exchange) REFERENCES exchange (pk_symbol), CONSTRAINT instrument_exchange_fk FOREIGN KEY (fk_exchange) REFERENCES exchange (pk_symbol), CONSTRAINT instrument_entity_fk FOREIGN KEY (fk_entity_uuid) REFERENCES entity (pk_uuid) ); INSERT INTO exchange (pk_symbol, name) VALUES ('EXCH', 'The exchange'); INSERT INTO entity (pk_uuid, name, industry, category, subcategory) VALUES ('52aaa24f-c9cb-4421-9501-33be20d80dcc', 'NAME', 'XXX', 'YYY', 'ZZZ'); --Crash the server with SIGSEGV INSERT INTO instrument (pk_uuid, symbol, fk_exchange, fk_entity_uuid) VALUES ('24a2a880-451c-4401-94af-93715ad0baf6', 'ABC', 'EXCH', '52aaa24f-c9cb-4421-9501-33be20d80dcc'); On Wed, Oct 7, 2015 at 8:35 AM, Sjoerd Mullender wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 07/10/15 01:28, Doug Service wrote:

...

Hello Stefan,

I modified the uuid.mal file in the lib directory and that all works great for a small sample test from mclient. Thanks!

Now I have run into a problem where the server crashes when I try to insert into one of the tables, though inserts in other tables work fine. I do not think this problem has anything with UUIDS as the table I am inserting into does not use UUIDS and I can do inserts into tables that have uuid columns. This insert that causes the crash worked fine on the last version of our schema that did not use UUIDs.

I have a small database from msqldump and an insert statement that causes the server to crash consistently. However, I do not see any way to add attachments to a bug report on the tracker. Is there a way to do this?

After you have created a bug report, you can edit it again. Then there is a link "Add an attachment" where you can add attachments.

...

Is there any other information I can collect that would be useful in a bug report?

Here is the monetdb log which shows a sigsegv.

Doug

2015-10-06 16:02:19 MSG quantbox[3433]: # MonetDB 5 server v11.21.5 "Jul2015" 2015-10-06 16:02:19 MSG quantbox[3433]: # Serving database 'quantbox', using 4 threads 2015-10-06 16:02:19 MSG quantbox[3433]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked 2015-10-06 16:02:19 MSG quantbox[3433]: # Found 1.907 GiB available main-memory. 2015-10-06 16:02:19 MSG quantbox[3433]: # Copyright (c) 1993-July 2008 CWI. 2015-10-06 16:02:19 MSG quantbox[3433]: # Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved 2015-10-06 16:02:19 MSG quantbox[3433]: # Visit http://www.monetdb.org/ for further information 2015-10-06 16:02:19 MSG quantbox[3433]: # Listening for UNIX domain connection requests on mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock 2015-10-06 16:02:19 MSG quantbox[3433]: # Start processing logs sql/sql_logs version 52200 2015-10-06 16:02:19 MSG quantbox[3433]: # Start reading the write-ahead log 'sql_logs/sql/log.4' 2015-10-06 16:02:19 MSG quantbox[3433]: # Finished reading the write-ahead log 'sql_logs/sql/log.4' 2015-10-06 16:02:19 MSG quantbox[3433]: # Finished processing logs sql/sql_logs 2015-10-06 16:02:19 MSG quantbox[3433]: # MonetDB/SQL module loaded 2015-10-06 16:02:19 MSG merovingian[809]: proxying client 10.1.10.101:40633 http://10.1.10.101:40633 for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:02:19 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:19 MSG merovingian[809]: proxying client (local) for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:05:19 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:27 MSG merovingian[809]: proxying client (local) for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:05:27 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:48 MSG merovingian[809]: database 'quantbox' (3433) was killed by signal SIGSEGV 2015-10-06 16:05:59 MSG merovingian[809]: starting database 'quantbox', up min/avg/max: 0s/0s/0s, crash average: 1.00 0.30 0.10 (3-0=3) 2015-10-06 16:06:00 MSG quantbox[3532]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/quantbox --set merovingian_uri=mapi:monetdb://qbdb:42000/quantbox --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/quantbox/.mapi.sock --set monet_vault_key=/var/lib/monetdb/quantbox/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

- -- Sjoerd Mullender -----BEGIN PGP SIGNATURE----- Version: GnuPG v2

iQEcBAEBCAAGBQJWFNlvAAoJEISMxT6LrWYgST8H/1NK3P3tsm7IgEFTsRjZ7Dgc FL6xMUHJwvzQrzQJKCJmqvOXomVqgkrVBYPyDxd/HjP74Mr33QKGvafTtQFBU8K8 j5CebKyRiItLmAbfxP6PXN6wQO99VtaNlyJa96fU6cO36kiO1J/fbW67QhJDSKdR r34vD2vnO8jxBizIrcTTKQn/25sStLf+TEfgGI5knuU04+J8IjDro7UfELnHjQBO pZZxlgCnjz68j9q6iBcNdGbARJmxixU9oraOgpUAu44q+p3m9XEQiqn4OHSdRcJQ 3pZhxD047+XcN46wkXM1ce2vlqTWLoXu7MxEniuKc3mSF/H9uNXEc9ZDl/CRhkY= =5BES -----END PGP SIGNATURE----- _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

done On Thu, Oct 8, 2015 at 7:16 PM, Sjoerd Mullender wrote:

Can you turn this into a bug report on bugs.monetdb.org, please?

On 10/08/2015 05:36 PM, Doug Service wrote:

...

Hello Sjoerd,

It turns out the crash in partly my fault as I ended up with the a repeated foreign constraint during a merge which monetdb accepts in the schema but then crashes during an insert into the table. I fixed the problem in our schema and everything is working fine again. I have made a small repro below. The last insert causes SIGSEGV. UUIDs also work fine through mapi which is our primary interface to the database.

The question is since the problem is caused only through incorrect syntax do you want it filed as a bug?

Doug

CREATE TABLE exchange ( pk_symbol VARCHAR(16) NOT NULL, name VARCHAR(128) NOT NULL, CONSTRAINT exchange_pk PRIMARY KEY (pk_symbol) );

CREATE TABLE entity ( pk_uuid UUID NOT NULL, name VARCHAR(128) NOT NULL, industry VARCHAR(64), category VARCHAR(64), subcategory VARCHAR(64), CONSTRAINT entity_pk PRIMARY KEY (pk_uuid) );

CREATE TABLE instrument ( pk_uuid UUID NOT NULL, symbol VARCHAR(32) NOT NULL, fk_exchange VARCHAR(16) NOT NULL, fk_entity_uuid UUID NOT NULL, CONSTRAINT instrument_pk PRIMARY KEY (pk_uuid), -- INCORRECT DOUBLE CONSTRAINT CONSTRAINT instrument_exchange_fk FOREIGN KEY (fk_exchange) REFERENCES exchange (pk_symbol), CONSTRAINT instrument_exchange_fk FOREIGN KEY (fk_exchange) REFERENCES exchange (pk_symbol), CONSTRAINT instrument_entity_fk FOREIGN KEY (fk_entity_uuid) REFERENCES entity (pk_uuid) );

INSERT INTO exchange (pk_symbol, name) VALUES ('EXCH', 'The exchange'); INSERT INTO entity (pk_uuid, name, industry, category, subcategory) VALUES ('52aaa24f-c9cb-4421-9501-33be20d80dcc', 'NAME', 'XXX', 'YYY', 'ZZZ');

--Crash the server with SIGSEGV INSERT INTO instrument (pk_uuid, symbol, fk_exchange, fk_entity_uuid) VALUES ('24a2a880-451c-4401-94af-93715ad0baf6', 'ABC', 'EXCH', '52aaa24f-c9cb-4421-9501-33be20d80dcc');

On Wed, Oct 7, 2015 at 8:35 AM, Sjoerd Mullender mailto:sjoerd@acm.org> wrote:

On 07/10/15 01:28, Doug Service wrote:

...

Hello Stefan,

...

I modified the uuid.mal file in the lib directory and that all works great for a small sample test from mclient. Thanks!

...

Now I have run into a problem where the server crashes when I try to insert into one of the tables, though inserts in other tables work fine. I do not think this problem has anything with UUIDS as the table I am inserting into does not use UUIDS and I can do inserts into tables that have uuid columns. This insert that causes the crash worked fine on the last version of our schema that did not use UUIDs.

...

I have a small database from msqldump and an insert statement that causes the server to crash consistently. However, I do not see any way to add attachments to a bug report on the tracker. Is there a way to do this?

After you have created a bug report, you can edit it again. Then there is a link "Add an attachment" where you can add attachments.

...

Is there any other information I can collect that would be useful in a bug report?

...

Here is the monetdb log which shows a sigsegv.

...

Doug

...

2015-10-06 16:02:19 MSG quantbox[3433]: # MonetDB 5 server v11.21.5 "Jul2015" 2015-10-06 16:02:19 MSG quantbox[3433]: # Serving database 'quantbox', using 4 threads 2015-10-06 16:02:19 MSG quantbox[3433]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked 2015-10-06 16:02:19 MSG quantbox[3433]: # Found 1.907 GiB available main-memory. 2015-10-06 16:02:19 MSG quantbox[3433]: # Copyright (c) 1993-July 2008 CWI. 2015-10-06 16:02:19 MSG quantbox[3433]: # Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved 2015-10-06 16:02:19 MSG quantbox[3433]: # Visit http://www.monetdb.org/ for further information 2015-10-06 16:02:19 MSG quantbox[3433]: # Listening for UNIX domain connection requests on mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock 2015-10-06 16:02:19 MSG quantbox[3433]: # Start processing logs sql/sql_logs version 52200 2015-10-06 16:02:19 MSG quantbox[3433]: # Start reading the write-ahead log 'sql_logs/sql/log.4' 2015-10-06 16:02:19 MSG quantbox[3433]: # Finished reading the write-ahead log 'sql_logs/sql/log.4' 2015-10-06 16:02:19 MSG quantbox[3433]: # Finished processing logs sql/sql_logs 2015-10-06 16:02:19 MSG quantbox[3433]: # MonetDB/SQL module loaded 2015-10-06 16:02:19 MSG merovingian[809]: proxying client 10.1.10.101:40633 http://10.1.10.101:40633 http://10.1.10.101:40633 for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:02:19 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:19 MSG merovingian[809]: proxying client (local) for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:05:19 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:27 MSG merovingian[809]: proxying client (local) for database 'quantbox' to mapi:monetdb:///var/lib/monetdb/quantbox/.mapi.sock?database=quantbox

2015-10-06 16:05:27 MSG merovingian[809]: target connection is on local

...

UNIX domain socket, passing on filedescriptor instead of proxying 2015-10-06 16:05:48 MSG merovingian[809]: database 'quantbox' (3433) was killed by signal SIGSEGV 2015-10-06 16:05:59 MSG merovingian[809]: starting database 'quantbox', up min/avg/max: 0s/0s/0s, crash average: 1.00 0.30 0.10 (3-0=3) 2015-10-06 16:06:00 MSG quantbox[3532]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/quantbox --set merovingian_uri=mapi:monetdb://qbdb:42000/quantbox --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/quantbox/.mapi.sock --set monet_vault_key=/var/lib/monetdb/quantbox/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes

...

_______________________________________________ users-list mailing list users-list@monetdb.org mailto:users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org mailto: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

-- Sjoerd Mullender

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list