agenticSeek icon indicating copy to clipboard operation
agenticSeek copied to clipboard

BUG: frontend error

Open liuxingbo12138 opened this issue 10 months ago • 2 comments

Describe the bug I used the code in the dev branch to start the service in Windows using Docker. The startup command was "start_services.cmd full". I chose the OpenAI service.

Image

Image

Image

Image

config.ini

Image

.env

Image

start_services.cmd full Starting full deployment... Stopping containers... time="2025-06-04T15:39:58+08:00" level=warning msg="The \"HUGGINGFACE_API_KEY\" variable is not set. Defaulting to a blank string." time="2025-06-04T15:39:58+08:00" level=warning msg="The \"DSK_DEEPSEEK_API_KEY\" variable is not set. Defaulting to a blank string." time="2025-06-04T15:39:58+08:00" level=warning msg="D:\\AAA\\agenticSeek\\docker-compose.yml: the attributeversionis obsolete, it will be ignored, please remove it to avoid potential confusion" [+] Running 1/1 ✔ Container backend Started 0.2s time="2025-06-04T15:40:03+08:00" level=warning msg="The \"HUGGINGFACE_API_KEY\" variable is not set. Defaulting to a blank string." time="2025-06-04T15:40:03+08:00" level=warning msg="The \"DSK_DEEPSEEK_API_KEY\" variable is not set. Defaulting to a blank string." time="2025-06-04T15:40:03+08:00" level=warning msg="D:\\AAA\\agenticSeek\\docker-compose.yml: the attributeversionis obsolete, it will be ignored, please remove it to avoid potential confusion" [+] Running 4/4 ✔ Container redis Created 0.0s ✔ Container frontend Created 0.0s ✔ Container backend Running 0.0s ✔ Container searxng Created 0.0s Attaching to backend, frontend, redis, searxng frontend | frontend | > [email protected] start frontend | > react-scripts start frontend | searxng | SearXNG 2025.6.1+d63bdcd searxng | [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini searxng | open("./python3_plugin.so"): No such file or directory [core/utils.c line 3709] searxng | !!! UNABLE to load uWSGI plugin: ./python3_plugin.so: cannot open shared object file: No such file or directory !!! searxng | [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static searxng | *** Starting uWSGI 2.0.29 (64bit) on [Wed Jun 4 07:40:04 2025] *** searxng | compiled with version: 14.2.0 on 15 May 2025 21:45:46 searxng | os: Linux-6.6.87.1-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Mon Apr 21 17:08:54 UTC 2025 searxng | nodename: 37002fc44bae searxng | machine: x86_64 searxng | clock source: unix searxng | detected number of CPU cores: 16 searxng | current working directory: /usr/local/searxng searxng | detected binary path: /usr/local/searxng/venv/bin/uwsgi searxng | !!! no internal routing support, rebuild with pcre support !!! searxng | setgid() to 977 searxng | setuid() to 977 searxng | chdir() to /usr/local/searxng/searx/ searxng | your memory page size is 4096 bytes searxng | detected max file descriptor number: 1048576 searxng | building mime-types dictionary from file /etc/mime.types...1390 entry found searxng | lock engine: pthread robust mutexes searxng | thunder lock: disabled (you can enable it with --thunder-lock) searxng | uwsgi socket 0 bound to TCP6 address [::]:8080 fd 3 searxng | Python version: 3.13.3 (tags/v3.13.3-0-g6280bb5-dirty:6280bb5, May 29 2025, 17:11:20) [GCC 14.2.0] searxng | Python main interpreter initialized at 0x780fdcbade90 searxng | python threads support enabled searxng | your server socket listen backlog is limited to 100 connections searxng | your mercy for graceful operations on workers is 60 seconds searxng | mapped 603040 bytes (588 KB) for 16 cores searxng | *** Operational MODE: preforking+threaded *** searxng | added /usr/local/searxng/ to pythonpath. searxng | spawned uWSGI master process (pid: 1) searxng | spawned uWSGI worker 1 (pid: 21, cores: 4) searxng | spawned uWSGI worker 2 (pid: 22, cores: 4) searxng | spawned uWSGI worker 3 (pid: 24, cores: 4) searxng | spawned uWSGI worker 4 (pid: 29, cores: 4) searxng | spawned 4 offload threads for uWSGI worker 1 searxng | spawned 4 offload threads for uWSGI worker 2 searxng | spawned 4 offload threads for uWSGI worker 3 searxng | spawned 4 offload threads for uWSGI worker 4 searxng | 2025-06-04 07:40:05,449 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml searxng | 2025-06-04 07:40:05,459 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml searxng | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x780fdcbade90 pid: 22 (default app) searxng | 2025-06-04 07:40:05,460 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml searxng | 2025-06-04 07:40:05,462 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml searxng | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x780fdcbade90 pid: 21 (default app) searxng | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x780fdcbade90 pid: 24 (default app) searxng | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x780fdcbade90 pid: 29 (default app) searxng | 2025-06-04 07:40:05,640 ERROR:searx.engines.radio browser: Fail to initialize searxng | Traceback (most recent call last): searxng | File "/usr/local/searxng/searx/search/processors/abstract.py", line 73, in initialize searxng | self.engine.init(get_engine_from_settings(self.engine_name)) searxng | ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 71, in init searxng | server_list() searxng | ~~~~~~~~~~~^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 84, in server_list searxng | url = socket.gethostbyaddr(_ip)[0] searxng | ~~~~~~~~~~~~~~~~~~~~^^^^^ searxng | socket.herror: [Errno 4] No address associated with name searxng | 2025-06-04 07:40:05,640 ERROR:searx.engines.radio browser: Fail to initialize searxng | Traceback (most recent call last): searxng | File "/usr/local/searxng/searx/search/processors/abstract.py", line 73, in initialize frontend | (node:26) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option. searxng | self.engine.init(get_engine_from_settings(self.engine_name)) frontend | (Usenode --trace-deprecation ...to show where the warning was created) searxng | ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ frontend | (node:26) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option. searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 71, in init searxng | server_list() searxng | ~~~~~~~~~~~^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 84, in server_list searxng | url = socket.gethostbyaddr(_ip)[0] searxng | ~~~~~~~~~~~~~~~~~~~~^^^^^ searxng | socket.herror: [Errno 4] No address associated with name searxng | 2025-06-04 07:40:05,640 ERROR:searx.engines.radio browser: Fail to initialize searxng | Traceback (most recent call last): searxng | File "/usr/local/searxng/searx/search/processors/abstract.py", line 73, in initialize searxng | self.engine.init(get_engine_from_settings(self.engine_name)) searxng | ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 71, in init searxng | server_list() searxng | ~~~~~~~~~~~^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 84, in server_list searxng | url = socket.gethostbyaddr(_ip)[0] searxng | ~~~~~~~~~~~~~~~~~~~~^^^^^ searxng | socket.herror: [Errno 4] No address associated with name searxng | 2025-06-04 07:40:05,640 ERROR:searx.engines.radio browser: Fail to initialize searxng | Traceback (most recent call last): searxng | File "/usr/local/searxng/searx/search/processors/abstract.py", line 73, in initialize frontend | Starting the development server... searxng | self.engine.init(get_engine_from_settings(self.engine_name)) frontend | searxng | ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 71, in init searxng | server_list() searxng | ~~~~~~~~~~~^^ searxng | File "/usr/local/searxng/searx/engines/radio_browser.py", line 84, in server_list searxng | url = socket.gethostbyaddr(_ip)[0] searxng | ~~~~~~~~~~~~~~~~~~~~^^^^^ searxng | socket.herror: [Errno 4] No address associated with name backend | Warning: you are using an API provider. You data will be sent to the cloud. frontend | Compiled successfully! frontend | frontend | You can now view agentic-seek in the browser. frontend | frontend | Local: http://localhost:3000 frontend | On Your Network: http://172.18.0.3:3000 frontend | frontend | Note that the development build is not optimized. frontend | To create a production build, use npm run build. frontend | frontend | webpack compiled successfully backend | Device set to use cpu backend | INFO: Started server process [1] backend | INFO: Waiting for application startup. backend | INFO: Application startup complete. backend | INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)

liuxingbo12138 avatar Jun 04 '25 07:06 liuxingbo12138

did you install a chrome extension ? I don't understand how the first error could happen otherwise. Why is the error not happening on the second localhost:3000 screenshot ?

For the "unable to get a response error" in the second localhost screenshot, Did you wait long enough for the backend then refreshed the frontend ?

Fosowl avatar Jun 04 '25 17:06 Fosowl

did you install a chrome extension ? I don't understand how the first error could happen otherwise. Why is the error not happening on the second localhost:3000 screenshot ?

the error caused by another chrome extension, both extensions attempt to define the 'ethereum' property on the 'window' object

i waited until the uvicorn log output occurred

Image

liuxingbo12138 avatar Jun 05 '25 02:06 liuxingbo12138

but what extension did you install in your browser ? could you try to update the project, we just made AgenticSeek run fully in docker. You will have to read the readme.md again since installation instruction are a bit different

Fosowl avatar Jun 06 '25 16:06 Fosowl