[Bug] dokploy平台使用docker-compose部署服务区版本，正常运行一段时间后总是自动退出 #5383
Comments
|
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
|
I found a similar unsolved discussion regarding a docker deployment error where the service exits unexpectedly [1]. This might be related to the issue you're experiencing with the lobe-chat-database service exiting after some time. The error message "ReferenceError: Cannot access 'm' before initialization" suggests that there might be a problem with variable initialization in the code. This type of error typically occurs when a variable is used before it has been declared or initialized. To address this issue, you might want to check the code for any variables that are being accessed before they are initialized. Additionally, ensure that all environment variables and configurations are correctly set up in your docker-compose file, as incorrect configurations can sometimes lead to unexpected service exits. If the problem persists, consider reviewing the specific code sections mentioned in the error logs to identify where the initialization issue might be occurring. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
|
我之前在dokploy上使用docker-compose部署没遇到过这个问题，自动退出后重新启动就可以了吧 |
I have never encountered this problem before using docker-compose deployment on dokploy. I just need to automatically exit and restart. |
|
#5352 |
#5352 |
不能重新启动 需要手动启动，而且都不提示状态异常，deployment状态都显示正常。 |
It cannot be restarted and needs to be started manually. It does not prompt any abnormal status and the deployment status shows normal. |
感觉是Dokploy的问题，之前也遇到过2次容器全部退出，但是也没显示异常，手动重启的，不过最近没遇到过了，现在用的最新版本 |
I feel it is a problem with Dokploy. I have encountered it twice before when all the containers exited, but no exception was displayed. I restarted it manually. However, I have not encountered it recently. I am using the latest version. |
|
回滚到 1.44.1 版本试试 |
Try rolling back to version 1.44.1 |
成 我试试看 试完再来反馈 |
OK, I'll give it a try and give you feedback after I've finished. |
我用的也是最新版本，还是没能解决。 |
I'm also using the latest version and still can't solve it. |
|
试下最新版本，应该已经修复才对 |
github-project-automation
bot
moved this from Roadmap - Chat 1.x
to Done
in Lobe Chat Routine
Try the latest version, it should be fixed. |
|
This issue is closed, If you have any questions, you can comment and reply. |
📦 Environment
Other
📌 Version
1.45
💻 Operating System
Ubuntu
🌐 Browser
Edge
🐛 Bug Description
2025-01-10T05:13:36.785Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:36.785Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:36.785Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:36.785Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:36.785Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:36.785Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:36.785Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:36.785Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:36.785Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:36.785Z at t (.next/server/webpack-runtime.js:1:143)
2025-01-10T05:13:36.786Z ⨯ unhandledRejection: ReferenceError: Cannot access 'm' before initialization
2025-01-10T05:13:36.786Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:36.786Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:43.648Z {
2025-01-10T05:13:43.648Z allowDangerousEmailAccountLinking: true,
2025-01-10T05:13:43.648Z clientId: undefined,
2025-01-10T05:13:43.648Z clientSecret: undefined,
2025-01-10T05:13:43.648Z platformType: 'WebsiteApp',
2025-01-10T05:13:43.648Z profile: [Function: profile]
2025-01-10T05:13:43.648Z }
2025-01-10T05:13:36.786Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:36.786Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:36.786Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:36.786Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:36.786Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:36.786Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:36.786Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:36.786Z at t (.next/server/webpack-runtime.js:1:143)
2025-01-10T05:13:43.769Z ⨯ ReferenceError: Cannot access 'm' before initialization
2025-01-10T05:13:43.769Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:43.769Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:43.769Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:43.769Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:43.769Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:43.769Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:43.769Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:43.769Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:43.769Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:43.769Z at t (.next/server/webpack-runtime.js:1:143) {
2025-01-10T05:13:43.769Z digest: '2116735162'
2025-01-10T05:13:43.769Z }
2025-01-10T05:13:52.354Z ⨯ ReferenceError: Cannot access 'm' before initialization
2025-01-10T05:13:52.354Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:52.354Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:52.354Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:52.354Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:52.354Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:52.354Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:52.354Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:52.354Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:52.354Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:52.354Z at t (.next/server/webpack-runtime.js:1:143) {
2025-01-10T05:13:52.354Z digest: '2116735162'
2025-01-10T05:13:52.354Z }
2025-01-10T05:13:57.169Z ⨯ ReferenceError: Cannot access 'm' before initialization
2025-01-10T05:13:57.169Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:57.169Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:57.169Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:57.169Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:57.169Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:57.169Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:57.169Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:57.169Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:57.169Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:57.169Z at t (.next/server/webpack-runtime.js:1:143) {
2025-01-10T05:14:06.636Z next auth: undefined
2025-01-10T05:14:06.637Z {"level":30,"time":1736486046636,"pid":28,"hostname":"4e8c9fee27ba","msg":"Error in tRPC handler (lambda) on path: topic.createTopic, type: mutation"}
2025-01-10T05:22:12.120Z {
2025-01-10T05:22:12.120Z allowDangerousEmailAccountLinking: true,
2025-01-10T05:22:12.120Z clientId: undefined,
2025-01-10T05:22:12.120Z clientSecret: undefined,
2025-01-10T05:22:12.120Z platformType: 'WebsiteApp',
2025-01-10T05:22:12.120Z profile: [Function: profile]
2025-01-10T05:22:12.120Z }
2025-01-10T05:13:57.169Z digest: '2116735162'
2025-01-10T05:13:57.169Z }
2025-01-10T05:13:58.954Z ⨯ ReferenceError: Cannot access 'm' before initialization
2025-01-10T05:13:58.954Z at Object.y (.next/server/chunks/39817.js:257:19183)
2025-01-10T05:13:58.954Z at (.next/server/chunks/39817.js:257:23459)
2025-01-10T05:13:58.954Z at (.next/server/chunks/86177.js:159:1345)
2025-01-10T05:13:58.954Z at o (.next/server/chunks/86177.js:159:1740)
2025-01-10T05:13:58.954Z at s (.next/server/chunks/86177.js:159:1766)
2025-01-10T05:13:58.954Z at d (.next/server/chunks/86177.js:159:1943)
2025-01-10T05:13:58.954Z at (.next/server/chunks/39817.js:257:23405)
2025-01-10T05:13:58.954Z at t.a (.next/server/webpack-runtime.js:1:989)
2025-01-10T05:13:58.954Z at 955225 (.next/server/chunks/39817.js:257:23158)
2025-01-10T05:13:58.954Z at t (.next/server/webpack-runtime.js:1:143) {
2025-01-10T05:13:58.954Z digest: '2116735162'
2025-01-10T05:13:58.954Z }
2025-01-10T05:14:06.638Z Error [TRPCError]: UNAUTHORIZED
2025-01-10T05:14:06.638Z at (.next/server/chunks/17836.js:1:7685)
2025-01-10T05:14:06.638Z at f (.next/server/chunks/12620.js:4:74)
2025-01-10T05:14:06.638Z at r (.next/server/chunks/12620.js:1:5805)
2025-01-10T05:14:06.638Z at (.next/server/chunks/98787.js:1:7780)
2025-01-10T05:14:06.638Z at Array.map ()
2025-01-10T05:14:06.638Z at g (.next/server/chunks/98787.js:1:7317)
2025-01-10T05:14:06.638Z at async r (.next/server/chunks/22699.js:1:428) {
2025-01-10T05:14:06.638Z cause: undefined,
2025-01-10T05:14:06.638Z code: 'UNAUTHORIZED'
2025-01-10T05:14:06.638Z }
📷 Recurrence Steps
dokploy版本V0.15.1
试了好几个版本都一样，部署lobe-chat-database运行一段时间后自己退出，然后就要重新部署。
后台日志如上，不知道问题在哪里。
🚦 Expected Behavior
不再退出
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: