No "non-startup" logs

[Draiqil]

Steps To Reproduce

1. Set up the instance
2. Define a logs path
3. Observe no logs

Expected Result

Logs

Actual Result

No logs

Screenshots or Videos

No response

Additional Context

Hello community! I hope you are all well.

My issue was originally concerning SMTP settings not working despite independent verification that the same creds entered work (via https://www.gmass.co/smtp-test), but fundamentally the reason this is such a struggle is because i have absolutely no logs. There is a good chance (virtually guaranteed) i'm simply incompetent but i've done the due dilligence i can do for this.

Despite setting a log directory, i cannot find logs anywhere (beyond startup jargon), so trying to debug the above issue has been absolute hell. I have checked:

• /bwdata
• /etc/bitwarden
• /var/log
• watching docker compose up (no information)

My logs are configured to go into /var/log/bitwarden as defined in docker-compose.yml. Most of my day has gone to this so perhaps i've tunnelvisioned and missed something super simple in the absolute struggle, or perhaps this is a bug. Hopefully i'll find out soon! Thank you in advance.

If i am missing any details, please let me know and i will provide them.

Githash Version

5db89f2-dirty

Environment Details

Archlinux ARM, bitwarden behind a nginx reverse proxy.

Database Image

mariadb:10

Issue-Link

#2480

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[cbbit]

Hi there,

This report has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[justindbaur]

@gimmehacs To be clear, when you say "no non-startup logs" you do have .log files that are viewable? It's just that they contain no information about the SMTP issue right?

[Draiqil]

@gimmehacs To be clear, when you say "no non-startup logs" you do have .log files that are viewable? It's just that they contain no information about the SMTP issue right?

I apologise for the lack of clarity, there is not even a log file for some reason in any of the above mentioned locations. The settings.env and the docker-compose.yml specify a total of 3 different log paths (for debugging purposes) and logs do not show in any of the locations.

[justindbaur]

Can you share those log paths you are configuring? Only one should be needed like in our example.

https://github.com/bitwarden/self-host/blob/2b5c24f7adbf7eaf86242e86f1530aedd3f24954/docker-unified/docker-compose.yml#L16

[justindbaur]

I'm going to close this issue since there has not been a reply if you are still encountering the issue please create a new issue and include your docker compose project redacted of any secrets you are using to encounter the issue.