starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-27 19:07:53 +03:00
Code Issues 32 Packages Projects Releases 12 Wiki Activity

What does this mean in my logs? #264

New Issue
Closed
opened 2026-02-04 19:07:47 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 19:07:47 +03:00
Owner
Copy Link

Originally created by @BobWs on GitHub (Mar 25, 2019).

What does this mean? I'm seeing it a lot in my logs:

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 1

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 1

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 0

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 0

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 4

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 4

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 2

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 2

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 3

2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 3

2019-03-25 12:23:27,stdout,[2019-03-25 12:23:27][tokio_reactor][DEBUG] dropping I/O source: 8

2019-03-25 12:23:16,stdout,[2019-03-25 12:23:16][_][INFO] Response succeeded.

2019-03-25 12:23:16,stdout,[2019-03-25 12:23:16][_][INFO] Outcome: Success

Originally created by @BobWs on GitHub (Mar 25, 2019). What does this mean? I'm seeing it a lot in my logs: > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 1 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 1 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 0 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 0 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 4 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 4 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 2 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 2 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor][DEBUG] dropping I/O source: 3 > > 2019-03-25 12:23:51,stdout,[2019-03-25 12:23:51][tokio_reactor::registration][DEBUG] scheduling Read for: 3 > > 2019-03-25 12:23:27,stdout,[2019-03-25 12:23:27][tokio_reactor][DEBUG] dropping I/O source: 8 > > 2019-03-25 12:23:16,stdout,[2019-03-25 12:23:16][_][INFO] Response succeeded. > > 2019-03-25 12:23:16,stdout,[2019-03-25 12:23:16][_][INFO] Outcome: Success
OVERLORD commented 2026-02-04 19:07:53 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 25, 2019):

Seems you are running a "debug" version instead of the "release" version.
It's just normal output.

@BlackDex commented on GitHub (Mar 25, 2019): Seems you are running a "debug" version instead of the "release" version. It's just normal output.
OVERLORD commented 2026-02-04 19:08:02 +03:00
Author
Owner
Copy Link

@BobWs commented on GitHub (Mar 25, 2019):

That is strange I'm using the latest image "mprasil/bitwarden:latest"

@BobWs commented on GitHub (Mar 25, 2019): That is strange I'm using the latest image "mprasil/bitwarden:latest"
OVERLORD commented 2026-02-04 19:08:13 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Mar 25, 2019):

That's from the reqwest library that we use for icon downloading which uses the tokio crate, we currently hardcode the log level to debug globally (except a couple of dependencies which are set to a higher value), so this is what we get. It should happen regardless of what version you are using.

We don't really use the debug log level ourselves, so I've changed it to Info by default, which makes more sense and would hide that kind of message (which isn't very useful for us anyway). I also implemented a log_level config option. This should be available in the latest commit now, and in the built images soon.

@dani-garcia commented on GitHub (Mar 25, 2019): That's from the reqwest library that we use for icon downloading which uses the tokio crate, we currently hardcode the log level to debug globally (except a couple of dependencies which are set to a higher value), so this is what we get. It should happen regardless of what version you are using. We don't really use the debug log level ourselves, so I've changed it to Info by default, which makes more sense and would hide that kind of message (which isn't very useful for us anyway). I also implemented a log_level config option. This should be available in the latest commit now, and in the built images soon.
OVERLORD commented 2026-02-04 19:08:40 +03:00
Author
Owner
Copy Link

@BobWs commented on GitHub (Mar 25, 2019):

okay thanks for explaining

@BobWs commented on GitHub (Mar 25, 2019): okay thanks for explaining
OVERLORD commented 2026-02-04 19:08:42 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Mar 25, 2019):

Images are now being built, give it about an hour to complete. I think we can close this one now? Feel free to reopen if there's anything more we can help with.

@mprasil commented on GitHub (Mar 25, 2019): Images are now being built, give it about an hour to complete. I think we can close this one now? Feel free to reopen if there's anything more we can help with.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#264
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?