-
Notifications
You must be signed in to change notification settings - Fork 852
arangod silently exits #1426
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
Comments
Can you try starting it manually from the command-line with option |
Here you go! For some reason ulimit is not installed. Not sure what to make of that yet. sar@jessie-rpi:~$ sudo /usr/sbin/arangod -c /etc/arangodb/arangod.conf --pid-file /var/run/arangodb/arangod.pid --javascript.v8-contexts 1
2015-08-05T20:18:43Z [12162] INFO ArangoDB 2.6.3 32bit -- ICU 54.1, V8 3.31.74.1, OpenSSL 1.0.1k 8 Jan 2015
2015-08-05T20:18:43Z [12162] INFO using default language 'en'
2015-08-05T20:18:44Z [12162] INFO loaded database '_system' from '/var/lib/arangodb/databases/database-126282'
2015-08-05T20:18:44Z [12162] INFO running WAL recovery (1 logfiles)
2015-08-05T20:18:44Z [12162] INFO replaying WAL logfile '/var/lib/arangodb/journals/logfile-257354.db' (1 of 1)
2015-08-05T20:18:44Z [12162] INFO WAL recovery finished successfully
2015-08-05T20:18:44Z [12162] INFO using endpoint 'tcp://127.0.0.1:8529' for non-encrypted requests
2015-08-05T20:18:44Z [12162] INFO using default API compatibility: 20600
2015-08-05T20:18:44Z [12162] INFO JavaScript using startup '/usr/share/arangodb/js', application '/var/lib/arangodb-apps'
2015-08-05T20:18:47Z [12162] INFO In database '_system': Database is up-to-date (20603/prod/standalone/existing)
sar@jessie-rpi:~$ echo $?
135
sar@jessie-rpi:~$ sudo ulimit -c unlimited
sudo: ulimit: command not found
sar@jessie-rpi:~$ sudo apt-get install ulimit
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ulimit
sar@jessie-rpi:~$ |
An exit code of 135 is probably This is probably V8 triggering this. The position at which it fails also supports that hypothesis. Regarding ulimit and core dumps: I think ulimit is a bash built-in, so it may work by omitting the |
Oops! you are correct. Ulimit says its already set at unlimited. |
|
@jsteemann The core dump is pretty big so I sent you a link. Check your email. |
hm, the package installs just fine on our cubie truck. The coredump doesn't produce usefull information about the offending thread except for that its killed by SIG_BUS. Which OS image did you use? |
ok, after ugrading the box, I can reproduce this: (it was somewhat behind since it was installed when jessie was still testing) Seems openssl is broken... |
@sleepycat : as @dothebart mentioned, we were able to reproduce it locally with the 2.6.3 package after upgrading the OS. Interestingly enough, the issue didn't occur before the OS upgrade but with the same ArangoDB package. |
New 2.6x packages are available - closing. |
the Cubie truck accidently became a debian testing. We now have a debian jessie bananapi - awaiting the V8 compile to finish. |
'silently exited' seemed not to be true. after researching we found The new 2.6.5 packages are uploaded. their md5-sum is: ca1860c20cec2ee7f4ed9c5e952e28a3 |
We isolated the issue with the unaligned memory access. @jsteemann will work on fixing this later this week. |
if properly controlled (its bit flags - my bad) we revalidated this with this simple test program doing unaligned acces as we do it in ArangoDB:
(The first line in the loop does unaligned access, the second re-alignes pointer access, the third one unaligned array access) One can simply compile the sample above using
From now on arangod will autodetect the alignment kernel settings on start on ARM and decline to start if its wrong for us. |
I installed Debian Jessie on my Raspberry Pi as suggested in the Google group.
The install seems to go well but I cannot connect to arangodb after:
I can see that the arangodb supervisor is running but no instances of arangod are around:
The cause of this appears to be that /usr/sbin/arangod silently exits after about 20 seconds.
Nothing is printed in the logs:
The text was updated successfully, but these errors were encountered: