Skip to content

Nginx fails to start because of log format #3078

Closed
@Oicho

Description

@Oicho

Hi,

Using 17.8.4 and nginx fails to start.

2025-02-28 07:40:32,943 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-28 07:40:32,958 INFO exited: nginx (exit status 1; not expected)
2025-02-28 07:40:35,092 INFO spawned: 'nginx' with pid 2968
2025-02-28 07:40:35,109 INFO exited: nginx (exit status 1; not expected)
2025-02-28 07:40:38,118 INFO spawned: 'nginx' with pid 2969
2025-02-28 07:40:38,135 INFO exited: nginx (exit status 1; not expected)
2025-02-28 07:40:39,137 INFO gave up: nginx entered FATAL state, too many start retries too quickly

Looking at the nginx error logs

2025/02/28 07:39:17 [emerg] 2437#2437: unknown log format "gitlab_access" in /etc/nginx/conf.d/gitlab-registry.conf:14
2025/02/28 07:39:18 [emerg] 2609#2609: unknown log format "gitlab_access" in /etc/nginx/conf.d/gitlab-registry.conf:14
2025/02/28 07:39:20 [emerg] 2623#2623: unknown log format "gitlab_access" in /etc/nginx/conf.d/gitlab-registry.conf:14

The workaround was to remove the two access-log lines in the gitlab registry file

Btw if you want i'd gladly work on a fix for this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions