Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log level not applied from configuration #5007

Closed
2 of 7 tasks
nauevg opened this issue Jan 21, 2018 · 1 comment
Closed
2 of 7 tasks

Log level not applied from configuration #5007

nauevg opened this issue Jan 21, 2018 · 1 comment
Labels
💊 bug Something isn't working status: needs feedback Tell me more about it

Comments

@nauevg
Copy link

nauevg commented Jan 21, 2018

  • Gogs version (0.11.34.1122):
  • Git version: 2.11.0
  • Operating system: Debian GNU/Linux 9.3 (stretch)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gogs.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist (usually found in log/gogs.log):
    2018/01/22 01:19:35 [TRACE] Log Mode: File (Trace)
    2018/01/22 01:19:35 [ INFO] Gogs 0.11.34.1122
    2018/01/22 01:19:35 [ INFO] Cache Service Enabled
    2018/01/22 01:19:35 [ INFO] Session Service Enabled
    2018/01/22 01:19:35 [ WARN] Register Mail Service: Mail Service is not enabled
    2018/01/22 01:19:35 [ INFO] Git Version: 2.11.0
    2018/01/22 01:19:35 [ INFO] SQLite3 Supported
    2018/01/22 01:19:35 [ INFO] Run Mode: Production
    2018/01/22 01:19:35 [TRACE] Doing: CheckRepoStats
    2018/01/22 01:19:36 [ INFO] Listen: http://0.0.0.0:3000

Description

Hello.
I tried version from packages and from binary. And I can see "TRACE" and "INFO" level messages at logs when I set "Warn" value at section:
[log]
MODE = file
LEVEL = Warn
ROOT_PATH = /opt/gogs/log

I searched about it and found two issues (#2798 and #4478). But I do not get current status. Can I edit level value or not?
I use default app.ini file with little changes about run user and some other. No any changes in logging settings excluding level value as shown above.

@unknwon unknwon added the 💊 bug Something isn't working label Nov 26, 2018
@unknwon unknwon added this to the 0.12 milestone Nov 26, 2018
@unknwon unknwon added the status: needs feedback Tell me more about it label Nov 26, 2018
@unknwon
Copy link
Member

unknwon commented Nov 26, 2018

Hi, patch has pushed to fix this issue, it turns out to be a misuse on Gogs side.

In the meanwhile, you can do the following without upgrading:

[log.file]
LEVEL = Info

@unknwon unknwon changed the title Log level not applied from custom/conf/app.ini Log level not applied from configuration Dec 12, 2018
@unknwon unknwon closed this as completed Dec 12, 2018
richmahn referenced this issue in unfoldingWord/dcs Feb 4, 2019
Current docs demonstrate how to configure a database container but don't
explicitly specify that you should add additional environment variables
to the Gitea container to make it use the database. This just
demonstrates the changes required.

Signed-off-by: Dane Elwell <dane.elwell@ukfast.co.uk>
@unknwon unknwon removed this from the 0.13 milestone Nov 26, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💊 bug Something isn't working status: needs feedback Tell me more about it
Projects
None yet
Development

No branches or pull requests

2 participants