如何解决如何处理Bash脚本中的Vagrant Up命令超时错误消息
所以我有一个初始化脚本，其中我试图处理一些错误，这些错误在无所事事的机器尝试出现时会弹出和/或发生。
init.sh脚本：
#!/bin/bash
# Timeout Error for SSH on Vagrantfile
TIMEOUT=$(echo "Timed out")
# Node Variables
MASTER=$(pwd | awk -F/ '{print $5}')-k8s-master
NODE_1=$(pwd | awk -F/ '{print $5}')-node-1
NODE_2=$(pwd | awk -F/ '{print $5}')-node-2
# Initialize Cluster
while true; do
read -p "Do you wish to initialize the cluster in $pwd (yes/no)?" yn
case $yn in
[Yy]* ) vagrant up; \
if (($TIMEOUT));
then vagrant destroy $MASTER -f;
vagrant up $MASTER --[no-]destroy-on-error;
elif (($TIMEOUT));
then vagrant destroy $NODE_1 -f;
vagrant up $NODE_1 --[no-]destroy-on-error;
elif (($TIMEOUT));
then vagrant destroy $NODE_2 -f;
vagrant up $NODE_2 --[no-]destroy-on-error;
else (($TIMEOUT=FALSE));
echo "Node Provisioned";
fi
break;; \
[Nn]* ) exit;;
* ) echo "Please answer yes or no.";;
esac
done
# Prepare Join Command
vagrant ssh -c "kubeadm token create --print-join-command > /tmp/temp_join_token.txt; \
cat /tmp/temp_join_token.txt; \
exit" \
$(pwd | awk -F/ '{print $5}')-k8s-master
# Copy the file within Directory opn Local Host
vagrant scp $(pwd | awk -F/ '{print $5}')-k8s-master:/tmp/temp_join_token.txt .
# Copy the File to Guest Machines
vagrant scp $(pwd)/temp_join_token.txt $(pwd | awk -F/ '{print $5}')-node-1:/home/vagrant
vagrant scp $(pwd)/temp_join_token.txt $(pwd | awk -F/ '{print $5}')-node-2:/home/vagrant
# Delete Token on Local host
rm $(pwd)/temp_join_token.txt
# Echo Completion
echo "Cluster has been initialized and Join Command is inside the worker nodes on home directory"
脚本的基本前提是仅在特定目录内的计算机上vagrant up。我有一个交互式提示，提示用户输入是或否，以从该目录中的Vagrantfile中“设置群集”。但是，在该目录中并且初始化vagrant up时，有时会收到如下错误消息：
Timed out...
该消息相当长，因此我只输入了前两个单词，但这是由于未在计算机上配置SSH。但是，我有一个解决方案：
- 如果流浪汉遇到主节点超时消息：销毁发生故障的计算机
vagrant destroy $MASTER -f
- 如果无业游民遇到Node-1工作节点的超时消息，则破坏发生故障的计算机：
vagrant destroy $NODE_1 -f
- 如果流浪汉遇到Node-2辅助节点的超时消息，请破坏发生故障的计算机：
vagrant destroy $NODE_2 -f
我知道我的提示的while循环语法可以工作，但是主要的重点是为这三个节点创建一个有条件的for循环，如果由于$ TIMEOUT而导致失败，则销毁它并将其重新备份直到它被调配。
我可以寻求帮助吗？
也许我在while循环中的if-then语句方法是错误的，不是很确定。
我也知道我的语法是错误的，因此我欢迎任何方法。
超时消息如下所示：
这里只是更新，但是当我运行脚本时，出现以下错误消息：
sto@suplab02:~/Engineering-Labs/jcarpentier/Kubernetes$ ./init.sh
Do you wish to initialize the cluster in (yes/no)?yes
Bringing machine 'jcarpentier-k8s-master' up with 'virtualbox' provider...
Bringing machine 'jcarpentier-node-1' up with 'virtualbox' provider...
Bringing machine 'jcarpentier-node-2' up with 'virtualbox' provider...
==> jcarpentier-k8s-master: Importing base box 'bento/ubuntu-16.04'...
==> jcarpentier-k8s-master: Matching MAC address for NAT networking...
==> jcarpentier-k8s-master: Checking if box 'bento/ubuntu-16.04' version '202008.16.0' is up to date...
==> jcarpentier-k8s-master: Setting the name of the VM: Kubernetes_jcarpentier-k8s-master_1598286213993_42402
==> jcarpentier-k8s-master: Fixed port collision for 22 => 2222. Now on port 2212.
==> jcarpentier-k8s-master: Vagrant has detected a configuration issue which exposes a
==> jcarpentier-k8s-master: vulnerability with the installed version of VirtualBox. The
==> jcarpentier-k8s-master: current guest is configured to use an E1000 NIC type for a
==> jcarpentier-k8s-master: network adapter which is vulnerable in this version of VirtualBox.
==> jcarpentier-k8s-master: Ensure the guest is trusted to use this configuration or update
==> jcarpentier-k8s-master: the NIC type using one of the methods below:
==> jcarpentier-k8s-master:
==> jcarpentier-k8s-master: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> jcarpentier-k8s-master: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> jcarpentier-k8s-master: Clearing any previously set network interfaces...
==> jcarpentier-k8s-master: Preparing network interfaces based on configuration...
jcarpentier-k8s-master: Adapter 1: nat
jcarpentier-k8s-master: Adapter 2: hostonly
==> jcarpentier-k8s-master: Forwarding ports...
jcarpentier-k8s-master: 22 (guest) => 2212 (host) (adapter 1)
==> jcarpentier-k8s-master: Running 'pre-boot' VM customizations...
==> jcarpentier-k8s-master: Booting VM...
==> jcarpentier-k8s-master: Waiting for machine to boot. This may take a few minutes...
jcarpentier-k8s-master: SSH address: 127.0.0.1:2212
jcarpentier-k8s-master: SSH username: vagrant
jcarpentier-k8s-master: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above,you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box,make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,as well.
If the box appears to be booting properly,you may want to increase
the timeout ("config.vm.boot_timeout") value.
./init.sh: line 14: ((: Timed out: syntax error in expression (error token is "out")
./init.sh: line 17: ((: Timed out: syntax error in expression (error token is "out")
./init.sh: line 20: ((: Timed out: syntax error in expression (error token is "out")
./init.sh: line 23: ((: Timed out=FALSE: syntax error in expression (error token is "out=FALSE")
Node Provisioned
我的问题似乎在于if then语句是否有任何建议：
if (($TIMEOUT));
then vagrant destroy $MASTER -f;
vagrant up $MASTER --[no-]destroy-on-error;
elif (($TIMEOUT));
then vagrant destroy $NODE_1 -f;
vagrant up $NODE_1 --[no-]destroy-on-error;
elif (($TIMEOUT));
then vagrant destroy $NODE_2 -f;
vagrant up $NODE_2 --[no-]destroy-on-error;
else (($TIMEOUT=FALSE));
echo "Node Provisioned";
fi
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。