Reduce the possibility of port conflicts and simplify deployment steps

[daikon12]

starrocks version: StarRocks-1.18.2
today I deployed a starrocks cluster according to documents.
It failed when I started Be, then I checked the log (log/be.out ):
W0908 16:38:03.955521 11189 task_worker_pool.cpp:1060] Fail to report task to :0, err=-1
E0908 16:38:03.959837 10949 doris_main.cpp:236] Doris Be http service did not start correctly, exiting

I noticed a problem with Be http service，but I still don't know why.
After some efforts, I know that some port in the configuration file conflicted.

I believe this has also troubled many friends. Let's share it here。
I came up with two solutions to make it easier for everyone to use：
1.Before start the script(start_be.sh or start_fe.sh), we first check whether the configured ports have conflicts
We can add the following logic to the startup script：
confdir=cd "$curdir"; pwd/../conf/be.conf
port_detected() {
serviceandport=grep -v ^# $confdir | grep "_port" | sed 's/ //g'
serviceandportarray=(${serviceandport// / })
for pair in ${serviceandportarray[@]}
do
service=echo $pair | awk -F '=' '{print $1}'
port=echo $pair | awk -F '=' '{print $2}'
res=netstat -anp | grep $port
if [ ! -z "$res" ]; then
echo "port $port already in use ! "
echo "Please check the configuration $service in $confdir"
exit 1
fi
done
}

2.Generate more log information in the doris_main.cpp

[Astralidea]

Hi @daikon12 Thanks for your report。
We already add more log information to slove this problem in this PR #26
For 2. It will affect in next release.

[daikon12]

@Astralidea Thanks for the quick reply, this pr is very valuable #26。In addition，I also suggest to check whether the deployment dependencies are satisfied before deployment。