10000 SegFault when using an AQL for loop through edges · Issue #12507 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

SegFault when using an AQL for loop through edges #12507

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.

Sign up for GitHub

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

Jump to bottom
Closed
n-toussaint opened this issue Aug 24, 2020 · 8 comments
Closed

SegFault when using an AQL for loop through edges #12507

n-toussaint opened this issue Aug 24, 2020 · 8 comments
Assignees
@jsteemann
Labels
1 Bug 2 Fixed Resolution 3 AQL Query language related
Milestone
3.7.3

Comments

@n-toussaint
Copy link
n-toussaint commented Aug 24, 2020 •
edited
Loading

My Environment

  • ArangoDB Version: 3.7.1
  • Storage Engine: RocksDB
  • Deployment Mode: Single Server
  • Deployment Strategy: ArangoDB Starter in Docker
  • Infrastructure: AWS
  • Operating System: Linux version 4.15.0-1065-aws (buildd@lgw01-amd64-035) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04))
  • Total RAM in your machine: 4GB
  • Used Package: Debian or Ubuntu .deb

Hello, I run into troubles after having updated the arangodb version to 3.7.1.
Each time that I am using the AQL command below, the container stops with a segfault. It is the same with all the edge types and databases.

FOR vertex, edge IN 1 OUTBOUND @_id @edge_name
    return vertex

Here are the logs:

arangodb.1| 2020-08-24T13:34:09Z [1] FATAL [a7902] {crash} ArangoDB 3.7.1 [linux], thread 6 [SchedWorker] caught unexpected signal 11 (SIGSEGV) accessing address 0x0000000000000040: signal handler invoked
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 1 [0x00007f05c02da56d] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 2 [0x00007f05c325a515] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 3 [0x00007f05c0dbe933] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 4 [0x00007f05c0c7b946] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 5 [0x00007f05c0dcf0ea] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 6 [0x00007f05c0dd0c6a] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 7 [0x00007f05c0dd2d02] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 8 [0x00007f05c0fdd4da] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 9 [0x00007f05c0170d1e] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 10 [0x00007f05c0fd6584] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 11 [0x00007f05c12c8bcc] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 12 [0x00007f05c12c9e69] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 13 [0x00007f05c133dfe6] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 14 [0x00007f05c13633ca] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 15 [0x00007f05c1076155] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 16 [0x00007f05c122b579] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 17 [0x00007f05c02d6fdb] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 18 [0x00007f05c025bfbf] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [308c3] {crash} frame 19 [0x00007f05c3261068] *no symbol name available for this frame
arangodb.1| 2020-08-24T13:34:09Z [1] INFO [ded81] {crash} available physical memory: 8362708992, rss usage: 269983744, vsz usage: 1051136000, threads: 28
arangodb.1| automatically choosing storage engine
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [e52b0] ArangoDB 3.7.1 [linux] 64bit, using jemalloc, build tags/v3.7.1-0-gdd98295dcc, VPack 0.1.33, RocksDB 6.8.0, ICU 64.2, V8 7.9.317, OpenSSL 1.1.1g  21 Apr 2020
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [75ddc] detected operating system: Linux version 4.15.0-1065-aws (buildd@lgw01-amd64-035) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #69-Ubuntu SMP Thu Mar 26 02:17:29 UTC 2020
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [25362] {memory} Available physical memory: 8362708992 bytes, available cores: 2
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [43396] {authentication} Jwt secret not specified, generating...
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [144fe] using storage engine 'rocksdb'
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [3bb7d] {cluster} Starting up with role SINGLE
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [6ea38] using endpoint 'http+tcp://0.0.0.0:8529' for non-encrypted requests
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [a1c60] {syscall} file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [3844e] {authentication} Authentication is turned on (system only), authentication for unix sockets is turned on
arangodb.1| 2020-08-24T13:34:21Z [1] WARNING [ad4b2] found existing lockfile '/var/lib/arangodb3/LOCK' of previous process with pid 1, and that process seems to be still running
arangodb.1| 2020-08-24T13:34:21Z [1] INFO [e6460] created base application directory '/var/lib/arangodb3-apps/_db'
arangodb.1| 2020-08-24T13:34:22Z [1] INFO [cf3f4] ArangoDB (version 3.7.1 [linux]) is ready for business. Have fun!

Thank you very much for your time and experience!
Nicolas
@jsteemann jsteemann self-assigned this Aug 24, 2020
@jsteemann jsteemann added 1 Analyzing 1 Bug 3 AQL Query language related labels Aug 24, 2020
@jsteemann
Copy link
Contributor 8000

Thanks for the bug report. Will check...

@jsteemann
Copy link
Contributor

Can you try adjusting the query string so it becomes

FOR vertex, edge IN 1 OUTBOUND @_id @@edge_name
    return vertex

and use a collection name bind parameter named @edge_name?
AFAICS this should work.
Will now try to figure out why the simple bind parameter does not work as expected.

@n-toussaint
Copy link
Author
n-toussaint commented Aug 24, 2020 •
edited
Loading

You are right, it does work with a collection name bind parameter.
What are the differences between the two?

@jsteemann
Copy link
Contributor

It's the internal code path that is different for the two.
It worked in 3.6, so it looks like a regression and I will try to fix it.

jsteemann added a commit that referenced this issue Aug 24, 2020
@jsteemann
fixed issue #12507: SegFault when using an AQL for loop through edges
d6d3ea4
jsteemann added a commit that referenced this issue Aug 24, 2020
@jsteemann
fixed issue #12507: SegFault when using an AQL for loop through edges
0ea8502
This was referenced Aug 24, 2020
Merged
Merged
@jsteemann jsteemann added 2 Fixed Resolution and removed 1 Analyzing labels Aug 24, 2020
@jsteemann
Copy link
Contributor

Fixed via the above PRs.
The bugfix should be released with either 3.7.2 or 3.7.3. I can't say for sure yet.

@Simran-B Simran-B added this to the 3.7.3 milestone Aug 26, 2020
@Simran-B
Copy link
Contributor

Setting milestone to 3.7.3 just so this ticket won't be forgotten.

KVS85 added a commit that referenced this issue Sep 1, 2020
@jsteemann @KVS85
Bug fix 3.7/issue 12507 (#12511)
3db1e45 
* fixed issue #12507: SegFault when using an AQL for loop through edges

* added derived files

* added more tests

* Update CHANGELOG

Co-authored-by: Vadim <vadim@arangodb.com>
@insider777
Copy link

Thank god somone discovered this i was like wtf does it keep crashing 😄

@mpoeter mpoeter mentioned this issue Sep 27, 2020
Closed
@maxkernbach
Copy link
Contributor

Hi @KevinAuSon and @insider777,

Version 3.7.3, which includes a fix for this issue, has just been released.

From the Changelog:

Please comment in case the SegFault still occurs after upgrading.

Thanks

@maxkernbach maxkernbach mentioned this issue Oct 27, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsteemann jsteemann

Labels
1 Bug 2 Fixed Resolution 3 AQL Query language related
Projects
None yet
Milestone
3.7.3
Development

No branches or pull requests
5 participants
@jsteemann @Simran-B @maxkernbach @n-toussaint @insider777
0