One of the cases where the Spring Cloud Config service pulls the git configuration to fail

Keywords: basedir git spring cloud

Problems encountered: config-server pulls the configuration of gitlab has been normal. Suddenly one day the config-server can be normal, but the configuration has not been obtained for a long time and finally found to be

There is a problem with the path configured by basedir. It turned out that it was not possible for any reason, so just change the folder path.

   such as:

basedir: /releases/config/config-repo 

改为
basedir: C: / releases / config / config-repo is ok, this path can be changed to your own local 

unique problem. The problem is that it can be changed afterwards, and then changed to a path that has not been able to be pulled before, after success Suddenly. It is also possible to delete the automatically created folder.
such as:
basedir: C:/releases/config/config-repo
改为
basedir: / releases / config / config-repo is ok again 

, so the key points to note are
The folder set by basedir, the permissions corresponding to the folder, and the permissions for ide activation can also be checked to see if it is activated as an administrator. There are thousands of difficult problems, one for each.

Guess you like

Origin www.cnblogs.com/liuyu7177/p/12724556.html