Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: API /models/start does not work - weird response message #1475

Closed
2 of 6 tasks
louis-menlo opened this issue Oct 15, 2024 · 5 comments
Closed
2 of 6 tasks

bug: API /models/start does not work - weird response message #1475

louis-menlo opened this issue Oct 15, 2024 · 5 comments
Assignees
Labels
type: bug Something isn't working
Milestone

Comments

@louis-menlo
Copy link
Contributor

Cortex version

v1.0.0-168

Describe the Bug

I'm checking out the latest nightly version, started the server successfully, however, when I request /models/start, it returns a 400 error with a very peculiar message response: "om ". Please see the attached screenshot. I can run the model via CLI tho.

Steps to Reproduce

  1. Pull a model
  2. Start server
  3. Request a /models/start request, with correct model name or alias

Screenshots / Logs

35236

What is your OS?

  • MacOS
  • Windows
  • Linux

What engine are you running?

  • cortex.llamacpp (default)
  • cortex.tensorrt-llm (Nvidia GPUs)
  • cortex.onnx (NPUs, DirectML)
@louis-menlo louis-menlo added the type: bug Something isn't working label Oct 15, 2024
@github-project-automation github-project-automation bot moved this to Investigating in Menlo Oct 15, 2024
@louis-menlo
Copy link
Contributor Author

After stopping the server and restarting it, I was able to make it work, but sending the 2nd request resulted in the same issue. It might be a zombie process or something from the past. Now I received a 409 from the CLI but a 400 with this strange message from the API.

@gabrielle-ong
Copy link
Contributor

@louis-jan verifying if this is fixed for you?
from v172, its fixed for me - I'm able to send /models/start request even if the model is already loaded.
image

@louis-menlo
Copy link
Contributor Author

louis-menlo commented Oct 16, 2024

It's weird here. Checking engines
image

@louis-menlo louis-menlo reopened this Oct 16, 2024
@github-project-automation github-project-automation bot moved this from Review + QA to In Progress in Menlo Oct 16, 2024
@louis-menlo
Copy link
Contributor Author

Oh, it's another issue then; 500 when there's no engine setup. I installed the engine, but it's still 500. Restarting the server doesn't seem to work.

@github-project-automation github-project-automation bot moved this from In Progress to Review + QA in Menlo Oct 16, 2024
@gabrielle-ong
Copy link
Contributor

Since om issue not happening anymore, shall close this
500 error for engine setup is captured in #1422,
and should be handled in #1514 to bubble up this common error

@gabrielle-ong gabrielle-ong moved this from Review + QA to Completed in Menlo Oct 18, 2024
@gabrielle-ong gabrielle-ong added this to the v1.0.1 milestone Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

4 participants