From ffe15dffc09b31e47eca04a32aee6a9878f4f57f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Jaenisch?= Date: Wed, 8 Mar 2023 15:48:32 +0100 Subject: [PATCH] Rename file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: André Jaenisch --- v1.19/admin/seek-assistance.md | 49 ++++++++++++++++++++++++++++++++++ v1.19/admin/seek-help.md | 47 -------------------------------- 2 files changed, 49 insertions(+), 47 deletions(-) create mode 100644 v1.19/admin/seek-assistance.md delete mode 100644 v1.19/admin/seek-help.md diff --git a/v1.19/admin/seek-assistance.md b/v1.19/admin/seek-assistance.md new file mode 100644 index 00000000..228b4638 --- /dev/null +++ b/v1.19/admin/seek-assistance.md @@ -0,0 +1,49 @@ +--- +layout: '~/layouts/Markdown.astro' +title: 'Getting Support' +license: 'Apache-2.0' +origin_url: 'https://github.com/go-gitea/gitea/blob/699f20234b9f7cdbbeeee3be004470c598fa1147/docs/content/doc/help/seek-help.en-us.md' +--- + +- [Chatroom](https://matrix.to/#/#forgejo-chat:matrix.org) +- [Issue tracker](https://codeberg.org/forgejo/forgejo/issues) + +**NOTE:** When asking for support, it may be a good idea to have the following available so that the person helping has all the info they need: + +1. Your `app.ini` (with any sensitive data scrubbed as necessary). +2. The Forgejo logs, and any other appropriate log files for the situation. + + - When using systemd, use `journalctl --lines 1000 --unit forgejo` to collect logs. + - When using docker, use `docker logs --tail 1000 ` to collect logs. + - By default, the logs are outputted to console. If you need to collect logs from files, + you could copy the following config into your `app.ini` (remove all other `[log]` sections), + then you can find the `*.log` files in Forgejo's log directory (default: `%(FORGEJO_WORK_DIR)/log`). + + ```ini + ; To show all SQL logs, you can also set LOG_SQL=true in the [database] section + [log] + LEVEL=debug + MODE=console,file + ROUTER=console,file + XORM=console,file + ENABLE_XORM_LOG=true + FILE_NAME=gitea.log + [log.file.router] + FILE_NAME=router.log + [log.file.xorm] + FILE_NAME=xorm.log + ``` + +3. Any error messages you are seeing. +4. If you meet slow/hanging/deadlock problems, please report the stack trace when the problem occurs: + + 1. Enable pprof in `app.ini` and restart Forgejo + + ```ini + [server] + ENABLE_PPROF = true + ``` + + 2. Trigger the bug, when Forgejo gets stuck, use curl or browser to visit: `http://127.0.0.1:6060/debug/pprof/goroutine?debug=1` (IP must be `127.0.0.1` and port must be `6060`). + 3. If you are using Docker, please use `docker exec -it curl "http://127.0.0.1:6060/debug/pprof/goroutine?debug=1"`. + 4. Report the output (the stack trace doesn't contain sensitive data) diff --git a/v1.19/admin/seek-help.md b/v1.19/admin/seek-help.md deleted file mode 100644 index a882628f..00000000 --- a/v1.19/admin/seek-help.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -layout: '~/layouts/Markdown.astro' -title: 'Getting Support' -license: 'Apache-2.0' -origin_url: 'https://github.com/go-gitea/gitea/blob/699f20234b9f7cdbbeeee3be004470c598fa1147/docs/content/doc/help/seek-help.en-us.md' ---- - -- [Chatroom](https://matrix.to/#/#forgejo-chat:matrix.org) -- [Issue tracker](https://codeberg.org/forgejo/forgejo/issues) - -**NOTE:** When asking for support, it may be a good idea to have the following available so that the person helping has all the info they need: - -1. Your `app.ini` (with any sensitive data scrubbed as necessary). -2. The Forgejo logs, and any other appropriate log files for the situation. - - When using systemd, use `journalctl --lines 1000 --unit forgejo` to collect logs. - - When using docker, use `docker logs --tail 1000 ` to collect logs. - - By default, the logs are outputted to console. If you need to collect logs from files, - you could copy the following config into your `app.ini` (remove all other `[log]` sections), - then you can find the `*.log` files in Forgejo's log directory (default: `%(FORGEJO_WORK_DIR)/log`). - - ```ini - ; To show all SQL logs, you can also set LOG_SQL=true in the [database] section - [log] - LEVEL=debug - MODE=console,file - ROUTER=console,file - XORM=console,file - ENABLE_XORM_LOG=true - FILE_NAME=gitea.log - [log.file.router] - FILE_NAME=router.log - [log.file.xorm] - FILE_NAME=xorm.log - ``` - -3. Any error messages you are seeing. -4. If you meet slow/hanging/deadlock problems, please report the stack trace when the problem occurs: - 1. Enable pprof in `app.ini` and restart Forgejo - - ```ini - [server] - ENABLE_PPROF = true - ``` - - 2. Trigger the bug, when Forgejo gets stuck, use curl or browser to visit: `http://127.0.0.1:6060/debug/pprof/goroutine?debug=1` (IP must be `127.0.0.1` and port must be `6060`). - 3. If you are using Docker, please use `docker exec -it curl "http://127.0.0.1:6060/debug/pprof/goroutine?debug=1"`. - 4. Report the output (the stack trace doesn't contain sensitive data)