Errors on latest docker arangodb/arangodb-preview image #13877
Labels
Comments
|
It's look like that I have to do a Now it works. I well try to close this ticker. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My Environment
$docker-compose up
Starting arango_arangodb_db_container_1 ... done
Attaching to arango_arangodb_db_container_1
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [e52b0] {general} ArangoDB 3.8.0-alpha.1 [linux] 64bit, using jemalloc, build tags/v3.8.0-alpha.1-0-gf46ea7b6ff, VPack 0.1.35, RocksDB 6.8.0, ICU 64.2, V8 7.9.317, OpenSSL 1.1.1k 25 Mar 2021
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [75ddc] {general} detected operating system: Linux version 5.11.10-1-MANJARO (builduser@LEGION) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu Mar 25 17:14:55 UTC 2021
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [25362] {memory} Available physical memory: 16728309760 bytes, available cores: 8
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] WARNING [118b0] {memory} maximum number of memory mappings per process is 65530, which seems too low. it is recommended to set it to at least 512000
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] WARNING [49528] {memory} execute 'sudo sysctl -w "vm.max_map_count=512000"'
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [144fe] {general} using storage engine 'rocksdb'
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [3bb7d] {cluster} Starting up with role SINGLE
arangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [f6e0e] {aql} memory limit per AQL query automatically set to 10036985856 bytes. to modify this value, please adjust the startup option
--query.memory-limitarangodb_db_container_1 | 2021-03-30T15:26:37Z [1] INFO [a1c60] {syscall} file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] INFO [c1b63] {arangosearch} ArangoSearch maintenance: [1..1] commit thread(s), [1..1] consolidation thread(s)
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [3bc7f] {startup} Database directory version (30710) is lower than current version (30800).
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [ebca0] {startup} ----------------------------------------------------------------------
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [24e3c] {startup} It seems like you have upgraded the ArangoDB binary.
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [8bcec] {startup} If this is what you wanted to do, please restart with the
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [b0360] {startup} --database.auto-upgrade true
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [13414] {startup} option to upgrade the data in the database directory.
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [24bd1] {startup} ----------------------------------------------------------------------'
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] ERROR [1c156] {general} Database '_system' needs upgrade. Please start the server with --database.auto-upgrade
arangodb_db_container_1 | 2021-03-30T15:26:38Z [1] FATAL [2eb08] {general} Database '_system' upgrade failed (bad parameter). Please inspect the logs from the upgrade procedure and try starting the server again.
The text was updated successfully, but these errors were encountered: