Skip to content
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.

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

[Question]: infinity can not start normally #2550

Open
yyjsgdtc opened this issue Mar 27, 2025 · 0 comments
Open

[Question]: infinity can not start normally #2550

yyjsgdtc opened this issue Mar 27, 2025 · 0 comments
Labels
question Further information is requested

Comments

@yyjsgdtc
Copy link

Describe your problem

My computer shutdown unexpectedly,and when I turn on the computer, and use docker-compose to start ragflow, the infinity container can not start ,the log shows
2025-03-27 15:31:05 __ .__ . _______ __ . . __ ..____ ____
2025-03-27 15:31:05 | | | \ | | | __|| | | \ | | | | | |\ \ / /
2025-03-27 15:31:05 | | | | | | | | | | | | | | ---| |---- \ / /
2025-03-27 15:31:05 | | | . | | __| | | | . | | | | | _ _/
2025-03-27 15:31:05 | | | |\ | | | | | | |\ | | | | | | |
2025-03-27 15:31:05 || || __| || |
| |
| __| || || |_|
2025-03-27 15:31:05 Release: 0.6.0 build on 2025-02-05 11:55.07 with RelWithDebInfo mode from branch: , commit-id: v0.6.0-dev3-0-d498c5d
2025-03-27 15:31:05 Currently enabled SIMD support: f16c, sse2, avx, avx2
2025-03-27 15:31:05 [info] Config file: /infinity_conf.toml
2025-03-27 15:31:05 Infinity system configs:
2025-03-27 15:31:05 - version: 0.6.0
2025-03-27 15:31:05 - timezone: UTC-8
2025-03-27 15:31:05 - cpu_limit: 2
2025-03-27 15:31:05 - server mode: standalone
2025-03-27 15:31:05 - server address: 0.0.0.0
2025-03-27 15:31:05 - peer server ip: 0.0.0.0
2025-03-27 15:31:05 - peer server port: 23850
2025-03-27 15:31:05 - postgres port: 5432
2025-03-27 15:31:05 - http port: 23820
2025-03-27 15:31:05 - rpc client port: 23817
2025-03-27 15:31:05 - connection pool size: 128
2025-03-27 15:31:05 - peer server connection pool size: 128
2025-03-27 15:31:05 - log_filename: infinity.log
2025-03-27 15:31:05 - log_dir: /var/infinity/log
2025-03-27 15:31:05 - log_file_path: /var/infinity/log/infinity.log
2025-03-27 15:31:05 - log_to_stdout: true
2025-03-27 15:31:05 - log_file_max_size: 100.00MB
2025-03-27 15:31:05 - log_file_rotate_count: 10
2025-03-27 15:31:05 - log_level: Info
2025-03-27 15:31:05 - persistence_dir: /var/infinity/persistence
2025-03-27 15:31:05 - persistence_file_size: 134217728
2025-03-27 15:31:05 - data_dir: /var/infinity/data
2025-03-27 15:31:05 - cleanup_interval: 1m
2025-03-27 15:31:05 - compact_interval: 2m
2025-03-27 15:31:05 - optimize_index_interval: 10s
2025-03-27 15:31:05 - memindex_capacity: 65536
2025-03-27 15:31:05 - dense_index_building_worker: 2
2025-03-27 15:31:05 - sparse_index_building_worker: 2
2025-03-27 15:31:05 - fulltext_index_building_worker: 2
2025-03-27 15:31:05 - storage_type: local
2025-03-27 15:31:05 - snapshot_dir: /var/infinity/snapshot
2025-03-27 15:31:05 - buffer_manager_size: 8.00GB
2025-03-27 15:31:05 - temp_dir: /var/infinity/tmp
2025-03-27 15:31:05 - memindex_memory_quota: 4.00GB
2025-03-27 15:31:05 - wal_dir: /var/infinity/wal
2025-03-27 15:31:05 - buffer_manager_size: 1.00GB
2025-03-27 15:31:05 - full_checkpoint_interval: 30s
2025-03-27 15:31:05 - delta_checkpoint_interval: 5s
2025-03-27 15:31:05 - delta_checkpoint_threshold: 64.00MB
2025-03-27 15:31:05 - flush_method_at_commit: FlushAtOnce
2025-03-27 15:31:05 - resource_dir: /var/infinity/resource
2025-03-27 15:31:05 [07:31:05.544] [1] [info] ChangeServerRole from uninitialized to admin
2025-03-27 15:31:05 [07:31:05.544] [1] [info] Start to initialize storage from un-init mode to admin
2025-03-27 15:31:05 [07:31:05.545] [1] [info] Finish initializing storage from un-init mode to admin
2025-03-27 15:31:05 API server(for Infinity-SDK) listen on 0.0.0.0: 23817, connection limit: 128
2025-03-27 15:31:05 [07:31:05.591] [1] [info] Thrift server is started.
2025-03-27 15:31:05 Peer server listen on 0.0.0.0: 23850, connection limit: 64
2025-03-27 15:31:05 [07:31:05.609] [1] [info] Peer server is started.
2025-03-27 15:31:05 Run 'psql -h 0.0.0.0 -p 5432' to connect to the server (SQL is only for test).
2025-03-27 15:31:05 HTTP server listen on 0.0.0.0: 23820
2025-03-27 15:31:05 [07:31:05.609] [1] [info] ChangeServerRole from admin to standalone
2025-03-27 15:31:05 [07:31:05.610] [1] [info] Find temp wal file: /var/infinity/wal/wal.log
2025-03-27 15:31:05 [07:31:05.610] [1] [info] Start Wal Replay
2025-03-27 15:31:05 [07:31:05.610] [1] [info] Replay phase 1: find the max commit ts and catalog path
2025-03-27 15:31:05 [07:31:05.610] [1] [info] Find checkpoint max commit ts: 0
2025-03-27 15:31:05 [07:31:05.610] [1] [info] Replay phase 2: by the max commit ts, find the entries to replay
2025-03-27 15:31:05 [07:31:05.612] [1] [critical] Error: WAL replay: No checkpoint found in wal@src/storage/wal/wal_manager.cpp:792.
How should I handle the problem,thank you very much!

@yyjsgdtc yyjsgdtc added the question Further information is requested label Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant