starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #442] What does this mean in my logs? #264

New issue
Closed
opened 2026-03-03 01:27:23 +03:00 by kerem · 5 comments
kerem commented 2026-03-03 01:27:23 +03:00
Owner
Copy link

Originally created by @BobWs on GitHub (Mar 25, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/442

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). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/442 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
kerem closed this issue 2026-03-03 01:27:23 +03:00
kerem commented 2026-03-03 01:27:24 +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.

<!-- gh-comment-id:476184061 --> @BlackDex commented on GitHub (Mar 25, 2019): Seems you are running a "debug" version instead of the "release" version. It's just normal output.
kerem commented 2026-03-03 01:27:24 +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"

<!-- gh-comment-id:476193213 --> @BobWs commented on GitHub (Mar 25, 2019): That is strange I'm using the latest image "mprasil/bitwarden:latest"
kerem commented 2026-03-03 01:27:24 +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.

<!-- gh-comment-id:476197451 --> @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.
kerem commented 2026-03-03 01:27:24 +03:00
Author
Owner
Copy link

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

okay thanks for explaining

<!-- gh-comment-id:476198454 --> @BobWs commented on GitHub (Mar 25, 2019): okay thanks for explaining
kerem commented 2026-03-03 01:27:24 +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.

<!-- gh-comment-id:476201905 --> @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
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
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 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
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#264
No description provided.