website error
Q1: bkiam v3 failed
This error is usually caused by the rights center SaaS not starting after the machine is restarted. You need to manually pull up the SaaS
Central control machine execution /data/install/bkcli start saas-o
For other operations required for machine restart, see Machine Restart
Q2: Click on the plug-in and error message is displayed: The service is being deployed. Please wait
This is commonly seen in mongodb exceptions.
Central control machine execution /data/install/bkcli restart mongod
Then check whether the mongodb status is normal /data/install/bkcli status mongod
Q3: Plugin pack upload failure (R&D store)
Can check artifactory blueking users whether normal, speaking, reading and writing data directory: / data/bkce/public/ci/artifactory /
Then check the artifactory log file for errors.
Q4: Error bkiam v3 failed (Environment Management) (Builder) occurred when BKCI was adding nodes.
Then check the log according to the given documentation
/data/bkce/ci/environment/logs/environment-devops.log
/data/bkce/ci/environment/logs/auth-devops.log
The T_AUTH_IAM_CALLBACK table in the ci auth library is empty
The initial cluster configuration failed, but the script did not terminate
Q5: JOOQ; uncategorized SQLException for SQL (R&D Store) (Plugin)
The old sql is not cleaned up
Q6: pipeline start failed the upper limit of concurrency
If more than 50 tasks are running concurrently in a single pipeline, performance will be affected and the pipeline may fail. So the limit.
update devops_process.T_PIPELINE_SETTING set MAX_CON_RUNNING_QUEUE_SIZE=100 where database restrictions can be changed PIPELINE_ID = '${PIPELINE_ID}; A maximum of 100 is recommended
Q7: Error 2102004 using pipeline file variable
When uploading, you need to fill in the full path of the variable containing the file name. This functionality relies on the BKCI artifact Library.
Last updated