Memos container stops working after some time running

[javierspn]

Describe the bug

Hi!

After some time running the container fails to respond.

1. Memos compose file:

services:

  memos:


    container_name: "${CONTAINER_NAME}"
    image: ${CONTAINER_IMAGE}

    environment:
      TZ: ${TZ}

    networks:
      - proxied

    restart: ${POLICY_RESTART}

    volumes:
      - ${MEMOS_VOLUME}

    logging:

      driver: ${LOG_TYPE}
      options:
        max-size: ${LOG_SIZE}
        max-file: ${LOG_FILES}

networks:
  proxied:
    name: proxied

2. .env file:

CONTAINER_NAME=memos
CONTAINER_IMAGE=neosmemo/memos:stable
TZ=Europe/Madrid
POLICY_RESTART=unless-stopped
MEMOS_VOLUME=/docker/data/memos/:/var/opt/memos
LOG_TYPE=json-file
LOG_SIZE=10M
LOG_FILES=3

3. The errors in the log since the container is restarted till it fails:

2025/01/23 16:58:09 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile
2025/01/23 16:58:09 INFO client error method=/memos.api.v1.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"
2025/01/23 16:58:09 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:58:10 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:58:11 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile
2025/01/23 16:58:12 INFO client error method=/memos.api.v1.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"
2025/01/23 16:58:12 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:58:12 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:58:12 INFO OK method=/memos.api.v1.MemoService/ListMemos
2025/01/23 16:58:14 INFO OK method=/memos.api.v1.IdentityProviderService/ListIdentityProviders
2025/01/23 16:58:22 INFO OK method=/memos.api.v1.AuthService/SignIn
2025/01/23 16:58:22 INFO OK method=/memos.api.v1.AuthService/GetAuthStatus
2025/01/23 16:58:22 INFO OK method=/memos.api.v1.UserService/GetUserSetting
2025/01/23 16:58:22 INFO OK method=/memos.api.v1.InboxService/ListInboxes
2025/01/23 16:58:22 INFO OK method=/memos.api.v1.MemoService/ListMemos
2025/01/23 16:58:22 ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary error="rpc error: code = Internal desc = failed to get resource: context canceled"
2025/01/23 16:58:23 INFO OK method=/memos.api.v1.MemoService/ListMemos
2025/01/23 16:58:23 INFO OK method=/memos.api.v1.ResourceService/GetResourceBinary
2025/01/23 16:59:14 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 16:59:14 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile
2025/01/23 16:59:15 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile
2025/01/23 16:59:15 INFO OK method=/memos.api.v1.AuthService/GetAuthStatus
2025/01/23 16:59:16 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:59:16 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
2025/01/23 16:59:16 INFO OK method=/memos.api.v1.UserService/GetUserSetting
2025/01/23 16:59:16 ERROR server error method=/memos.api.v1.MemoService/ListMemos error="failed to get user: interrupted (9)"
2025/01/23 16:59:16 INFO OK method=/memos.api.v1.InboxService/ListInboxes
2025/01/23 16:59:35 INFO OK method=/memos.api.v1.MemoService/ListMemos
2025/01/23 16:59:35 ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary error="rpc error: code = Internal desc = failed to get resource: context canceled"
2025/01/23 16:59:35 ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary error="failed to get user: interrupted (9)"
2025/01/23 16:59:35 ERROR server error method=/memos.api.v1.MemoService/ListMemos error="failed to get user: interrupted (9)"
2025/01/23 17:18:33 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2025/01/23 17:18:33 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 17:18:36 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2025/01/23 17:18:36 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 17:18:39 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2025/01/23 17:18:39 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 17:18:54 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2025/01/23 17:18:54 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 17:19:21 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2025/01/23 17:19:21 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
2025/01/23 17:20:36 ERROR mux server listen error error="accept tcp [::]:5230: use of closed network connection"
2025/01/23 17:20:36 ERROR failed to start echo server error="http: Server closed"
2025/01/23 17:20:36 INFO memos stopped properly

Steps to reproduce

1. Start container.
2. Wait for an hour more or less.
3. Open a browser. The web loads but it displays an empty screen.

The version of Memos you're using

0.23.0

Screenshots or additional context

No response

[RoccoSmit]

Duplicate of #3922
we were unable to replicate, making testing and patching really hard.
Users have found turning 3rd party tools that stop the container off have solved their issues #3922 (comment)