search

getzep / zep

Zep | The Memory Foundation For Your AI Stack
https://help.getzep.com/ce
Apache License 2.0
2.7k stars 384 forks source link

ERROR: zep_python.exceptions.APIError: API error: {'status_code': 502, 'message': ''} #136

Closed jkgdz closed 1 year ago

jkgdz commented 1 year ago

Hello, I'm not very good at English. If possible, please help me

This is my detailed error message：

File "d:\360MoveData\Users\Administrator\Desktop\bot\memory.py", line 119, in <module>
memory.chat_memory.add_message(
File "D:\ana\envs\pbot\lib\site-packages\langchain\memory\chat_message_histories\zep.py", line 168, in add_message
self.zep_client.add_memory(self.session_id, zep_memory)
File "D:\ana\envs\pbot\lib\site-packages\zep_python\zep_client.py", line 400, in add_memory
self._handle_response(response)
File "D:\ana\envs\pbot\lib\site-packages\zep_python\zep_client.py", line 111, in _handle_response
raise APIError(response)
zep_python.exceptions.APIError: API error: {'status_code': 502, 'message': ''}

This is my code, almost copied from the zepmemory in Python. langchain:

from langchain.memory import ZepMemory
from langchain.retrievers import ZepRetriever
from langchain import OpenAI
from langchain.schema import HumanMessage, AIMessage
from langchain.utilities import WikipediaAPIWrapper
from langchain.agents import initialize_agent, AgentType, Tool
from uuid import uuid4

ZEP_API_URL =  "http://localhost:8000"
ZEP_API_KEY = "gzTpR0Ace87a6Z-0KMmhlzfMtjsSkQXyjfSdIUFjgKN5cNBLaeOZW1Nq5O6lQ_TNzFh3wKRa6I_NksHEKtloYA"

session_id = str(uuid4())  

import getpass

openai_key = "sk-***************************************"

zep_api_key = ZEP_API_KEY

search = WikipediaAPIWrapper()
tools = [
    Tool(
        name="Search",
        func=search.run,
        description="useful for when you need to search online for answers. You should ask targeted questions",
    ),
]

memory = ZepMemory(
    session_id=session_id,
    url=ZEP_API_URL,
    api_key=zep_api_key,
    memory_key="chat_history",
)

llm = OpenAI(temperature=0, openai_api_key=openai_key)
agent_chain = initialize_agent(
    tools,
    llm,
    agent=AgentType.CONVERSATIONAL_REACT_DESCRIPTION,
    verbose=True,
    memory=memory,
)

test_history = [
    {"role": "human", "content": "Who was Octavia Butler?"},
    {
        "role": "ai",
        "content": (
            "Octavia Estelle Butler (June 22, 1947 – February 24, 2006) was an American"
            " science fiction author."
        ),
    },
    {"role": "human", "content": "Which books of hers were made into movies?"},
    {
        "role": "ai",
        "content": (
            "The most well-known adaptation of Octavia Butler's work is the FX series"
            " Kindred, based on her novel of the same name."
        ),
    },
    {"role": "human", "content": "Who were her contemporaries?"},
    {
        "role": "ai",
        "content": (
            "Octavia Butler's contemporaries included Ursula K. Le Guin, Samuel R."
            " Delany, and Joanna Russ."
        ),
    },
    {"role": "human", "content": "What awards did she win?"},
    {
        "role": "ai",
        "content": (
            "Octavia Butler won the Hugo Award, the Nebula Award, and the MacArthur"
            " Fellowship."
        ),
    },
    {
        "role": "human",
        "content": "Which other women sci-fi writers might I want to read?",
    },
    {
        "role": "ai",
        "content": "You might want to read Ursula K. Le Guin or Joanna Russ.",
    },
    {
        "role": "human",
        "content": (
            "Write a short synopsis of Butler's book, Parable of the Sower. What is it"
            " about?"
        ),
    },
    {
        "role": "ai",
        "content": (
            "Parable of the Sower is a science fiction novel by Octavia Butler,"
            " published in 1993. It follows the story of Lauren Olamina, a young woman"
            " living in a dystopian future where society has collapsed due to"
            " environmental disasters, poverty, and violence."
        ),
        "metadata": {"foo": "bar"},
    },
]

for msg in test_history:
    memory.chat_memory.add_message(
        HumanMessage(content=msg["content"])
        if msg["role"] == "human"
        else AIMessage(content=msg["content"]),
        metadata=msg.get("metadata", {}),
    )

agent_chain.run(
    input="What is the book's relevance to the challenges facing contemporary society?",
)

The server uses Docker self deployment, and the ports are all default. Zep: 8000:8000, zep npl: 8080:8080, zep postgres: 5432:5432,

The server is running normally without any errors, and can browse 127.0.0.1:8080 normally. Using telnet, it is possible to ping ports 8080 and 8000 normally

If you need any more information, please let me know. I would be happy to provide it. Thank you. I am not very proficient in English, and all English is translated through translation software. If there is any offense, I sorry

danielchalef commented 1 year ago

I'm able to run your code as-is. I noticed that your JWT token (the ZEP_API_KEY) is not a valid base64-encoded token value. JWT tokens all start with the characters ey. It's possible you're using your API secret as your token. Please would you carefully review the the authentication guide below, in particular Step 3, in order to ensure you've correctly set this up?

https://docs.getzep.com/deployment/auth/

Some additional things to check:

jkgdz commented 1 year ago

Thank you for answering my question. I rechecked the version number and found no problem, but "3 Create a JWT Token for client access ", unfortunately, I am using Windows. In the zep-0.8.1 directory, whether using dotnet build or msbuild build, it shows that the project file does not exist. If possible, please help me

danielchalef commented 1 year ago

You’ll need to install go if you’d like to compile Zep: https://go.dev/doc/install

Alternatively, you can generate a JWT token using the jwt.io website:

https://jwt.io/

The algorithm should be HS256 and the payload an empty {}.

Note that you’ll be pasting your secret into a form on the website. I don’t believe the form submits to the site backend and the site is run by a reputable company. Nevertheless, you should be aware that this there is a risk to doing this.

jkgdz commented 1 year ago

You’ll need to install go if you’d like to compile Zep: https://go.dev/doc/install

Alternatively, you can generate a JWT token using the jwt.io website:

https://jwt.io/

The algorithm should be HS256 and the payload an empty {}.

Note that you’ll be pasting your secret into a form on the website. I don’t believe the form submits to the site backend and the site is run by a reputable company. Nevertheless, you should be aware that this there is a risk to doing this.

Thank you for helping me so much, I cleared PAYLOAD:DATA, the generated JWT token into the ZEP_API_KEY, still the error I described above, nothing has changed, I plan to learn programming first and then use it, thank you for your help

danielchalef commented 1 year ago

Would you please share the Zep logs? Thanks

jkgdz commented 1 year ago

Would you please share the Zep logs? Thanks Of course, I would be happy to. Here is the log file information I found on Docker

Firstly, zep's logs：

2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=warning msg=".env file not found or unable to load. This warning can be ignored if Zep is run using docker compose with env_file defined or you are passing ENV variables."
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Log level set to: info"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Starting zep server version 0.8.1-c204bed (2023-07-14T07:50:34+0000)"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Using memory store: postgres"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Starting purge delete processor. Purging every 1h0m0s"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Initializing extractors"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="SummaryExtractor attached to memory store"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="EmbeddingExtractor attached to memory store"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="TokenCountExtractor attached to memory store"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="EntityExtractor attached to memory store"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="IntentExtractor attached to memory store"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="JWT authentication required"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="Listening on: :8000"
2023-07-25 14:22:51 time="2023-07-25T06:22:51Z" level=info msg="completed purging memory store"

Next is the logs of zep-nlp：

2023-07-21 17:23:20 INFO:     Started server process [1]
2023-07-21 17:23:20 INFO:     Waiting for application startup.
2023-07-21 17:23:20 INFO:     Application startup complete.
2023-07-21 17:23:20 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-21 17:34:25 INFO:     Shutting down
2023-07-21 17:34:25 INFO:     Waiting for application shutdown.
2023-07-21 17:34:25 INFO:     Application shutdown complete.
2023-07-21 17:34:25 INFO:     Finished server process [1]
2023-07-22 15:11:32 INFO:     Started server process [1]
2023-07-22 15:11:32 INFO:     Waiting for application startup.
2023-07-22 15:11:32 INFO:     Application startup complete.
2023-07-22 15:11:32 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-22 17:45:25 INFO:     Shutting down
2023-07-22 17:45:25 INFO:     Waiting for application shutdown.
2023-07-22 17:45:25 INFO:     Application shutdown complete.
2023-07-22 17:45:25 INFO:     Finished server process [1]
2023-07-22 17:50:21 INFO:     Started server process [1]
2023-07-22 17:50:21 INFO:     Waiting for application startup.
2023-07-22 17:50:21 INFO:     Application startup complete.
2023-07-22 17:50:21 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-23 08:21:27 INFO:     Shutting down
2023-07-23 08:21:27 INFO:     Waiting for application shutdown.
2023-07-23 08:21:27 INFO:     Application shutdown complete.
2023-07-23 08:21:27 INFO:     Finished server process [1]
2023-07-24 10:09:35 INFO:     Started server process [1]
2023-07-24 10:09:35 INFO:     Waiting for application startup.
2023-07-24 10:09:35 INFO:     Application startup complete.
2023-07-24 10:09:35 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-24 10:34:03 WARNING:  Invalid HTTP request received.
2023-07-24 14:19:07 WARNING:  Invalid HTTP request received.
2023-07-24 14:22:42 INFO:     Shutting down
2023-07-24 14:22:42 INFO:     Waiting for application shutdown.
2023-07-24 14:22:42 INFO:     Application shutdown complete.
2023-07-24 14:22:42 INFO:     Finished server process [1]
2023-07-24 14:23:34 INFO:     Started server process [1]
2023-07-24 14:23:34 INFO:     Waiting for application startup.
2023-07-24 14:23:34 INFO:     Application startup complete.
2023-07-24 14:23:34 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-24 14:31:32 INFO:     Shutting down
2023-07-24 14:31:32 INFO:     Waiting for application shutdown.
2023-07-24 14:31:32 INFO:     Application shutdown complete.
2023-07-24 14:31:32 INFO:     Finished server process [1]
2023-07-24 14:31:38 INFO:     Started server process [1]
2023-07-24 14:31:38 INFO:     Waiting for application startup.
2023-07-24 14:31:38 INFO:     Application startup complete.
2023-07-24 14:31:38 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-24 17:45:15 INFO:     Shutting down
2023-07-24 17:45:15 INFO:     Waiting for application shutdown.
2023-07-24 17:45:15 INFO:     Application shutdown complete.
2023-07-24 17:45:15 INFO:     Finished server process [1]
2023-07-25 08:27:42 INFO:     Started server process [1]
2023-07-25 08:27:42 INFO:     Waiting for application startup.
2023-07-25 08:27:42 INFO:     Application startup complete.
2023-07-25 08:27:42 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-25 09:45:28 INFO:     Shutting down
2023-07-25 09:45:28 INFO:     Waiting for application shutdown.
2023-07-25 09:45:28 INFO:     Application shutdown complete.
2023-07-25 09:45:28 INFO:     Finished server process [1]
2023-07-25 10:03:01 INFO:     Started server process [1]
2023-07-25 10:03:01 INFO:     Waiting for application startup.
2023-07-25 10:03:01 INFO:     Application startup complete.
2023-07-25 10:03:01 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-25 14:19:17 INFO:     Shutting down
2023-07-25 14:19:17 INFO:     Waiting for application shutdown.
2023-07-25 14:19:17 INFO:     Application shutdown complete.
2023-07-25 14:19:17 INFO:     Finished server process [1]
2023-07-25 14:22:43 INFO:     Started server process [1]
2023-07-25 14:22:43 INFO:     Waiting for application startup.
2023-07-25 14:22:43 INFO:     Application startup complete.
2023-07-25 14:22:43 INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)
2023-07-25 14:50:59 INFO:     Shutting down
2023-07-25 14:50:59 INFO:     Waiting for application shutdown.
2023-07-25 14:50:59 INFO:     Application shutdown complete.
2023-07-25 14:50:59 INFO:     Finished server process [1]
2023-07-22 16:39:53 INFO:     172.18.0.1:45264 - "GET / HTTP/1.1" 307 Temporary Redirect
2023-07-22 16:39:53 INFO:     172.18.0.1:45264 - "GET /docs HTTP/1.1" 200 OK
2023-07-22 16:40:03 INFO:     172.18.0.1:51106 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-22 16:40:51 INFO:     172.18.0.1:51252 - "GET /healthz HTTP/1.1" 200 OK
2023-07-22 16:40:55 INFO:     172.18.0.1:51266 - "GET /healthz HTTP/1.1" 200 OK
2023-07-22 16:41:03 INFO:     172.18.0.1:55932 - "GET /healthz HTTP/1.1" 200 OK
2023-07-22 16:41:04 INFO:     172.18.0.1:55932 - "GET /healthz HTTP/1.1" 200 OK
2023-07-22 16:42:03 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:03 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:03 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:42:04 INFO:     172.18.0.4:47712 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 16:57:40 INFO:     172.18.0.4:56770 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:01 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:06 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:02:06 INFO:     172.18.0.4:60404 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:06 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:09 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:03:09 INFO:     172.18.0.4:58916 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:33 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:34 INFO:     172.18.0.4:32938 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:39 INFO:     172.18.0.4:49528 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:07:39 INFO:     172.18.0.4:49528 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:00 INFO:     172.18.0.4:54846 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:06 INFO:     172.18.0.4:54856 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:08:06 INFO:     172.18.0.4:54856 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:24 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:27 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:25:27 INFO:     172.18.0.4:59968 - "POST /entities HTTP/1.1" 200 OK
2023-07-22 17:36:48 INFO:     172.18.0.1:33544 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-22 18:06:27 INFO:     172.18.0.1:47342 - "GET / HTTP/1.1" 307 Temporary Redirect
2023-07-22 18:06:27 INFO:     172.18.0.1:47342 - "GET /docs HTTP/1.1" 200 OK
2023-07-22 18:06:27 INFO:     172.18.0.1:47342 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-22 18:06:30 INFO:     172.18.0.1:47350 - "GET /docs HTTP/1.1" 200 OK
2023-07-22 18:06:30 INFO:     172.18.0.1:47350 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-24 10:10:55 INFO:     172.18.0.1:55888 - "GET / HTTP/1.1" 307 Temporary Redirect
2023-07-24 10:10:55 INFO:     172.18.0.1:55888 - "GET /docs HTTP/1.1" 200 OK
2023-07-24 10:10:56 INFO:     172.18.0.1:55888 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-24 10:11:22 INFO:     172.18.0.1:57640 - "POST /api/v1/sessions/1400cfea-cd4e-4a90-8694-008864c71404/memory HTTP/1.1" 404 Not Found
2023-07-24 10:12:42 INFO:     172.18.0.1:36658 - "POST /api/v1/sessions/c7a3ffdf-cd9e-4031-8e8f-e748241fe551/memory HTTP/1.1" 404 Not Found
2023-07-24 10:15:20 INFO:     172.18.0.1:35192 - "POST /api/v1/sessions/7024ec46-ae26-4968-8855-4fec9edc75a1/memory HTTP/1.1" 404 Not Found
2023-07-24 10:22:40 INFO:     172.18.0.1:38210 - "GET / HTTP/1.1" 307 Temporary Redirect
2023-07-24 10:22:40 INFO:     172.18.0.1:38210 - "GET /docs HTTP/1.1" 200 OK
2023-07-24 10:22:40 INFO:     172.18.0.1:38210 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-24 10:24:56 INFO:     172.18.0.1:49656 - "POST /api/v1/sessions/763f01ea-57d5-4e00-aac2-9775cbfedfcb/memory HTTP/1.1" 404 Not Found
2023-07-24 10:36:06 INFO:     172.18.0.1:45346 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-24 10:39:00 INFO:     172.18.0.1:50144 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-25 08:48:48 INFO:     172.18.0.1:35480 - "GET / HTTP/1.1" 307 Temporary Redirect
2023-07-25 08:48:48 INFO:     172.18.0.1:35480 - "GET /docs HTTP/1.1" 200 OK
2023-07-25 08:48:50 INFO:     172.18.0.1:35480 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-25 09:08:03 INFO:     172.18.0.1:56698 - "GET /openapi.json HTTP/1.1" 200 OK
2023-07-25 09:42:15 INFO:     172.18.0.1:54904 - "GET /openapi.json HTTP/1.1" 200 OK

Next is the logs of zep postgres

2023-07-21 17:23:08 The files belonging to this database system will be owned by user "postgres".
2023-07-21 17:23:08 This user must also own the server process.
2023-07-21 17:23:08 
2023-07-21 17:23:08 The database cluster will be initialized with locale "en_US.utf8".
2023-07-21 17:23:08 The default database encoding has accordingly been set to "UTF8".
2023-07-21 17:23:08 The default text search configuration will be set to "english".
2023-07-21 17:23:08 
2023-07-21 17:23:08 Data page checksums are disabled.
2023-07-21 17:23:08 
2023-07-21 17:23:08 fixing permissions on existing directory /var/lib/postgresql/data ... ok
2023-07-21 17:23:08 creating subdirectories ... ok
2023-07-21 17:23:08 selecting dynamic shared memory implementation ... posix
2023-07-21 17:23:08 selecting default max_connections ... 100
2023-07-21 17:23:08 selecting default shared_buffers ... 128MB
2023-07-21 17:23:08 selecting default time zone ... Etc/UTC
2023-07-21 17:23:08 creating configuration files ... ok
2023-07-21 17:23:09 initdb: warning: enabling "trust" authentication for local connections
2023-07-21 17:23:09 initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
2023-07-21 17:23:09 2023-07-21 09:23:09.684 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-21 17:23:09 2023-07-21 09:23:09.685 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-21 17:23:09 2023-07-21 09:23:09.685 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-21 17:23:09 2023-07-21 09:23:09.691 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-21 17:23:09 2023-07-21 09:23:09.698 UTC [63] LOG:  database system was shut down at 2023-07-21 09:23:09 UTC
2023-07-21 17:23:09 2023-07-21 09:23:09.708 UTC [1] LOG:  database system is ready to accept connections
2023-07-21 17:28:09 2023-07-21 09:28:09.798 UTC [61] LOG:  checkpoint starting: time
2023-07-21 17:28:30 2023-07-21 09:28:30.583 UTC [61] LOG:  checkpoint complete: wrote 210 buffers (1.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=20.753 s, sync=0.022 s, total=20.785 s; sync files=102, longest=0.008 s, average=0.001 s; distance=1002 kB, estimate=1002 kB
2023-07-21 17:34:25 2023-07-21 09:34:25.129 UTC [1] LOG:  received fast shutdown request
2023-07-21 17:34:25 2023-07-21 09:34:25.138 UTC [1] LOG:  aborting any active transactions
2023-07-21 17:34:25 2023-07-21 09:34:25.141 UTC [1] LOG:  background worker "logical replication launcher" (PID 66) exited with exit code 1
2023-07-21 17:34:25 2023-07-21 09:34:25.143 UTC [61] LOG:  shutting down
2023-07-21 17:34:25 2023-07-21 09:34:25.146 UTC [61] LOG:  checkpoint starting: shutdown immediate
2023-07-21 17:34:25 2023-07-21 09:34:25.337 UTC [61] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.194 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=902 kB
2023-07-21 17:34:25 2023-07-21 09:34:25.345 UTC [1] LOG:  database system is shut down
2023-07-22 15:11:26 2023-07-22 07:11:26.796 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-22 15:11:26 2023-07-22 07:11:26.797 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-22 15:11:26 2023-07-22 07:11:26.797 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-22 15:11:26 2023-07-22 07:11:26.802 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-22 15:11:26 2023-07-22 07:11:26.809 UTC [29] LOG:  database system was shut down at 2023-07-21 09:34:25 UTC
2023-07-22 15:11:26 2023-07-22 07:11:26.825 UTC [1] LOG:  database system is ready to accept connections
2023-07-22 15:11:37 2023-07-22 07:11:37.400 UTC [47] ERROR:  relation "session_session_id_idx" already exists
2023-07-22 15:11:37 2023-07-22 07:11:37.400 UTC [47] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-22 15:11:37 2023-07-22 07:11:37.402 UTC [47] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-22 15:11:37 2023-07-22 07:11:37.402 UTC [47] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-22 15:11:37 2023-07-22 07:11:37.403 UTC [47] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-22 15:11:37 2023-07-22 07:11:37.403 UTC [47] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-22 15:11:37 2023-07-22 07:11:37.404 UTC [47] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-22 15:11:37 2023-07-22 07:11:37.404 UTC [47] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-22 15:16:26 2023-07-22 07:16:26.830 UTC [27] LOG:  checkpoint starting: time
2023-07-22 15:16:27 2023-07-22 07:16:27.361 UTC [27] LOG:  checkpoint complete: wrote 8 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.505 s, sync=0.011 s, total=0.531 s; sync files=5, longest=0.009 s, average=0.003 s; distance=0 kB, estimate=0 kB
2023-07-22 16:46:27 2023-07-22 08:46:27.537 UTC [27] LOG:  checkpoint starting: time
2023-07-22 16:46:29 2023-07-22 08:46:29.670 UTC [27] LOG:  checkpoint complete: wrote 22 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.107 s, sync=0.006 s, total=2.134 s; sync files=14, longest=0.002 s, average=0.001 s; distance=32 kB, estimate=32 kB
2023-07-22 17:01:27 2023-07-22 09:01:27.882 UTC [27] LOG:  checkpoint starting: time
2023-07-22 17:01:29 2023-07-22 09:01:29.610 UTC [27] LOG:  checkpoint complete: wrote 18 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.706 s, sync=0.013 s, total=1.729 s; sync files=14, longest=0.009 s, average=0.001 s; distance=57 kB, estimate=57 kB
2023-07-22 17:06:27 2023-07-22 09:06:27.636 UTC [27] LOG:  checkpoint starting: time
2023-07-22 17:06:33 2023-07-22 09:06:33.085 UTC [27] LOG:  checkpoint complete: wrote 55 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=5.415 s, sync=0.008 s, total=5.450 s; sync files=30, longest=0.002 s, average=0.001 s; distance=199 kB, estimate=199 kB
2023-07-22 17:11:27 2023-07-22 09:11:27.126 UTC [27] LOG:  checkpoint starting: time
2023-07-22 17:11:31 2023-07-22 09:11:31.881 UTC [27] LOG:  checkpoint complete: wrote 48 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.713 s, sync=0.027 s, total=4.755 s; sync files=30, longest=0.015 s, average=0.001 s; distance=201 kB, estimate=201 kB
2023-07-22 17:16:27 2023-07-22 09:16:27.920 UTC [27] LOG:  checkpoint starting: time
2023-07-22 17:16:28 2023-07-22 09:16:28.238 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.301 s, sync=0.002 s, total=0.319 s; sync files=2, longest=0.002 s, average=0.001 s; distance=12 kB, estimate=182 kB
2023-07-22 17:26:27 2023-07-22 09:26:27.402 UTC [27] LOG:  checkpoint starting: time
2023-07-22 17:26:31 2023-07-22 09:26:31.134 UTC [27] LOG:  checkpoint complete: wrote 38 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=3.711 s, sync=0.007 s, total=3.732 s; sync files=24, longest=0.002 s, average=0.001 s; distance=125 kB, estimate=176 kB
2023-07-22 17:45:25 2023-07-22 09:45:25.716 UTC [1] LOG:  received fast shutdown request
2023-07-22 17:45:25 2023-07-22 09:45:25.720 UTC [1] LOG:  aborting any active transactions
2023-07-22 17:45:25 2023-07-22 09:45:25.722 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-07-22 17:45:25 2023-07-22 09:45:25.725 UTC [27] LOG:  shutting down
2023-07-22 17:45:25 2023-07-22 09:45:25.728 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-07-22 17:45:25 2023-07-22 09:45:25.736 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.012 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=159 kB
2023-07-22 17:45:25 2023-07-22 09:45:25.742 UTC [1] LOG:  database system is shut down
2023-07-22 17:50:15 2023-07-22 09:50:15.812 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-22 17:50:15 2023-07-22 09:50:15.812 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-22 17:50:15 2023-07-22 09:50:15.813 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-22 17:50:15 2023-07-22 09:50:15.817 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-22 17:50:15 2023-07-22 09:50:15.825 UTC [28] LOG:  database system was shut down at 2023-07-22 09:45:25 UTC
2023-07-22 17:50:15 2023-07-22 09:50:15.842 UTC [1] LOG:  database system is ready to accept connections
2023-07-22 17:50:27 2023-07-22 09:50:27.526 UTC [46] ERROR:  relation "session_session_id_idx" already exists
2023-07-22 17:50:27 2023-07-22 09:50:27.526 UTC [46] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-22 17:50:27 2023-07-22 09:50:27.528 UTC [46] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-22 17:50:27 2023-07-22 09:50:27.528 UTC [46] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-22 17:50:27 2023-07-22 09:50:27.529 UTC [46] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-22 17:50:27 2023-07-22 09:50:27.529 UTC [46] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-22 17:50:27 2023-07-22 09:50:27.530 UTC [46] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-22 17:50:27 2023-07-22 09:50:27.530 UTC [46] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-22 17:55:15 2023-07-22 09:55:15.879 UTC [26] LOG:  checkpoint starting: time
2023-07-22 17:55:16 2023-07-22 09:55:16.008 UTC [26] LOG:  checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.106 s, sync=0.010 s, total=0.129 s; sync files=3, longest=0.008 s, average=0.004 s; distance=0 kB, estimate=0 kB
2023-07-23 08:21:27 2023-07-23 00:21:27.486 UTC [1] LOG:  received fast shutdown request
2023-07-23 08:21:27 2023-07-23 00:21:27.491 UTC [1] LOG:  aborting any active transactions
2023-07-23 08:21:27 2023-07-23 00:21:27.492 UTC [1] LOG:  background worker "logical replication launcher" (PID 31) exited with exit code 1
2023-07-23 08:21:27 2023-07-23 00:21:27.493 UTC [26] LOG:  shutting down
2023-07-23 08:21:27 2023-07-23 00:21:27.496 UTC [26] LOG:  checkpoint starting: shutdown immediate
2023-07-23 08:21:27 2023-07-23 00:21:27.520 UTC [26] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.027 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-23 08:21:27 2023-07-23 00:21:27.524 UTC [1] LOG:  database system is shut down
2023-07-24 10:09:31 2023-07-24 02:09:31.614 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-24 10:09:31 2023-07-24 02:09:31.614 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-24 10:09:31 2023-07-24 02:09:31.614 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-24 10:09:31 2023-07-24 02:09:31.620 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-24 10:09:31 2023-07-24 02:09:31.627 UTC [29] LOG:  database system was shut down at 2023-07-23 00:21:27 UTC
2023-07-24 10:09:31 2023-07-24 02:09:31.633 UTC [1] LOG:  database system is ready to accept connections
2023-07-24 10:09:42 2023-07-24 02:09:42.338 UTC [47] ERROR:  relation "session_session_id_idx" already exists
2023-07-24 10:09:42 2023-07-24 02:09:42.338 UTC [47] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-24 10:09:42 2023-07-24 02:09:42.339 UTC [47] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-24 10:09:42 2023-07-24 02:09:42.339 UTC [47] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-24 10:09:42 2023-07-24 02:09:42.339 UTC [47] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-24 10:09:42 2023-07-24 02:09:42.339 UTC [47] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-21 17:23:08 running bootstrap script ... ok
2023-07-21 17:23:09 performing post-bootstrap initialization ... ok
2023-07-21 17:23:09 syncing data to disk ... ok
2023-07-21 17:23:09 
2023-07-21 17:23:09 
2023-07-21 17:23:09 Success. You can now start the database server using:
2023-07-21 17:23:09 
2023-07-21 17:23:09     pg_ctl -D /var/lib/postgresql/data -l logfile start
2023-07-21 17:23:09 
2023-07-21 17:23:09 waiting for server to start....2023-07-21 09:23:09.392 UTC [49] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-21 17:23:09 2023-07-21 09:23:09.395 UTC [49] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-21 17:23:09 2023-07-21 09:23:09.402 UTC [52] LOG:  database system was shut down at 2023-07-21 09:23:09 UTC
2023-07-21 17:23:09 2023-07-21 09:23:09.408 UTC [49] LOG:  database system is ready to accept connections
2023-07-21 17:23:09  done
2023-07-21 17:23:09 server started
2023-07-21 17:23:09 
2023-07-21 17:23:09 /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2023-07-21 17:23:09 
2023-07-21 17:23:09 2023-07-21 09:23:09.558 UTC [49] LOG:  received fast shutdown request
2023-07-21 17:23:09 waiting for server to shut down....2023-07-21 09:23:09.561 UTC [49] LOG:  aborting any active transactions
2023-07-21 17:23:09 2023-07-21 09:23:09.563 UTC [49] LOG:  background worker "logical replication launcher" (PID 55) exited with exit code 1
2023-07-21 17:23:09 2023-07-21 09:23:09.564 UTC [50] LOG:  shutting down
2023-07-21 17:23:09 2023-07-21 09:23:09.566 UTC [50] LOG:  checkpoint starting: shutdown immediate
2023-07-21 17:23:09 2023-07-21 09:23:09.582 UTC [50] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.007 s, sync=0.002 s, total=0.018 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-21 17:23:09 2023-07-21 09:23:09.586 UTC [49] LOG:  database system is shut down
2023-07-21 17:23:09  done
2023-07-21 17:23:09 server stopped
2023-07-21 17:23:09 
2023-07-21 17:23:09 PostgreSQL init process complete; ready for start up.
2023-07-21 17:23:09 
2023-07-22 15:11:26 
2023-07-22 15:11:26 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-22 15:11:26 
2023-07-22 17:50:15 
2023-07-22 17:50:15 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-22 17:50:15 
2023-07-24 10:09:31 
2023-07-24 10:09:31 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-24 10:09:31 
2023-07-24 14:23:31 
2023-07-24 14:23:31 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-24 14:23:31 
2023-07-24 10:09:42 2023-07-24 02:09:42.340 UTC [47] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-24 10:09:42 2023-07-24 02:09:42.340 UTC [47] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-24 10:14:31 2023-07-24 02:14:31.726 UTC [27] LOG:  checkpoint starting: time
2023-07-24 10:14:31 2023-07-24 02:14:31.752 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.010 s, sync=0.002 s, total=0.026 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-24 10:58:38 2023-07-24 02:58:38.385 UTC [4182] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.387 UTC [4183] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.390 UTC [4184] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.391 UTC [4185] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.395 UTC [4186] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.896 UTC [4188] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.901 UTC [4189] LOG:  invalid length of startup packet
2023-07-24 10:58:38 2023-07-24 02:58:38.907 UTC [4190] LOG:  invalid length of startup packet
2023-07-24 10:58:39 2023-07-24 02:58:39.968 UTC [4191] LOG:  invalid length of startup packet
2023-07-24 10:58:39 2023-07-24 02:58:39.971 UTC [4192] LOG:  invalid length of startup packet
2023-07-24 10:58:39 2023-07-24 02:58:39.975 UTC [4193] LOG:  invalid length of startup packet
2023-07-24 10:58:40 2023-07-24 02:58:40.431 UTC [4194] LOG:  invalid length of startup packet
2023-07-24 10:58:40 2023-07-24 02:58:40.435 UTC [4195] LOG:  invalid length of startup packet
2023-07-24 10:58:40 2023-07-24 02:58:40.438 UTC [4196] LOG:  invalid length of startup packet
2023-07-24 14:22:42 2023-07-24 06:22:42.860 UTC [1] LOG:  received fast shutdown request
2023-07-24 14:22:42 2023-07-24 06:22:42.867 UTC [1] LOG:  aborting any active transactions
2023-07-24 14:22:42 2023-07-24 06:22:42.869 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-07-24 14:22:42 2023-07-24 06:22:42.869 UTC [27] LOG:  shutting down
2023-07-24 14:22:42 2023-07-24 06:22:42.874 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-07-24 14:22:42 2023-07-24 06:22:42.890 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.022 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-24 14:22:42 2023-07-24 06:22:42.896 UTC [1] LOG:  database system is shut down
2023-07-24 14:23:31 2023-07-24 06:23:31.160 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-24 14:23:31 2023-07-24 06:23:31.161 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-24 14:23:31 2023-07-24 06:23:31.162 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-24 14:23:31 2023-07-24 06:23:31.169 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-24 14:23:31 2023-07-24 06:23:31.178 UTC [29] LOG:  database system was shut down at 2023-07-24 06:22:42 UTC
2023-07-24 14:23:31 2023-07-24 06:23:31.185 UTC [1] LOG:  database system is ready to accept connections
2023-07-24 14:23:41 2023-07-24 06:23:41.907 UTC [47] ERROR:  relation "session_session_id_idx" already exists
2023-07-24 14:23:41 2023-07-24 06:23:41.907 UTC [47] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-24 14:23:41 2023-07-24 06:23:41.908 UTC [47] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-24 14:23:41 2023-07-24 06:23:41.908 UTC [47] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-24 14:23:41 2023-07-24 06:23:41.909 UTC [47] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-24 14:23:41 2023-07-24 06:23:41.909 UTC [47] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-24 14:23:41 2023-07-24 06:23:41.910 UTC [47] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-24 14:23:41 2023-07-24 06:23:41.910 UTC [47] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-24 14:28:31 2023-07-24 06:28:31.230 UTC [27] LOG:  checkpoint starting: time
2023-07-24 14:28:31 2023-07-24 06:28:31.245 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.002 s, total=0.018 s; sync files=2, longest=0.002 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-24 14:31:31 2023-07-24 06:31:31.986 UTC [1] LOG:  received fast shutdown request
2023-07-24 14:31:31 2023-07-24 06:31:31.989 UTC [1] LOG:  aborting any active transactions
2023-07-24 14:31:31 2023-07-24 06:31:31.991 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-07-24 14:31:31 2023-07-24 06:31:31.991 UTC [27] LOG:  shutting down
2023-07-24 14:31:31 2023-07-24 06:31:31.994 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-07-24 14:31:32 2023-07-24 06:31:32.006 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.015 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-24 14:31:35 
2023-07-24 14:31:35 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-24 14:31:35 
2023-07-24 14:31:32 2023-07-24 06:31:32.010 UTC [1] LOG:  database system is shut down
2023-07-24 14:31:35 2023-07-24 06:31:35.358 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-24 14:31:35 2023-07-24 06:31:35.358 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-24 14:31:35 2023-07-24 06:31:35.358 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-24 14:31:35 2023-07-24 06:31:35.362 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-24 14:31:35 2023-07-24 06:31:35.370 UTC [28] LOG:  database system was shut down at 2023-07-24 06:31:32 UTC
2023-07-24 14:31:35 2023-07-24 06:31:35.383 UTC [1] LOG:  database system is ready to accept connections
2023-07-24 14:31:46 2023-07-24 06:31:46.057 UTC [46] ERROR:  relation "session_session_id_idx" already exists
2023-07-24 14:31:46 2023-07-24 06:31:46.057 UTC [46] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-24 14:31:46 2023-07-24 06:31:46.058 UTC [46] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-24 14:31:46 2023-07-24 06:31:46.058 UTC [46] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-24 14:31:46 2023-07-24 06:31:46.059 UTC [46] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-24 14:31:46 2023-07-24 06:31:46.059 UTC [46] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-24 14:31:46 2023-07-24 06:31:46.060 UTC [46] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-24 14:31:46 2023-07-24 06:31:46.060 UTC [46] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-24 14:36:35 2023-07-24 06:36:35.465 UTC [26] LOG:  checkpoint starting: time
2023-07-24 14:36:35 2023-07-24 06:36:35.484 UTC [26] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.020 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-24 17:45:15 2023-07-24 09:45:15.598 UTC [1] LOG:  received fast shutdown request
2023-07-24 17:45:15 2023-07-24 09:45:15.604 UTC [1] LOG:  aborting any active transactions
2023-07-24 17:45:15 2023-07-24 09:45:15.605 UTC [1] LOG:  background worker "logical replication launcher" (PID 31) exited with exit code 1
2023-07-24 17:45:15 2023-07-24 09:45:15.606 UTC [26] LOG:  shutting down
2023-07-24 17:45:15 2023-07-24 09:45:15.610 UTC [26] LOG:  checkpoint starting: shutdown immediate
2023-07-24 17:45:15 2023-07-24 09:45:15.623 UTC [26] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.017 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-24 17:45:15 2023-07-24 09:45:15.627 UTC [1] LOG:  database system is shut down
2023-07-25 08:27:39 2023-07-25 00:27:39.122 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-25 08:27:39 2023-07-25 00:27:39.123 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-25 08:27:39 2023-07-25 00:27:39.123 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-25 08:27:39 2023-07-25 00:27:39.128 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-25 08:27:39 2023-07-25 00:27:39.136 UTC [29] LOG:  database system was shut down at 2023-07-24 09:45:15 UTC
2023-07-25 08:27:39 2023-07-25 00:27:39.144 UTC [1] LOG:  database system is ready to accept connections
2023-07-25 08:27:49 2023-07-25 00:27:49.819 UTC [47] ERROR:  relation "session_session_id_idx" already exists
2023-07-25 08:27:49 2023-07-25 00:27:49.819 UTC [47] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-25 08:27:49 2023-07-25 00:27:49.820 UTC [47] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-25 08:27:49 2023-07-25 00:27:49.820 UTC [47] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-25 08:27:49 2023-07-25 00:27:49.822 UTC [47] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-25 08:27:49 2023-07-25 00:27:49.822 UTC [47] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-25 08:27:49 2023-07-25 00:27:49.823 UTC [47] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-25 08:27:49 2023-07-25 00:27:49.823 UTC [47] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-25 08:32:39 2023-07-25 00:32:39.236 UTC [27] LOG:  checkpoint starting: time
2023-07-25 08:32:39 2023-07-25 00:32:39.256 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.021 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-25 08:45:37 2023-07-25 00:45:37.665 UTC [1546] LOG:  could not send data to client: Broken pipe
2023-07-25 08:45:37 2023-07-25 00:45:37.668 UTC [1546] FATAL:  connection to client lost
2023-07-25 09:45:28 2023-07-25 01:45:28.053 UTC [1] LOG:  received fast shutdown request
2023-07-25 08:27:39 
2023-07-25 08:27:39 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-25 08:27:39 
2023-07-25 10:02:56 
2023-07-25 10:02:56 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-25 10:02:56 
2023-07-25 14:22:40 
2023-07-25 14:22:40 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-25 14:22:40 
2023-07-25 09:45:28 2023-07-25 01:45:28.063 UTC [1] LOG:  aborting any active transactions
2023-07-25 09:45:28 2023-07-25 01:45:28.065 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-07-25 09:45:28 2023-07-25 01:45:28.065 UTC [27] LOG:  shutting down
2023-07-25 09:45:28 2023-07-25 01:45:28.071 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-07-25 09:45:28 2023-07-25 01:45:28.093 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.028 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-25 09:45:28 2023-07-25 01:45:28.099 UTC [1] LOG:  database system is shut down
2023-07-25 10:02:56 2023-07-25 02:02:56.952 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-25 10:02:56 2023-07-25 02:02:56.952 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-25 10:02:56 2023-07-25 02:02:56.952 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-25 10:02:56 2023-07-25 02:02:56.958 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-25 10:02:56 2023-07-25 02:02:56.966 UTC [30] LOG:  database system was shut down at 2023-07-25 01:45:28 UTC
2023-07-25 10:02:56 2023-07-25 02:02:56.972 UTC [1] LOG:  database system is ready to accept connections
2023-07-25 10:03:07 2023-07-25 02:03:07.582 UTC [48] ERROR:  relation "session_session_id_idx" already exists
2023-07-25 10:03:07 2023-07-25 02:03:07.582 UTC [48] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-25 10:03:07 2023-07-25 02:03:07.584 UTC [48] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-25 10:03:07 2023-07-25 02:03:07.584 UTC [48] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-25 10:03:07 2023-07-25 02:03:07.585 UTC [48] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-25 10:03:07 2023-07-25 02:03:07.585 UTC [48] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-25 10:03:07 2023-07-25 02:03:07.586 UTC [48] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-25 10:03:07 2023-07-25 02:03:07.586 UTC [48] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-25 10:07:56 2023-07-25 02:07:56.990 UTC [28] LOG:  checkpoint starting: time
2023-07-25 10:07:57 2023-07-25 02:07:57.009 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.020 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-25 14:19:17 2023-07-25 06:19:17.369 UTC [1] LOG:  received fast shutdown request
2023-07-25 14:19:17 2023-07-25 06:19:17.374 UTC [1] LOG:  aborting any active transactions
2023-07-25 14:19:17 2023-07-25 06:19:17.375 UTC [1] LOG:  background worker "logical replication launcher" (PID 33) exited with exit code 1
2023-07-25 14:19:17 2023-07-25 06:19:17.377 UTC [28] LOG:  shutting down
2023-07-25 14:19:17 2023-07-25 06:19:17.381 UTC [28] LOG:  checkpoint starting: shutdown immediate
2023-07-25 14:19:17 2023-07-25 06:19:17.398 UTC [28] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.022 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-25 14:19:17 2023-07-25 06:19:17.403 UTC [1] LOG:  database system is shut down
2023-07-25 14:22:41 2023-07-25 06:22:41.031 UTC [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-25 14:22:41 2023-07-25 06:22:41.031 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-25 14:22:41 2023-07-25 06:22:41.031 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-07-25 14:22:41 2023-07-25 06:22:41.037 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-25 14:22:41 2023-07-25 06:22:41.045 UTC [29] LOG:  database system was shut down at 2023-07-25 06:19:17 UTC
2023-07-25 14:22:41 2023-07-25 06:22:41.052 UTC [1] LOG:  database system is ready to accept connections
2023-07-25 14:22:51 2023-07-25 06:22:51.191 UTC [47] ERROR:  relation "session_session_id_idx" already exists
2023-07-25 14:22:51 2023-07-25 06:22:51.191 UTC [47] STATEMENT:  CREATE INDEX "session_session_id_idx" ON "session" ("session_id")
2023-07-25 14:22:51 2023-07-25 06:22:51.192 UTC [47] ERROR:  relation "memstore_session_id_idx" already exists
2023-07-25 14:22:51 2023-07-25 06:22:51.192 UTC [47] STATEMENT:  CREATE INDEX "memstore_session_id_idx" ON "message" ("session_id")
2023-07-25 14:22:51 2023-07-25 06:22:51.193 UTC [47] ERROR:  relation "sumstore_session_id_idx" already exists
2023-07-25 14:22:51 2023-07-25 06:22:51.193 UTC [47] STATEMENT:  CREATE INDEX "sumstore_session_id_idx" ON "summary" ("session_id")
2023-07-25 14:22:51 2023-07-25 06:22:51.194 UTC [47] ERROR:  relation "mem_vec_store_session_id_idx" already exists
2023-07-25 14:22:51 2023-07-25 06:22:51.194 UTC [47] STATEMENT:  CREATE INDEX "mem_vec_store_session_id_idx" ON "message_embedding" ("session_id")
2023-07-25 14:27:41 2023-07-25 06:27:41.147 UTC [27] LOG:  checkpoint starting: time
2023-07-25 14:27:41 2023-07-25 06:27:41.167 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.021 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-07-25 14:50:59 2023-07-25 06:50:59.279 UTC [1] LOG:  received fast shutdown request
2023-07-25 14:50:59 2023-07-25 06:50:59.282 UTC [1] LOG:  aborting any active transactions
2023-07-25 14:50:59 2023-07-25 06:50:59.284 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2023-07-25 14:50:59 2023-07-25 06:50:59.285 UTC [27] LOG:  shutting down
2023-07-25 14:50:59 2023-07-25 06:50:59.287 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-07-25 14:50:59 2023-07-25 06:50:59.295 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.011 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB
2023-07-25 14:50:59 2023-07-25 06:50:59.300 UTC [1] LOG:  database system is shut down

I would be happy to add any areas that may have been missed 0v0

danielchalef commented 1 year ago

I don't see client requests in the Zep logs. Can you confirm that you've using the correct URL and port when you configure the Zep client?

You should see entries similar to this in your Zep logs if there are successful requests:

INFO[2023-07-25T20:23:30-07:00] https://YOURHOST:8000/api/v1/XXXX       bytes=283 category=router duration=5853083 duration_display=5.853291ms method=GET proto=HTTP/1.1 remote_ip=127.0.0.1 status_code=200
jkgdz commented 1 year ago

I don't see client requests in the Zep logs. Can you confirm that you've using the correct URL and port when you configure the Zep client?

You should see entries similar to this in your Zep logs if there are successful requests:

INFO[2023-07-25T20:23:30-07:00] https://YOURHOST:8000/api/v1/XXXX       bytes=283 category=router duration=5853083 duration_display=5.853291ms method=GET proto=HTTP/1.1 remote_ip=127.0.0.1 status_code=200

I'm using zep deployed by docker, the default url is "http://localhost:8000", and I also tried "http://localhost:8080", but again nothing happens, and there is no record of link failure even on the server side

danielchalef commented 1 year ago

Do you have any other services running on your PC that may be listening on port 8000? My guess is that something else is intercepting requests to Zep.

danielchalef commented 1 year ago

@jkgdz Would you please update the zep-python client to v0.34? This new version includes a test to determine whether the client can successfully connect to the Zep server.

jkgdz commented 1 year ago

Okay, I'm sorry I haven't seen any response messages from Github in the past few days. I think it might be possible, but I've tried using telnet to verify ports 8000 and 8080, and I've tried to open them on the webpage, and they can all be accessed normally

jkgdz commented 1 year ago

It seems useless. My code uses langchain code, and there is no call to zep-python in the code. However, thank you for being willing to help me 0v0

danielchalef commented 1 year ago

@jkgdz The Langchain ZepMemory and ZepRetriever classes call the Zep Python SDK. Please reopen this issue if you have the opportunity to upgrade the Zep Python package and still need assistance.