Skip to content

Info logs displayed as ERROR | stderr #1292

Open

Description

@pie3636

Currently, a lot of logs which are clearly only info-level are displayed as ERROR | stderr, which probably shouldn't be the case.
Two examples:

$ python3 -m fastchat.serve.controller
2023-05-17 10:56:57 | INFO | controller | args: Namespace(host='localhost', port=21001, dispatch_method='shortest_queue')
2023-05-17 10:56:57 | INFO | controller | Init controller
2023-05-17 10:56:57 | ERROR | stderr | INFO:     Started server process [19332]
2023-05-17 10:56:57 | ERROR | stderr | INFO:     Waiting for application startup.
2023-05-17 10:56:57 | ERROR | stderr | INFO:     Application startup complete.
2023-05-17 10:56:57 | ERROR | stderr | INFO:     Uvicorn running on http://localhost:21001 (Press CTRL+C to quit)
> python3 -m fastchat.serve.model_worker --model-name 'vicuna-13b-v1.1' --model-path /path/to/vicuna
2023-05-17 10:57:44 | INFO | model_worker | args: Namespace(host='localhost', port=21002, worker_address='http://localhost:21002', controller_address='http://localhost:21001', model_path='/path/to/vicuna', device='cuda', gpus=None, num_gpus=1, max_gpu_memory=None, load_8bit=False, cpu_offloading=False, model_name='vicuna-13b-v1.1', limit_model_concurrency=5, stream_interval=2, no_register=False)
2023-05-17 10:57:44 | INFO | model_worker | Loading the model vicuna-13b-v1.1 on worker c7ee88 ...                                                                                                         
Downloading (…)okenizer_config.json:   0%|                                                                                                                                       | 0.00/727 [00:00<?, ?B/s]
Downloading (…)okenizer_config.json: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 727/727 [00:00<00:00, 199kB/s]
2023-05-17 10:57:44 | ERROR | stderr |                                                                                                                                                                     
Downloading tokenizer.model:   0%|                                                                                                                                              | 0.00/500k [00:00<?, ?B/s]
Downloading tokenizer.model: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 500k/500k [00:00<00:00, 7.57MB/s]
2023-05-17 10:57:44 | ERROR | stderr |                                                                                                                                                                     
Downloading (…)cial_tokens_map.json:   0%|                                                                                                                                       | 0.00/411 [00:00<?, ?B/s]
Downloading (…)cial_tokens_map.json: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 411/411 [00:00<00:00, 594kB/s]      

Activity

  1. merrymercy commented on May 20, 2023

    @merrymercy
    Member

    Please help us fix them by sending pull requests

  2. henrylo1671 commented on Jun 27, 2023

    @henrylo1671

    I've got into the same problem. Are there any solutions yet?

  3. qiangtang2017 commented on Jul 13, 2023

    @qiangtang2017

    me to

  4. qiangtang2017 commented on Jul 13, 2023

    @qiangtang2017

    any solution?

  5. dinchu commented on Sep 26, 2023

    @dinchu

    is there a way to turn the logs off by passing some flag?

  6. surak commented on Oct 23, 2023

    @surak
    Collaborator

    @pie3636 , @qiangtang2017 , @henrylo1671 , you can have a look at the code where those messages are produced, and fix them. We are accepting merge requests :-)

  7. added a commit that references this issue on Mar 13, 2026
    9f5f3f9
  8. added a commit that references this issue on Mar 13, 2026
    05ec471
  9. Chessing234 commented on Jul 16, 2026

    @Chessing234

    PR #3895 maps uvicorn stderr level prefixes to the right log level (CI black format fix pushed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions