Skip to main content

47 posts tagged with "MLflow"

MLflow, the Open Source Platform for Tracking, Evaluating and Serving Machine Learning Models

View All Tags

Fixed: "[Errno 48] Address already in use" When You Start the MLflow Server

· 7 min read
Jagdish Kumawat
Founder @ Dewiride

uv run mlflow server --port 8080 stopped right after it began, with ERROR: [Errno 48] Address already in use and Running the mlflow server failed: The server process exited with code 3. Another MLflow server was already listening on that port. lsof showed which one, and the new server started cleanly on a free port.

Fixed: "MlflowException: API request to … failed with exception … Max retries exceeded" Connection Refused in MLflow

· 9 min read
Jagdish Kumawat
Founder @ Dewiride

An MLflow training run printed seven urllib3 retry warnings over about four minutes, then failed with MlflowException: API request to … failed with exception … Max retries exceeded … [Errno 61] Connection refused. Nothing was listening at the tracking URI. MLflow's client retries for minutes before it gives up, which makes a missing server look like a hang. Starting the server fixed it, and MLFLOW_HTTP_REQUEST_MAX_RETRIES makes the same mistake fail in seconds.

Fixed: SADeprecationWarning "The noload loader strategy is deprecated" When You Run pytest with MLflow

· 7 min read
Jagdish Kumawat
Founder @ Dewiride

pytest passed all 12 tests of a project that logs to MLflow, then printed a warnings summary: SADeprecationWarning: The ``noload`` loader strategy is deprecated. It comes from MLflow 3.18.0's SQL tracking store meeting SQLAlchemy 2.1, and MLflow fixed it the day after 3.18.0 shipped. Until a release includes the fix, one filterwarnings line hides exactly this warning in your tests.

Fixed: "Exception ignored on threading shutdown" KeyboardInterrupt When You Stop the MLflow Server

· 9 min read
Jagdish Kumawat
Founder @ Dewiride

Pressing Ctrl+C to stop MLflow 3.18.0's tracking server printed Exception ignored on threading shutdown: and a KeyboardInterrupt traceback from Python's own threading.py. Nothing crashed: the server stopped cleanly, and the message comes from its background job runner being interrupted at exit. If you don't use MLflow's server jobs, MLFLOW_SERVER_ENABLE_JOB_EXECUTION=false makes it go away.

Fixed: "StarletteDeprecationWarning: starlette.middleware.wsgi is deprecated" When You Start the MLflow Server

· 8 min read
Jagdish Kumawat
Founder @ Dewiride

Starting MLflow 3.18.0's tracking server printed StarletteDeprecationWarning: starlette.middleware.wsgi is deprecated four times. Nothing was wrong with my setup: the warning comes from MLflow's own code meeting Starlette 1.10.0, and the server works. One PYTHONWARNINGS filter hides this warning, and only this one, until MLflow changes its code.

Fixed: "Access to localhost was denied" HTTP ERROR 403 When You Open the MLflow UI on a Mac

· 8 min read
Jagdish Kumawat
Founder @ Dewiride

On a Mac, mlflow server --port 5000 started without a single error, but opening http://localhost:5000 showed Chrome's Access to localhost was denied page with HTTP ERROR 403. MLflow never saw the request: macOS's AirPlay Receiver also listens on port 5000, and localhost reached it first. http://127.0.0.1:5000 opened the MLflow UI, and moving MLflow to port 8080 ended the clash.

Fixed: "Invalid comparator '>' not one of" When You Search MLflow Runs by a Parameter

· 7 min read
Jagdish Kumawat
Founder @ Dewiride

Filtering MLflow runs with params.n_estimators > "100" failed with Invalid comparator '>' not one of …, both in the UI's search box and in mlflow.search_runs(). MLflow stores every parameter as text, and text only takes =, !=, LIKE and ILIKE. Matching exact values works in the UI, and pandas compares the numbers in Python.