Error in shell: [!: Analysis solution of [!: command not found]

1. Report an error in the shell:[!: command not found，如图1

[Caption id=”attachment_4126″ align=”alignnone” width=”1363″]#ATFP_CLOSE_Translate_span# Figure 1[/caption]#atfp_close_translate_span#

2020/5/6 2:56:57 pcs_api_cfg_action_log_absolute_path=/var/log/pcs
2020/5/6 2:56:57 pm /config/init/console_init.sh: line 40:[!: command not found
2020/5/6 2:56:57 running chown -r nginx:nginx /var/log/pcs
2020/5/6 2:56:57 pm /config/init/cronlog.sh: line 4: log_name: unbound variable
2020/5/6 2:56:58 pm Unlinking stale socket /var/run/supervisor/supervisor.sock

#atfp_close_translate_span#
2. Edit /build/c_files/config/init/console_init.sh. at[]Add spaces before and after. as shown in Figure 2

Figure 2

env | grep pcs_api_cfg_action_log_absolute_path || export pcs_api_cfg_action_log_absolute_path="/var/log/pcs"
if[[ $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH != "" ]]
in
if[! -d $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH]
in
mkdir -P $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH
fi
chown -r nginx:nginx $pcs_api_cfg_action_log_absolute_path
echo "running chown -r nginx:nginx $pcs_api_cfg_action_log_absolute_path"
else
echo "Please Set Environment Variable PCS_API_CFG_Action_log_Absolute_Path Can Not Be Empty"
fi

env | grep pcs_api_cfg_action_log_absolute_path || export pcs_api_cfg_action_log_absolute_path="/var/log/pcs"
if[[ $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH != "" ]]
in
if[ ! -d $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH ]
in
mkdir -P $PCS_API_CFG_ACTION_LOG_ABSOLUTE_PATH
fi
chown -r nginx:nginx $pcs_api_cfg_action_log_absolute_path
echo "running chown -r nginx:nginx $pcs_api_cfg_action_log_absolute_path"
else
echo "Please Set Environment Variable PCS_API_CFG_Action_log_Absolute_Path Can Not Be Empty"
fi

3. There is no error in the shell. And the error: unlinking stale socket /var/run/supervisor/supervisor.sock has also disappeared. as shown in Figure 3

Figure 3

2020/5/8 2:17:09 pcs_api_cfg_action_log_absolute_path=/var/log/pcs
2020/5/8 2:17:09 running chown -r nginx:nginx /var/log/pcs
2020/5/8 2:17:09 pm /config/init/cronlog.sh: line 4: log_name: unbound variable