Open neunhoef opened 6 years ago
@neunhoef I met the same problem. I run the following command
nohup arangodb --starter.mode=single &
And then I log out. I found the ArangoDB server was down and arangod.log
was:
2019-11-11T02:51:58Z [6449] INFO [b4133] control-c received, beginning shut down sequence
2019-11-11T02:51:58Z [6449] FATAL [11ca3] {cluster} control-c received (again!), terminating
How could I make arangodb server run even though I log out? Thanks in advance for any help.
Observing the same arangod log output when starting via systemd and then running:
sudo systemctl stop arangodb3.service
The following is the output of arangod --version
:
3.7.0-1
architecture: 64bit
arm: false
asan: false
asm-crc32: true
assertions: false
avx2: true
boost-version: 1.71.0
build-date: 2020-06-21 00:47:47
build-repository: tags/v3.7.0.1-0-gbafb72d2ca-dirty
compiler: gcc [9.3.0]
cplusplus: 201703
curl-version: none
debug: false
endianness: little
failure-tests: false
fd-client-event-handler: poll
fd-setsize: 1024
full-version-string: ArangoDB 3.7.0-1 [linux] 64bit, using jemalloc, build tags/v3.7.0.1-0-gbafb72d2ca-dirty, VPack 0.1.33, RocksDB 6.2.0, ICU 64.2, V8 7.9.317, OpenSSL 1.1.1f 31 Mar 2020
icu-version: 64.2
ipo: true
iresearch-version: 1.0.0.0
jemalloc: true
license: community
maintainer-mode: false
ndebug: true
openssl-version-compile-time: OpenSSL 1.1.1f 31 Mar 2020
openssl-version-run-time: OpenSSL 1.1.1f 31 Mar 2020
optimization-flags: -march=znver1 -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -msse4a -mavx -mfma -mbmi2 -mavx2 -mno-xop -mno-fma4 -mno-avx512f -mno-avx512vl -mno-avx512pf -mno-avx512er -mno-avx512cd -mno-avx512dq -mno-avx512bw -mno-avx512ifma -mno-avx512vbmi
pic: 2
pie: 2
platform: linux
reactor-type: epoll
rocksdb-version: 6.2.0
server-version: 3.7.0-1
sizeof int: 4
sizeof long: 8
sizeof void*: 8
sse42: true
tsan: false
unaligned-access: true
v8-version: 7.9.317
vpack-version: 0.1.33
zlib-version: 1.2.11
It seems that in some configurations the
arangod
subprocesses of the starter are not correctly shut down on Ctrl-C to the starter. One example:And then hitting Ctrl-C when everything is up and running provokes this in the dbserver's log: