Deuxfleurs/garage
49
56
Fork 73
Code Issues 98 Pull requests 12 Releases 30 Wiki Activity

garage craches on start #754

New issue
Closed
opened 2024-03-03 21:02:40 +00:00 by mr_tron · 3 comments
mr_tron commented 2024-03-03 21:02:40 +00:00
Copy link

one node fall out from cluster and now can't join to it.

2024-03-03T20:57:06.599673Z  INFO garage::server: Loading configuration...
2024-03-03T20:57:06.600064Z  INFO garage::server: Initializing Garage main data store...
2024-03-03T20:57:06.600155Z  INFO garage_model::garage: Opening database...
2024-03-03T20:57:06.600236Z  INFO garage_model::garage: Opening LMDB database at: /var/lib/garage/meta/db.lmdb
2024-03-03T20:57:06.600614Z  INFO garage_model::garage: Initialize background variable system...
2024-03-03T20:57:06.600635Z  INFO garage_model::garage: Initialize membership management system...
2024-03-03T20:57:06.600713Z  INFO garage_rpc::system: Node ID of this node: 5c59b2c749541080
2024-03-03T20:57:06.601044Z  INFO garage_model::garage: Initialize block manager...
2024-03-03T20:57:06.602004Z  INFO garage_model::garage: Initialize bucket_table...
2024-03-03T20:57:06.602354Z  INFO garage_model::garage: Initialize bucket_alias_table...
2024-03-03T20:57:06.602626Z  INFO garage_model::garage: Initialize key_table_table...
2024-03-03T20:57:06.602887Z  INFO garage_model::garage: Initialize block_ref_table...
2024-03-03T20:57:06.603153Z  INFO garage_model::garage: Initialize version_table...
2024-03-03T20:57:06.603422Z  INFO garage_model::garage: Initialize multipart upload counter table...
2024-03-03T20:57:06.603726Z  INFO garage_model::garage: Initialize multipart upload table...
2024-03-03T20:57:06.603987Z  INFO garage_model::garage: Initialize object counter table...
2024-03-03T20:57:06.604264Z  INFO garage_model::garage: Initialize object_table...
2024-03-03T20:57:06.604538Z  INFO garage_model::garage: Load lifecycle worker state...
2024-03-03T20:57:06.604711Z  INFO garage_model::garage: Initialize K2V counter table...
2024-03-03T20:57:06.605014Z  INFO garage_model::garage: Initialize K2V subscription manager...
2024-03-03T20:57:06.605036Z  INFO garage_model::garage: Initialize K2V item table...
2024-03-03T20:57:06.605332Z  INFO garage_model::garage: Initialize K2V RPC handler...
2024-03-03T20:57:06.605435Z  INFO garage::server: Initializing background runner...
2024-03-03T20:57:06.605530Z  INFO garage::server: Spawning Garage workers...
2024-03-03T20:57:06.605807Z  INFO garage::server: Initialize Admin API server and metrics collector...
2024-03-03T20:57:06.605856Z  INFO garage::server: Launching internal Garage cluster communications...
2024-03-03T20:57:06.606175Z  INFO garage::server: Create admin RPC handler...
2024-03-03T20:57:06.606215Z  INFO garage::server: Initializing S3 API server...
2024-03-03T20:57:06.606242Z  INFO garage::server: Launching Admin API server...
2024-03-03T20:57:06.606554Z  INFO garage_api::generic_server: S3 API server listening on http://[::]:3900
2024-03-03T20:57:06.606554Z  INFO garage_api::generic_server: Admin API server listening on http://0.0.0.0:3903
2024-03-03T20:57:06.607363Z ERROR garage_util::background::worker: Error in worker bucket_object_counter queue (TID 29): Too many errors
2024-03-03T20:57:06.635171Z ERROR garage_util::background::worker: Error in worker version GC (TID 40): in try_send_and_delete in table GC:
GC: send tombstones
Could not reach quorum of 2. 0 of 2 request succeeded, others returned errors: ["Netapp error: Not connected: 330fe77f09552f2a", "Netapp error: Not connected: 52f5c8753ee5b49b"]
/build/lmdb-rkv-sys-0.11.2/lmdb/libraries/liblmdb/mdb.c:3267: Assertion 'len >= 0 && id <= env->me_pglast' failed in mdb_freelist_save()
one node fall out from cluster and now can't join to it. ``` 2024-03-03T20:57:06.599673Z INFO garage::server: Loading configuration... 2024-03-03T20:57:06.600064Z INFO garage::server: Initializing Garage main data store... 2024-03-03T20:57:06.600155Z INFO garage_model::garage: Opening database... 2024-03-03T20:57:06.600236Z INFO garage_model::garage: Opening LMDB database at: /var/lib/garage/meta/db.lmdb 2024-03-03T20:57:06.600614Z INFO garage_model::garage: Initialize background variable system... 2024-03-03T20:57:06.600635Z INFO garage_model::garage: Initialize membership management system... 2024-03-03T20:57:06.600713Z INFO garage_rpc::system: Node ID of this node: 5c59b2c749541080 2024-03-03T20:57:06.601044Z INFO garage_model::garage: Initialize block manager... 2024-03-03T20:57:06.602004Z INFO garage_model::garage: Initialize bucket_table... 2024-03-03T20:57:06.602354Z INFO garage_model::garage: Initialize bucket_alias_table... 2024-03-03T20:57:06.602626Z INFO garage_model::garage: Initialize key_table_table... 2024-03-03T20:57:06.602887Z INFO garage_model::garage: Initialize block_ref_table... 2024-03-03T20:57:06.603153Z INFO garage_model::garage: Initialize version_table... 2024-03-03T20:57:06.603422Z INFO garage_model::garage: Initialize multipart upload counter table... 2024-03-03T20:57:06.603726Z INFO garage_model::garage: Initialize multipart upload table... 2024-03-03T20:57:06.603987Z INFO garage_model::garage: Initialize object counter table... 2024-03-03T20:57:06.604264Z INFO garage_model::garage: Initialize object_table... 2024-03-03T20:57:06.604538Z INFO garage_model::garage: Load lifecycle worker state... 2024-03-03T20:57:06.604711Z INFO garage_model::garage: Initialize K2V counter table... 2024-03-03T20:57:06.605014Z INFO garage_model::garage: Initialize K2V subscription manager... 2024-03-03T20:57:06.605036Z INFO garage_model::garage: Initialize K2V item table... 2024-03-03T20:57:06.605332Z INFO garage_model::garage: Initialize K2V RPC handler... 2024-03-03T20:57:06.605435Z INFO garage::server: Initializing background runner... 2024-03-03T20:57:06.605530Z INFO garage::server: Spawning Garage workers... 2024-03-03T20:57:06.605807Z INFO garage::server: Initialize Admin API server and metrics collector... 2024-03-03T20:57:06.605856Z INFO garage::server: Launching internal Garage cluster communications... 2024-03-03T20:57:06.606175Z INFO garage::server: Create admin RPC handler... 2024-03-03T20:57:06.606215Z INFO garage::server: Initializing S3 API server... 2024-03-03T20:57:06.606242Z INFO garage::server: Launching Admin API server... 2024-03-03T20:57:06.606554Z INFO garage_api::generic_server: S3 API server listening on http://[::]:3900 2024-03-03T20:57:06.606554Z INFO garage_api::generic_server: Admin API server listening on http://0.0.0.0:3903 2024-03-03T20:57:06.607363Z ERROR garage_util::background::worker: Error in worker bucket_object_counter queue (TID 29): Too many errors 2024-03-03T20:57:06.635171Z ERROR garage_util::background::worker: Error in worker version GC (TID 40): in try_send_and_delete in table GC: GC: send tombstones Could not reach quorum of 2. 0 of 2 request succeeded, others returned errors: ["Netapp error: Not connected: 330fe77f09552f2a", "Netapp error: Not connected: 52f5c8753ee5b49b"] /build/lmdb-rkv-sys-0.11.2/lmdb/libraries/liblmdb/mdb.c:3267: Assertion 'len >= 0 && id <= env->me_pglast' failed in mdb_freelist_save() ```
kinovic commented 2024-03-04 13:50:35 +00:00
Copy link

We had a similar issue today. Check if the node that fell off does see other nodes with proper IP/addresses. For us, one of the nodes had 127.0.0.1:port. We were unable to track the core reason. Calling connect to all other nodes helped us. Something like:

garage node connect HASH@storage-b.original.instance:3901

Connect used the same way as in the documentation: https://garagehq.deuxfleurs.fr/documentation/cookbook/real-world/

We had a similar issue today. Check if the node that fell off does see other nodes with proper IP/addresses. For us, one of the nodes had `127.0.0.1:port`. We were unable to track the core reason. Calling connect to all other nodes helped us. Something like: ``` garage node connect HASH@storage-b.original.instance:3901 ``` Connect used the same way as in the documentation: https://garagehq.deuxfleurs.fr/documentation/cookbook/real-world/
lx commented 2024-03-04 13:55:25 +00:00
Owner
Copy link
/build/lmdb-rkv-sys-0.11.2/lmdb/libraries/liblmdb/mdb.c:3267: Assertion 'len >= 0 && id <= env->me_pglast' failed in mdb_freelist_save()

This line seems to indicate that your LMDB database file is corrupted. The best is probably to rebuild it from scratch if you can (see recovering from failures).

@kinovic Do you also have a similar message in your logs regarding LMDB?

``` /build/lmdb-rkv-sys-0.11.2/lmdb/libraries/liblmdb/mdb.c:3267: Assertion 'len >= 0 && id <= env->me_pglast' failed in mdb_freelist_save() ``` This line seems to indicate that your LMDB database file is corrupted. The best is probably to rebuild it from scratch if you can (see [recovering from failures](https://garagehq.deuxfleurs.fr/documentation/operations/recovering/)). @kinovic Do you also have a similar message in your logs regarding LMDB?
kinovic commented 2024-03-04 15:24:14 +00:00
Copy link

@lx I have read the issue wrong... We had a different problem then. Thank you for your explanation.

@lx I have read the issue wrong... We had a different problem then. Thank you for your explanation.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
update-dependencies-1.1
feat-metrics-metadata-engine
improve-secret-error-message
hotfix/1.0.0-rc1-red-ftr-wquorum
main-0.9.x
db-no-unsafe
main-0.8.x
k2v/shared_http_client
feat/website-redir
smithy2
test/compilation
poc/nomad-ci
test-ci-wait
pnet_datalink-0.33.0
optimal-layout
k2v-watch-range
db-debug-log
build-convert-db
demonstrate-cargo2nix-bug
dangerous/no-fsync
dev0.7.3
doc/benchmarks
bug/check_static
bucket-cors-more
storage-optimizations
old-main
v1.0.1
v1.0.0
v0.9.4
v1.0.0-rc1
v0.8.7
v0.9.3
v0.9.2
v0.8.6
v0.9.2-rc1
v0.9.1
v0.8.5
v0.10.0-beta1
v0.9.0
v0.9.0-rc2
v0.9.0-rc1
v0.9.0-beta4
v0.9.0-beta3
v0.9.0-beta2
v0.8.4
v0.9.0-beta1
v0.8.3
v0.8.3-rc1
format_table-v0.1.1
format_table-v0.1.0
v0.8.2
v0.8.1
v0.8.0
v0.8.0-rc2
v0.8.0-rc1
v0.8.0-dangerous-no-fsync
v0.8.0-beta2-k2v
v0.8.0-beta2
v0.8.0-beta1-k2v
v0.8.0-beta1
v0.7.99.3-k2v
v0.7.3
v0.7.3-beta2
v0.7.3-beta1
v0.7.2.1
v0.7.2
v0.7.2_ci-test-2
v0.7.2+ci-test-version
v0.7.99.2-k2v
v0.7.99.1-k2v
v0.7.99-k2v
v0.7.2-k2v
v0.7.1-admin-k2v-2
v0.7.1-admin-k2v
v0.7.1-k2v
v0.7.1
v0.7.0
v0.7.0-rc1
v0.6.1
v0.6.0
v0.6.0-rc1
v0.5.1
v0.5.0.1
v0.5.0
v0.5-beta1
v0.4.0
v0.4-rc2
v0.4-rc1
0.4-beta
0.4-alpha
v0.3.0.2
v0.3.0.1
v0.3.0
v0.2.1.5
v0.2.1
v0.2.0
0.1.1b
0.1.1
0.1.0b
0.1.0
Labels
Clear labels   
action
check-aws
The behaviour should be checked against AWS S3

  
action
discussion-needed
We need to discuss if the feature is desirable and/or better specify the envisioned behavior or technical implementation

  
action
for-external-contributors
Core team does not plan working on this in the near future however an external contribution will be reviewed & merged

  
action
for-newcomers
An issue that should be newcomer friendly.

  
action
more-info-needed
More information is needed to investigate this issue

  
action
need-funding
This issue represents lots of work, we need to find money to pay our core team work

  
action
triage-required
It's not very clear what we want to do with this issue yet, more thoughts is required

  
kind
correctness
Issues of theoretical correctness that may impact edge-case scenarios

  
kind
ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims

  
kind
improvement
Feature requests that do not fall in other categories

  
kind
performance
Deceptive performance observed OR idea to improve performances

  
kind
testing
Functional tests, integration tests, Jepsen, etc.

  
kind
usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.

  
kind
wrong-behavior
Unintended behavior

  
prio
critical
Could impact integrity or availability of production clusters

  
prio
low
For issues that we don't want to spend time on until made absolutely necessary

  
scope
admin-api
Issues concerning the administration API

  
scope
background-healing
Background healing covers repair tasks, anti-entropy, merkle trees, etc. ; everything related to replicating data appropriately.

  
scope
build
Issues with Nix, Drone, Rust Compiler, etc.

  
scope
documentation

  
scope
k8s
Kubernetes related, including Helm Charts

  
scope
layout
Linked to the cluster layout and storage management

  
scope
metadata
Metadata Engine (LMDB, sqlite, etc.)

  
scope
ops
Operations related to operations/maintenance issue, tooling related (like CLI missing info ; impossible, too dangerous, too complicated migration, etc.)

  
scope
rpc
Linked to RPC

  
scope
s3-api
Related to the S3 API (especially compatibility issues).

  
scope
security
Cryptography-related, auth-related, authorization-related issues

  
scope
telemetry
OpenTelemetry (traces, metrics, etc.)

No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#754
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?