[Bug]: After build milvus，start standalone failed

[mutezebra]

Is there an existing issue for this?

• I have searched the existing issues

Environment

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

Current Behavior

When I did the following behavior, I tried to activate the standalone, but it did not respond

$ git clone https://github.com/milvus-io/milvus.git
$ cd milvus/
$ ./scripts/install_deps.sh
$ make
$ cd deployments/docker/dev
$ docker-compose up -d
$ cd ../../../
$ ./scripts/start_standalone.sh

He only shows the starting... It's over.

$ ./scripts/start_standalone.sh
Starting standalone...

After waiting for a while, I tried to use go sdk to connect to 19530, but the timeout failed, so I used the command to check the port occupation and found that 19530 port was not occupied.

$ sudo netstat -tlnp | grep 19530
$ 

Does that mean that standalone startup failed? Where should I check the startup log?
Or do something else to get me connected to milvus server.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[SimFG]

you can find the log file /tmp/standalone.log

[mutezebra]

Thank you for reminding me. Through the log file, I found a fatal log output caused by the operation permission. I solved the problem by reusing sudo ./scripts/start_standalone.sh