3

I'm using Gitlab self server community version ci/cd function, It has been running well, But suddenly one day,All the projects in the gitlab/cicd has failed, it mentions below errors:

Uploading artifacts for successful job
Uploading artifacts...
promotion-api/my-boot-module-system/target/*.jar: found 1 matching files and directories 
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
WARNING: Retrying...                                context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed  id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
FATAL: invalid argument                            
ERROR: Job failed: exit code 1

Below is the code in .gitlab-ci.yml

deploy-java:
  stage: deploy
  dependencies:
    - build-java
  image:
    name: docker/compose:latest
  before_script:
    - docker info
    - docker-compose -v
  script:
    - cd promotion-api
    - docker-compose build
    - docker images
    - docker ps -a
    - docker-compose up -d
  tags:
    - promotion

2021-3-29:

I switched the runner from linux version to docker, seems all fine till now

Kris
  • 151
  • 1
  • 2
  • 12
  • This problem sometimes occurs and sometimes disappears, it seems to be related to the frequency of CI/CD – Kris Mar 22 '21 at 05:11
  • Was this previously building OK? If so, roll back the code to the last successful build point, and do your customer demo at that point. – halfer Mar 22 '21 at 08:47
  • In `responseStatus=500 Internal Server Error status=500`, what service is being contacted - is that a GitLab service to upload build artifacts? If this is a service that is under GitLab's control then you should report the server error to them. – halfer Mar 22 '21 at 08:48
  • @halfer The error is occured from gitlab server, It is built successfully before, It happens sometimes, Not so often. Is it possible to ignore to upload artifacts ? It is really no useful for me ... – Kris Mar 23 '21 at 02:09
  • Ah, is this an instance run by GitLab, or is it self-hosted? – halfer Mar 23 '21 at 19:46
  • @halfer self-hosted community version – Kris Mar 24 '21 at 00:13
  • Aha - please make a note of that in your post. That is probably quite relevant! – halfer Mar 24 '21 at 09:19
  • Have you looked through GitLab's bug tracker? Perhaps someone has encountered it before. – halfer Mar 24 '21 at 09:20
  • 1
    @halfer sure definitely, I just modied the question text, I switch the runner to docker version, seems all fine till now – Kris Mar 29 '21 at 04:56

2 Answers2

3

For me the problem was that gitlab had run out of disk-space.
After having deleted unnecessary artifacts and files everything was working correctly again.

You can check your system status (if you host your own gitlab) here: www.gitlab-url.com/admin/system_info
(Go to: Admin Area > Monitoring > System Info)

Hope it helps!

Gonen
  • 4,005
  • 1
  • 31
  • 39
Eduard Frankford
  • 151
  • 9
1

You ran into a bug in GitLab itself. Instead of a rather obscure HTTP status 500 it should say what the issue is explicitly. It is likely not a problem in your repository or CI settings.

Follow these issues to find out more:

Gogowitsch
  • 1,181
  • 1
  • 11
  • 32