Pulled the latest code and things broke , please adivse how to fix below error
things were working yesterday , but today failing to load
error is below
'LibreChat | 2024-11-06 03:03:19 error: KeyvMongo connection error: connect ECONNREFUSED 10.194.116.33:27017
LibreChat | 2024-11-06 03:03:19 error: There was an uncaught error: connect ECONNREFUSED 10.194.116.33:27017'
Steps to Reproduce
i use the folllowing command to run a local deployment
cd C:\personal\LibreChat; docker-compose down; git status; git pull; git log -1; docker-compose build; docker-compose up
What browsers are you seeing the problem on?
Chrome
Relevant log output
chat-mongodb | 2024-11-06T02:59:58.480+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730861998:480098][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata Raw: [1730861998:480098][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata
chat-mongodb | 2024-11-06T02:59:58.480+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730861998:480112][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk Raw: [1730861998:480112][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
chat-mongodb | 2024-11-06T02:59:58.480+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730861998:480122][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options Raw: [1730861998:480122][1:0x7f4e9dee7a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options
chat-mongodb | 2024-11-06T02:59:58.576+0000 F STORAGE [initandlisten] WiredTiger metadata corruption detected
chat-mongodb | 2024-11-06T02:59:58.576+0000 F STORAGE [initandlisten] This version of MongoDB is unable to repair this kind of corruption, but version 4.0.3+ may be able to repair it. See http://dochub.mongodb.org/core/repair for more information.
chat-mongodb | 2024-11-06T02:59:58.576+0000 F - [initandlisten] Fatal Assertion 50944 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 71
chat-mongodb | 2024-11-06T02:59:58.576+0000 F - [initandlisten] \n\n***aborting after fassert() failure\n\n
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=0eeea31db8ce
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] db version v3.6.23
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] git version: d352e6a4764659e0d0350ce77279de3c1f243e5c
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] allocator: tcmalloc
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] modules: none
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] build environment:
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] distmod: ubuntu1604
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] distarch: x86_64
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] target_arch: x86_64
chat-mongodb | 2024-11-06T03:00:05.028+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true }, security: { authorization: "disabled" } }
chat-mongodb | 2024-11-06T03:00:05.129+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
chat-mongodb | 2024-11-06T03:00:05.168+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7413M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
chat-mongodb | 2024-11-06T03:00:07.851+0000 E STORAGE [initandlisten] WiredTiger error (-31802) [1730862007:851611][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 604: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Raw: [1730862007:851611][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 604: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
chat-mongodb | 2024-11-06T03:00:07.851+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730862007:851722][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata Raw: [1730862007:851722][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata
chat-mongodb | 2024-11-06T03:00:07.851+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730862007:851735][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk Raw: [1730862007:851735][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
chat-mongodb | 2024-11-06T03:00:07.851+0000 E STORAGE [initandlisten] WiredTiger error (0) [1730862007:851744][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options Raw: [1730862007:851744][1:0x7f0dced7da40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options
chat-mongodb | 2024-11-06T03:00:07.911+0000 F STORAGE [initandlisten] WiredTiger metadata corruption detected
chat-mongodb | 2024-11-06T03:00:07.911+0000 F STORAGE [initandlisten] This version of MongoDB is unable to repair this kind of corruption, but version 4.0.3+ may be able to repair it. See http://dochub.mongodb.org/core/repair for more information.
chat-mongodb | 2024-11-06T03:00:07.911+0000 F - [initandlisten] Fatal Assertion 50944 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 71
chat-mongodb | 2024-11-06T03:00:07.911+0000 F - [initandlisten] \n\n***aborting after fassert() failure\n\n
LibreChat | 2024-11-06 03:00:08 error: KeyvMongo connection error: connect ECONNREFUSED 172.18.0.4:27017
LibreChat | 2024-11-06 03:00:08 error: There was an uncaught error: connect ECONNREFUSED 172.18.0.4:27017
LibreChat | npm notice
LibreChat | npm notice New minor version of npm available! 10.7.0 -> 10.9.0
LibreChat | npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
LibreChat | npm notice To update run: npm install -g npm@10.9.0
LibreChat | npm notice
LibreChat exited with code 0
Screenshots
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What happened?
Pulled the latest code and things broke , please adivse how to fix below error
things were working yesterday , but today failing to load
error is below 'LibreChat | 2024-11-06 03:03:19 error: KeyvMongo connection error: connect ECONNREFUSED 10.194.116.33:27017 LibreChat | 2024-11-06 03:03:19 error: There was an uncaught error: connect ECONNREFUSED 10.194.116.33:27017'
Steps to Reproduce
i use the folllowing command to run a local deployment cd C:\personal\LibreChat; docker-compose down; git status; git pull; git log -1; docker-compose build; docker-compose up
What browsers are you seeing the problem on?
Chrome
Relevant log output
Screenshots
Code of Conduct