BerriAI/litellm · error · HTTPException
Failed to list access groups: {e}
Error message
Failed to list access groups: {e} What it means
Catch-all around the access-group listing: any exception from get_all_access_groups_from_db or the response build (e.g. DB connectivity failures mid-query) is logged and re-raised as this 500. HTTPExceptions pass through unchanged.
Source
Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:514
raise HTTPException(
status_code=500,
detail={"error": "Database not connected."},
)
try:
access_groups_map: Final = await get_all_access_groups_from_db(prisma_client=prisma_client)
# Sort by access group name
access_groups_list: Final = sorted(
access_groups_map.values(),
key=lambda x: x.access_group,
)
return ListAccessGroupsResponse(access_groups=access_groups_list)
except Exception as e:
verbose_proxy_logger.exception("Error listing access groups: %s", e)
raise HTTPException(
status_code=500,
detail={"error": f"Failed to list access groups: {e}"},
)
@router.get(
"/access_group/{access_group}/info",
tags=["model management"],
dependencies=[Depends(user_api_key_auth)],
response_model=AccessGroupInfo,
)
async def get_access_group_info(
access_group: str,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
"""
Get information about a specific access group.
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy server logs for the underlying exception details.
- Verify database connectivity.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:514 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/9aa661cd02945999.
Report an issue: GitHub.