Open
Description
The first git clone from the client causes the repository to appear on the git-cache-http server, the second time git clone from the client leads to an error on the git-cache-http server: git clone exited with non-zero status: 128.
Apparently, the git-cache-http-server is trying to clone the repository again and is faced with the error that the repository already exists. A should send the repository from the cache to the client machine
git-cache-http-server.service - Caching git http server
Loaded: loaded (/etc/systemd/system/git-cache-http-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2024-08-06 05:22:15 EDT; 4s ago
Process: 9839 ExecStart=/root/.nvm/versions/node/v12.3.1/bin/git-cache-http-server --cache-dir /root/git_cache (code=exited, status=1/FAILURE)
Main PID: 9839 (code=exited, status=1/FAILURE)
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: at maybeClose (internal/child_process.js:1021:16)
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: at Socket.<anonymous> (internal/child_process.js:430:11)
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: at Socket.emit (events.js:200:13)
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: at Pipe.<anonymous> (net.js:586:12) {
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: val: 'git clone exited with non-zero status: 128',
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: message: 'git clone exited with non-zero status: 128'
Aug 06 05:22:15 localhost.localdomain git-cache-http-server[9839]: }
Aug 06 05:22:15 localhost.localdomain systemd[1]: git-cache-http-server.service: main process exited, code=exited, status=1/FAILURE
Aug 06 05:22:15 localhost.localdomain systemd[1]: Unit git-cache-http-server.service entered failed state.
Aug 06 05:22:15 localhost.localdomain systemd[1]: git-cache-http-server.service failed.
Metadata
Metadata
Assignees
Labels
No labels