Title
#users-public
Ahmad Abbasi

Ahmad Abbasi

11/06/2022, 1:39 AM
Has anyone experience an error like this:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # A fatal error has been detected by the Java Runtime Environment:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #  SIGSEGV (0xb) at pc=0x00007f7e4c86e460, pid=114765, tid=114954
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # JRE version: OpenJDK Runtime Environment Corretto-11.0.17.8.1 (11.0.17+8) (build 11.0.17+8-LTS)
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # Java VM: OpenJDK 64-Bit Server VM Corretto-11.0.17.8.1 (11.0.17+8-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # Problematic frame:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # J 3786 c2 io.questdb.cairo.vm.api.MemoryCR.getLong(J)J io.questdb@6.5.4 (44 bytes) @ 0x00007f7e4c86e460 [0x00007f7e4c86e420+0x0000000000000040]
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # An error report file with more information is saved as:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # //hs_err_pid114765.log
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: # If you would like to submit a bug report, please visit:
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #   <https://github.com/corretto/corretto-11/issues/>
Nov 06 01:39:20 ip-172-31-42-190.us-east-2.compute.internal questdb[114765]: #
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: questdb.service: main process exited, code=killed, status=6/ABRT
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: Unit questdb.service entered failed state.
Nov 06 01:39:21 ip-172-31-42-190.us-east-2.compute.internal systemd[1]: questdb.service failed.
Nicolas Hourcard

Nicolas Hourcard

11/06/2022, 10:13 AM
hey Ahmad, we’ll look into it 👍
Andrey Pechkurov

Andrey Pechkurov

11/08/2022, 8:11 AM
Hi Ahmad, Which QuestDB version are you using? If it's not the latest one, 6.5.5, there is a chance that the issue is already fixed, so you should try upgrading. If the issue remains, could you open a GH issue and attach the
hs_err_pidXYZ.log
file?
8:11 AM
Sorry, I haven't noticed the follow-up messages