Console logger keeps logging after changing default logger #199

New Issue

GiteaMirror · 2025-11-02T03:13:39-06:00

GiteaMirror commented

2025-11-02 03:13:39 -06:00

Originally created by @willemvd on GitHub (Jan 4, 2017).

Gitea version (or commit ref): 1.0.0 (6aacf4d)

When setting the default logger to something else then "console", it will still log to console on Trace level.

Failing configuration:
[log]
MODE = file
LEVEL = Info
ROOT_PATH = /var/log/gitea

Seems that changing the default logger will not remove the existing console logger that is attached in the settings.go init()

Workaround which at least limits the console logging:
[log]
MODE = console, file
LEVEL = Info
ROOT_PATH = /var/folders/5c/s85y9_014bd95y0x1wzr1vjm0000gn/T/log

[log.console]
LEVEL = Critical

Originally created by @willemvd on GitHub (Jan 4, 2017). Gitea version (or commit ref): 1.0.0 (6aacf4d) When setting the default logger to something else then "console", it will still log to console on Trace level. Failing configuration: [log] MODE = file LEVEL = Info ROOT_PATH = /var/log/gitea Seems that changing the default logger will not remove the existing console logger that is attached in the settings.go init() Workaround which at least limits the console logging: [log] MODE = console, file LEVEL = Info ROOT_PATH = /var/folders/5c/s85y9_014bd95y0x1wzr1vjm0000gn/T/log [log.console] LEVEL = Critical

GiteaMirror added the type/bug label 2025-11-02 03:13:39 -06:00

GiteaMirror closed this issue

2025-11-02 03:13:39 -06:00

GiteaMirror commented

2025-11-02 03:13:40 -06:00

@lunny commented on GitHub (Jan 26, 2017):

closed by #602

@lunny commented on GitHub (Jan 26, 2017): closed by #602

GiteaMirror referenced this issue

2025-11-02 11:41:35 -06:00

[PR #199] [MERGED] Added sorting to the labels & milestones page #15218

GiteaMirror referenced this issue