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

[Bug]: milvus docker Exited (137) #38647

Open
1 task done
minglong-huang opened this issue Dec 23, 2024 · 1 comment
Open
1 task done

[Bug]: milvus docker Exited (137) #38647

minglong-huang opened this issue Dec 23, 2024 · 1 comment
Assignees
Labels
help wanted Extra attention is needed

Comments

@minglong-huang
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:milvusdb/milvus:v2.4.0
- Deployment mode(standalone or cluster):standalone 
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):pymilvus 2.5.0
- OS(Ubuntu or CentOS): Ubuntu 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Firstly, I installed milvus and ran it for a month using the following method:
wget https://github.com/milvus-io/milvus/releases/download/v2.4.0/milvus-standalone-docker-compose.yml -O docker-compose.yml
sudo docker-compose up -d
Then in recent days, it was discovered that milvus encountered an error during Docker startup
image
May I ask how to solve this problem and where can I find the corresponding reason for this Exitcode on the official website
I tried deleting and reinstalling them, but it didn't work

Expected Behavior

Resolve this issue

Steps To Reproduce

No response

Milvus Log

[
milvus.log
](url)

Anything else?

No response

@minglong-huang minglong-huang added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 23, 2024
@yanliang567
Copy link
Contributor

It seems that everything is working.

�[32mmilvus-standalone |�[0m [2024/12/21 02:26:46.896 +00:00] [DEBUG] [proxy/service.go:664] ["init Proxy done"]
�[32mmilvus-standalone |�[0m ---Milvus Proxy successfully initialized and ready to serve!---
�[32mmilvus-standalone |�[0m [2024/12/21 02:26:46.896 +00:00] [DEBUG] [proxy/service.go:428] ["init Proxy server done"]

Does Milvus keeps restarting in this case? if it only restart for once during docker startup, it could be expected for it might be waiting for the dependency service be healthy.

/assign @minglong-huang
/unassign

@yanliang567 yanliang567 added help wanted Extra attention is needed and removed kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants