Langsung masuk ke status "CrashLoopBackOff".
Langsung masuk ke status "CrashLoopBackOff".
Halo,
ERPNext adalah aplikasi yang cukup berat. Untuk memeriksa CrashLoopBackOff, saya memerlukan log aktual dan ID layanan. Mohon lengkapi informasi berikut:
Masalah deployment ERPNext yang umum:
bench new-site. Langkah ini memerlukan MariaDB yang sudah siap; urutan startup yang salah akan menyebabkan crash.Lengkapi ketiga informasi di atas, dan kami dapat membantu Anda melihat penyebab pastinya.
ID Proyek: project-6a0c5c5233d1a635fa37b3b5
ID Layanan: service-6a0c5ca940a883532f3311ad
Server berada di Wonder Mesh, dan mesinnya berkapasitas 6C/64GB.
Log Runtime:
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.108s (1.108s including waiting). Image size: 929010383 bytes.
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.104s (1.104s including waiting). Image size: 929010383 bytes.
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.121s (1.121s including waiting). Image size: 929010383 bytes.
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)
[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)
Halo, setelah diperiksa, ini adalah masalah yang diketahui pada template komunitas ERPNext—image Docker yang dikonfigurasi dalam template adalah frappe/bench:latest (alat pengembangan), bukan image produksi frappe/erpnext yang benar, sehingga container akan langsung keluar setelah dimulai.
Cara memperbaiki:
frappe/bench:latest menjadi frappe/erpnext:v16.Jika masalah masih berlanjut setelah perubahan, silakan beri tahu kami.