This job does not have a trace. Another reason?

My jobs don’t have logs.

I’ve installed the latest version of GitLab Runner from this link.

My current GitLab Runner version is:

  • Version: 16.8.0
  • Git revision: c72a09b6
  • Git branch: 16-8-stable
  • GO version: go1.21.5
  • Built: 2024-01-18T22:42:25+0000
  • OS/Arch: linux/amd64

My operating system details:

  • OS: Ubuntu-20.04-amd64
  • Hardware: KVM SSD (1 CPU/768 MB RAM/7 GB SSD)

Time zone information:

  • Local time: Mon 2024-02-12 23:14:39 MSK
  • Universal time: Mon 2024-02-12 20:14:39 UTC
  • RTC time: Mon 2024-02-12 20:14:40
  • Time zone: Europe/Moscow (MSK, +0300)
  • System clock synchronized: yes
  • NTP service: active
  • RTC in local TZ: no

Here is what my .gitlab-ci.yml looks like:

  - deploy

  stage: deploy
    - echo PWD
    - payment_gate

The job appears to run correctly, but without generating any logs. I’ve already reviewed topics on the forum such as:

However, I haven’t found an answer. Could someone please help me figure out how to fix this issue?

Additionally, I’ve observed that the logs stopped appearing right after I attempted to use SSH connections within my script. Here are the commands I incorporated:

  - ssh root@
  - cd /root
  - pwd

This change was aimed at executing commands on a remote server, but it seems to coincide with the issue of disappearing logs.

Issue with Missing Job Logs and 409 Conflict Error

I’ve encountered an issue where my job finishes correctly, but without generating any logs. Below is the log from when the job was executed, as captured by journalctl:

– Logs begin at Sat 2024-01-27 18:46:50 MSK. –
Feb 14 22:23:38 systemd[1]: Stopped GitLab Runner.
Feb 14 22:23:38 systemd[1]: Started GitLab Runner.
Feb 14 22:23:38 gitlab-runner[559264]: Runtime platform arch=amd64 os=linux pid=559264 revision=c72a09b6 version=16.8.0
Feb 14 22:23:38 gitlab-runner[559264]: Starting multi-runner from /etc/gitlab-runner/config.toml… builds=0 max_builds=0
Feb 14 22:23:38 gitlab-runner[559264]: Running in system-mode.
Feb 14 22:23:38 gitlab-runner[559264]: Configuration loaded builds=0 max_builds=1
Feb 14 22:23:38 gitlab-runner[559264]: listen_address not defined, metrics & debug endpoints disabled builds=0 max_builds=1
Feb 14 22:23:38 gitlab-runner[559264]: [session_server].listen_address not defined, session endpoints disabled builds=0 max_builds=1
Feb 14 22:23:38 gitlab-runner[559264]: Initializing executor providers builds=0 max_builds=1
Feb 14 22:24:19 gitlab-runner[559264]: WARNING: Checking for jobs… failed runner=H6wkbwfD1 status=POST 409 Conflict

Additionally, here’s my runner configuration for reference (with sensitive information altered for security):

concurrent = 1
check_interval = 0
shutdown_timeout = 0

session_timeout = 1800

name = "payment_gate"
url = ""
id = 111 (changed for privacy)
token_obtained_at = 2024-02-12T19:37:53Z
token_expires_at = 0001-01-01T00:00:00Z
executor = "shell"
MaxUploadedArchiveSize = 0

I’m facing a 409 Conflict error when the runner tries to check for jobs. This started occurring after I attempted to utilize SSH connections within my script. I believe this may be related to the missing logs issue or could be a separate problem altogether.

Could anyone please help me understand what’s causing these issues and how I can resolve them? Any assistance or insights would be greatly appreciated.