8000 Not able to Start ArangoDB · Issue #7745 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

Not able to Start ArangoDB #7745

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
Bkbest opened this issue Dec 12, 2018 · 6 c 8000 omments
Closed

Not able to Start ArangoDB #7745

Bkbest opened this issue Dec 12, 2018 · 6 comments
Assignees
@jsteemann
Labels
1 Question 2 Solved Resolution 3 Core 3 RocksDB Storage engine related

Comments

@Bkbest
Copy link
Bkbest commented Dec 12, 2018 •
edited by OmarAyo
Loading

My Environment

  • ArangoDB Version: 3.5.0-devel
  • Storage Engine: rocksdb
  • Deployment Mode: Single server
  • Deployment Strategy: Manual Start
  • Configuration:
  • Infrastructure: own
  • Operating System: RHEL 7.5
  • Used Package: Compiled from source

Component, Query & Data

Affected feature:
not able to start arangodb

Problem:
I have compiled arangodb from github sources and compilation was successful without any issue. However when I try to start /build/bin/arangod it fails with error:

-bash-4.2$ **./arangod --server.endpoint tcp://hostname:8529**
2018-12-12T05:10:33Z [51927] INFO ArangoDB 3.5.0-devel [linux] 64bit, using jemalloc, build heads/devel-0-g775129a, VPack 0.1.33, RocksDB 5.16.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.0.2k-fips  26 Jan 2017
2018-12-12T05:10:33Z [51927] INFO detected operating system: Linux version 3.10.0-862.14.4.el7.x86_64 (mockbuild@x86-040.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Fri Sep 21 09:07:21 UTC 2018
2018-12-12T05:10:33Z [51927] WARNING {memory} maximum number of memory mappings per process is 65530, which seems too low. it is recommended to set it to at least 256000
2018-12-12T05:10:33Z [51927] WARNING {memory} execute 'sudo sysctl -w "vm.max_map_count=256000"'
2018-12-12T05:10:33Z [51927] WARNING {memory} /sys/kernel/mm/transparent_hugepage/enabled is set to 'always'. It is recommended to set it to a value of 'never' or 'madvise'
2018-12-12T05:10:33Z [51927] WARNING {memory} /sys/kernel/mm/transparent_hugepage/defrag is set to 'always'. It is recommended to set it to a value of 'never' or 'madvise'
2018-12-12T05:10:33Z [51927] WARNING {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/enabled"'
2018-12-12T05:10:33Z [51927] WARNING {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/defrag"'
2018-12-12T05:10:33Z [51927] **FATAL cannot convert username 'arangodb' to numeric uid**

Expected result:
successfully start arangodb
@Simran-B
Copy link
Contributor

Hi @Bkbest,

the devel branch is the place where development is the most active and it can be in a broken state at any time. You can checkout a slightly older state or pull in changes some time later and check if someone repaired it.

Did you use an existing data directory or a blank/new one? Perhaps the developers can tell what this error means. I didn't encounter it before personally.

@Simran-B Simran-B added 3 Core 3 RocksDB Storage engine related labels Dec 12, 2018
@jsteemann
Copy link
Contributor

@Bkbest : can you try starting with an additional -c etc/relative/arangod.conf (please adjust file to the shipped relative config file)?
I guess you did a make install after building arangod, which should not harm but is also not necessary. Regardless of that, I think your arangod installation uses a config file found by auto-detection, and that config file may contain something like --uid arangodb, which will fail if you haven't used an installation package, as there will be no OS user arangodb present.

@Bkbest
Copy link
Author
Bkbest commented Dec 12, 2018 •
edited
Loading

@jsteemann Wow, that solved my problem, thank you very much. I have one question, as I have compiled from sources does this mean that my compiled version could be broken as suggested by @Simran-B ? because currently I see no issue with it or should I revert to older versions?

@jsteemann
Copy link
Contributor

@Bkbest: I don't think your compiled version is broken.
It is just that when starting arangod without specifying a config file explicitly, it will search in some predefined places for a config file. One of the locations is probably /etc/arangodb3/arangod.conf or /usr/local/etc/arangodb3/arangod.conf (or something like that). If you happen to have a config file in that location, it will be used.
The config file may be put there by installing an ArangoDB release package or by running make install. And the config file may run arangod with a specific OS user arangodb, so the startup fails.
Overriding the automatically found config file with the one in ./etc/relative/arangod.conf fixes the problem, as well as removed the system config file.
To check which config file is actually used, you can start with --log.level config=trace.

@Bkbest
Copy link
Author
Bkbest commented Dec 12, 2018 •
edited
Loading

I understood, thank you very much. My problem is solved. @jsteemann @Simran-B

@Simran-B
Copy link
Contributor

@Bkbest As jsteemann said, your build should be fine. However, you should not use a devel version in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsteemann jsteemann

Labels
1 Question 2 Solved Resolution 3 Core 3 RocksDB Storage engine related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jsteemann @Simran-B @Bkbest
0