Gitlab 17.1.0 cannot start (gauge_all_sidekiq_exporter-0.db failed with weakmap value was not a string)
I'm the maintainer of the gitlab port for FreeBSD. I finished new packages for version 17.1.0, but I cannot start gitlab. While starting, I see in the sidekiq.log the following error:
==> sidekiq.log <==
W, [2024-06-21T10:06:14.648938 #7165] WARN -- : reading value from /usr/local/www/gitlab/tmp/prometheus_multiproc_dir/sidekiq/gauge_all_sidekiq_exporter-0.db failed with weakmap value was not a string
D, [2024-06-21T10:06:14.649984 #7165] DEBUG -- : /usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_dict.rb:42:in `fetch_entry'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_dict.rb:42:in `read_value'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:146:in `read_value'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:127:in `unsafe_initialize_file'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:107:in `block in initialize_file'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:106:in `synchronize'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:106:in `initialize_file'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/mmaped_value.rb:26:in `initialize'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/uses_value_type.rb:12:in `new'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/uses_value_type.rb:12:in `value_object'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/gauge.rb:23:in `default'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/metric.rb:21:in `block in initialize'
/usr/local/lib/ruby/gems/3.2/gems/prometheus-client-mmap-1.1.1/lib/prometheus/client/gauge.rb:28:in `set'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/ruby_sampler.rb:84:in `block (2 levels) in sample_gc'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/ruby_sampler.rb:83:in `each'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/ruby_sampler.rb:83:in `block in sample_gc'
<internal:kernel>:124:in `then'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/ruby_sampler.rb:82:in `sample_gc'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/ruby_sampler.rb:62:in `sample'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/base_sampler.rb:30:in `safe_sample'
/usr/local/www/gitlab/lib/gitlab/metrics/samplers/base_sampler.rb:72:in `start_working'
/usr/local/www/gitlab/lib/gitlab/daemon.rb:55:in `block in start'
/usr/local/www/gitlab/lib/gitlab/daemon.rb:52:in `synchronize'
/usr/local/www/gitlab/lib/gitlab/daemon.rb:52:in `start'
/usr/local/www/gitlab/metrics_server/metrics_server.rb:120:in `start'
/usr/local/www/gitlab/metrics_server/metrics_server.rb:67:in `fork'
/usr/local/www/gitlab/metrics_server/metrics_server.rb:33:in `start_for_sidekiq'
/usr/local/www/gitlab/sidekiq_cluster/cli.rb:164:in `restart_metrics_server'
/usr/local/www/gitlab/sidekiq_cluster/cli.rb:159:in `start_metrics_server'
/usr/local/www/gitlab/sidekiq_cluster/cli.rb:131:in `start_and_supervise_workers'
/usr/local/www/gitlab/sidekiq_cluster/cli.rb:106:in `run'
/usr/local/www/gitlab/bin/sidekiq-cluster:11:in `<main>'Do you have an idea, what can trigger this?