Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database was killed by signal SIGBUS #3502

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Database was killed by signal SIGBUS #3502

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2014-06-18 16:58:45 +0200
From: andrei <<andrei.ciobotar>>
To: MonetDB5 devs <>
Version: 11.17.17 (Jan2014-SP2)
CC: @hannesmuehleisen, @mlkersten

Last updated: 2014-10-31 14:13:48 +0100

Comment 19848

Date: 2014-06-18 16:58:45 +0200
From: andrei <<andrei.ciobotar>>

sql>\d table
CREATE TABLE "sys"."table" (
"bigint1" BIGINT DEFAULT '0',
"date" DATE DEFAULT '1970-01-01',
"bigint2" BIGINT DEFAULT '0',
"bigint3" BIGINT DEFAULT '0',
"bigint4" BIGINT DEFAULT '1'

Table has 1,556,041,536 entries.

We're attempting to aggregate on a day by day basis over the bigint4 field and are running the following query (example for a single day):

'INSERT INTO table_aggregation select "bigint1", "date", "bigint2", "bigint3", sum("bigint4") from table WHERE "date" = CURRENT_DATE() - INTERVAL '6' DAY group by "bigint1", "date", "bigint2", "bigint3"'

Every 2-3 queries, the database where the table resides is killed by SIGBUS:

2014-06-18 09:17:25 MSG merovingian[15877]: database 'table_database' (9656) was killed by signal SIGBUS

After the kill signal, the first database connection attempt is refused:

2014-06-18 09:33:35 ERR merovingian[15877]: client error: cannot connect: Connection refused

We need to attempt the connection a second time for it to be successful. Any info on the possible causes of SIGBUS and how to avoid this kind of signal is appreciated.

Kind regards,

Comment 19849

Date: 2014-06-18 17:00:02 +0200
From: @hannesmuehleisen

Are you sure there is enough space on your disk?

Comment 19850

Date: 2014-06-18 17:04:30 +0200
From: andrei <<andrei.ciobotar>>

Yea, we're sitting at around 75-80% usage when the error hits (with around 20GB available). It's currently running on a test machine with 24GB RAM and is swapping heavily.

Comment 19871

Date: 2014-07-03 17:36:37 +0200
From: MonetDB Mercurial Repository <>

Changeset 45acd0d7a20a made by Sjoerd Mullender in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=45acd0d7a20a

Changeset description:

Use posix_fallocate if available to extend files.
Using this function will ensure that disk blocks are allocated, so
when the file is the memory mapped and the memory then written to, we
should never get a Bus Error because the disk is full.
This hopefully fixes bug #64, bug #3202, and bug #3507, and possibly also
bug #3502.

Comment 20250

Date: 2014-10-04 23:30:59 +0200
From: @mlkersten

Let's close this one until further information

Comment 20338

Date: 2014-10-31 14:13:48 +0100
From: @sjoerdmullender

Oct2014 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant