... | ... | @@ -744,6 +744,9 @@ another logfile, see: |
|
|
tail -f /var/log/gitlab/mailroom/current
|
|
|
```
|
|
|
|
|
|
If you see a crash, it might be worth looking for an [upstream
|
|
|
regression](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name[]=regression), also look in [omnibus-gitlab](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/?sort=updated_desc&label_name%5B%5D=regression&first_page_size=20).
|
|
|
|
|
|
### Outgoing email
|
|
|
|
|
|
Follow the [email not sent](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/smtp.md#email-not-sent) procedure. TL;DR:
|
... | ... | @@ -1567,6 +1570,9 @@ retirement, see [TPA-RFC-41](policy/tpa-rfc-41-schleuder-retirement#role-key-and |
|
|
[File]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/new
|
|
|
[search]: https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues
|
|
|
|
|
|
Upstream manages its issue queue in GitLab, naturally. You may want to
|
|
|
look for [upstream regression](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name[]=regression), also look in [omnibus-gitlab](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/?sort=updated_desc&label_name%5B%5D=regression&first_page_size=20).
|
|
|
|
|
|
### Known
|
|
|
|
|
|
* Wikis:
|
... | ... | |