... | ... | @@ -82,4 +82,22 @@ Example: I open https://db.nomics.world/SCSMICH/MICS and it is "404 not found". |
|
|
- if a JSON document is displayed, it's OK
|
|
|
- else
|
|
|
- before reindexing check that there is disk space on the server
|
|
|
- try to index in *full mode* (not incremental mode): see [Solr indexation](./solr-indexation) |
|
|
\ No newline at end of file |
|
|
- try to index in *full mode* (not incremental mode): see [Solr indexation](./solr-indexation)
|
|
|
|
|
|
# Jobs stuck / Runner not responding
|
|
|
|
|
|
A runner is considered as stuck when the time of last contact is longer than one hour. You can find this information in the admin panel, by looking at the "Last contact" column in list of the runners registered for the Gitlab instance you're working with, for example: https://git.nomics.world/admin/runners.
|
|
|
|
|
|
First, connect to the server on which the runner is installed, for example:
|
|
|
|
|
|
```
|
|
|
ssh root@163.172.67.63
|
|
|
```
|
|
|
|
|
|
Then restart the runner service:
|
|
|
|
|
|
```
|
|
|
systemctl restart gitlab-runner.service
|
|
|
```
|
|
|
|
|
|
Gitlab should be able to "contact" the runner again and the jobs can be restarted as normal. |
|
|
\ No newline at end of file |