*The server is a centos 7 VM with 2 cores / 8GB ram*
*# cat /etc/centos-release*
CentOS Linux release 7.3.1611 (Core)
*#arangod --version*
3.1.9
architecture: 64bit
asan: false
asm-crc32: true
assertions: false
build-date: 2017-01-24 14:43:49
build-repository: tags/v3.1.9-0-g008fa5a
compiler: gcc [5.4.0]
cplusplus: 201103
endianness: little
fd-client-event-handler: poll
fd-setsize: 1024
icu-version: 54.1
jemalloc: true
maintainer-mode: false
openssl-version: OpenSSL 1.0.1e-fips 11 Feb 2013
rocksdb-version: 4.8.0
server-version: 3.1.9
sizeof int: 4
sizeof void*: 8
sse42: false
tcmalloc: false
v8-version: 5.0.71.39
vpack-version: 0.1.30
zlib-version: 1.2.8
*#cat /etc/arangodb3/arangod.conf*
[database]
directory = /var/lib/arangodb3
# maximal-journal-size = 33554432
[server]
# Specify the endpoint for HTTP requests by clients.
# tcp://ipv4-address:port
# tcp://[ipv6-address]:port
# ssl://ipv4-address:port
# ssl://[ipv6-address]:port
# unix:///path/to/socket
#
# Examples:
# endpoint = tcp://0.0.0.0:8529
# endpoint = tcp://127.0.0.1:8529
# endpoint = tcp://localhost:8529
# endpoint = tcp://myserver.arangodb.com:8529
# endpoint = tcp://[::]:8529
# endpoint = tcp://[fe80::21a:5df1:aede:98cf]:8529
#
#endpoint = tcp://127.0.0.1:8529
endpoint = tcp://0.0.0.0:8529
# resuse a port on restart or wait until it is freed by the operating system
# reuse-address = false
authentication = false
# number of server threads. use 0 to make arangod determine the
# number of threads automatically, based on available CPUs
#threads = 1
# gather server statistics
statistics = true
# the user and group are normally set in the start script
# uid = arangodb
# gid = arangodb
[scheduler]
# number of threads used for I/O, use 0 to make arangod determine
# the number of threads automatically
#threads = 1
[javascript]
startup-directory = usr/share/arangodb3/js
app-path = /var/lib/arangodb3-apps
# app-path = @HOMEDRIVE@/@HOMEPATH@/arangodb3/apps
# number of V8 contexts available for JavaScript execution. use 0 to
# make arangod determine the number of contexts automatically.
#v8-contexts = 1
[foxx]
# enable Foxx queues in the server
queues = false
# interval (seconds) to use for polling jobs in Foxx queues
# queues-poll-interval = 1
[log]
level = info
file = /var/log/arangodb3/arangod.log
[cluster]
*# service arangodb3 restart*
Restarting arangodb3 (via systemctl): Job for arangodb3.service failed
because the control process exited with error code. See "systemctl status
arangodb3.service" and "journalctl -xe" for details.
[FAILED]
*# service arangodb3 status*
● arangodb3.service - ArangoDB database server
Loaded: loaded (/usr/lib/systemd/system/arangodb3.service; enabled;
vendor preset: disabled)
Active: failed (Result: start-limit) since Fri 2017-01-27 21:08:59 EET;
8s ago
Process: 4254 ExecStartPre=/usr/sbin/arangod --uid arangodb --gid
arangodb --pid-file /var/run/arangodb3/arangod.pid --server.rest-server
false --database.auto-upgrade true (code=exited, status=1/FAILURE)
Process: 4251 ExecStartPre=/usr/bin/chmod 700 /var/lib/arangodb3-apps
(code=exited, status=0/SUCCESS)
Process: 4248 ExecStartPre=/usr/bin/chown -R arangodb:arangodb
/var/lib/arangodb3-apps (code=exited, status=0/SUCCESS)
Process: 4246 ExecStartPre=/usr/bin/chmod 700 /var/lib/arangodb3
(code=exited, status=0/SUCCESS)
Process: 4243 ExecStartPre=/usr/bin/chown -R arangodb:arangodb
/var/lib/arangodb3 (code=exited, status=0/SUCCESS)
Process: 4240 ExecStartPre=/usr/bin/chmod 700 /var/log/arangodb3
(code=exited, status=0/SUCCESS)
Process: 4238 ExecStartPre=/usr/bin/chown -R arangodb:arangodb
/var/log/arangodb3 (code=exited, status=0/SUCCESS)
Process: 4235 ExecStartPre=/usr/bin/install -g arangodb -o arangodb -d
/var/run/arangodb3 (code=exited, status=0/SUCCESS)
Process: 4233 ExecStartPre=/usr/bin/install -g arangodb -o arangodb -d
/var/tmp/arangodb3 (code=exited, status=0/SUCCESS)
*#journalctl -xe*
-- The leading process of the session is 4432.
Jan 27 21:10:35 db2.nelios systemd[1]: Starting Session 4 of user giorgos.
-- Subject: Unit session-4.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-4.scope has begun starting up.
Jan 27 21:10:35 db2.nelios sshd[4432]: pam_unix(sshd:session): session
opened for user giorgos by (uid=0)
Jan 27 21:11:41 db2.nelios kernel: hrtimer: interrupt took 37104234 ns
Jan 27 21:11:42 db2.nelios systemd[1]: arangodb3.service start-pre
operation timed out. Terminating.
Jan 27 21:11:44 db2.nelios systemd[1]: Failed to start ArangoDB database
server.
-- Subject: Unit arangodb3.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit arangodb3.service has failed.
--
-- The result is failed.
Jan 27 21:11:44 db2.nelios systemd[1]: Unit arangodb3.service entered
failed state.
Jan 27 21:11:44 db2.nelios systemd[1]: arangodb3.service failed.
Jan 27 21:11:44 db2.nelios polkitd[607]: Unregistered Authentication Agent
for unix-process:4311:101771 (system bus name :1.30, object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (d
Jan 27 21:11:44 db2.nelios systemd[1]: arangodb3.service holdoff time over,
scheduling restart.
Jan 27 21:11:44 db2.nelios systemd[1]: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:11:44 db2.nelios systemd[1]: Starting ArangoDB database server...
-- Subject: Unit arangodb3.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit arangodb3.service has begun starting up.
Jan 27 21:13:14 db2.nelios systemd[1]: arangodb3.service start-pre
operation timed out. Terminating.
Jan 27 21:13:16 db2.nelios systemd[1]: Failed to start ArangoDB database
server.
-- Subject: Unit arangodb3.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit arangodb3.service has failed.
--
-- The result is failed.
Jan 27 21:13:16 db2.nelios systemd[1]: Unit arangodb3.service entered
failed state.
Jan 27 21:13:16 db2.nelios systemd[1]: arangodb3.service failed.
Jan 27 21:13:16 db2.nelios systemd[1]: arangodb3.service holdoff time over,
scheduling restart.
Jan 27 21:13:16 db2.nelios systemd[1]: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:13:16 db2.nelios systemd[1]: Starting ArangoDB database server...
-- Subject: Unit arangodb3.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit arangodb3.service has begun starting up.
*#tail /var/log/messages --lines=100*
Jan 27 21:10:12 db2 systemd: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:10:12 db2 systemd: Starting ArangoDB database server...
Jan 27 21:10:35 db2 systemd: Started Session 4 of user giorgos.
Jan 27 21:10:35 db2 systemd-logind: New session 4 of user giorgos.
Jan 27 21:10:35 db2 systemd: Starting Session 4 of user giorgos.
Jan 27 21:11:41 db2 kernel: hrtimer: interrupt took 37104234 ns
Jan 27 21:11:42 db2 systemd: arangodb3.service start-pre operation timed
out. Terminating.
Jan 27 21:11:44 db2 systemd: Failed to start ArangoDB database server.
Jan 27 21:11:44 db2 systemd: Unit arangodb3.service entered failed state.
Jan 27 21:11:44 db2 systemd: arangodb3.service failed.
Jan 27 21:11:44 db2 systemd: arangodb3.service holdoff time over,
scheduling restart.
Jan 27 21:11:44 db2 systemd: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:11:44 db2 systemd: Starting ArangoDB database server...
Jan 27 21:13:14 db2 systemd: arangodb3.service start-pre operation timed
out. Terminating.
Jan 27 21:13:16 db2 systemd: Failed to start ArangoDB database server.
Jan 27 21:13:16 db2 systemd: Unit arangodb3.service entered failed state.
Jan 27 21:13:16 db2 systemd: arangodb3.service failed.
Jan 27 21:13:16 db2 systemd: arangodb3.service holdoff time over,
scheduling restart.
Jan 27 21:13:16 db2 systemd: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:13:16 db2 systemd: Starting ArangoDB database server...
Jan 27 21:14:46 db2 systemd: arangodb3.service start-pre operation timed
out. Terminating.
Jan 27 21:14:48 db2 systemd: Failed to start ArangoDB database server.
Jan 27 21:14:48 db2 systemd: Unit arangodb3.service entered failed state.
Jan 27 21:14:48 db2 systemd: arangodb3.service failed.
Jan 27 21:14:48 db2 systemd: arangodb3.service holdoff time over,
scheduling restart.
Jan 27 21:14:48 db2 systemd: Cannot add dependency job for unit
microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Jan 27 21:14:48 db2 systemd: Starting ArangoDB database server...
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
