You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running Debian 5.10.149-2.
followed all instructions from the readme as precisely as i could and got this error when trying to docker-compose up:
Starting redis ... done
Starting caddy ... done
Starting searxng ... done
Attaching to caddy, redis, searxng
caddy | {"level":"info","ts":1667527368.8843699,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
caddy | {"level":"warn","ts":1667527368.8925169,"logger":"caddyfile","msg":"Unnecessary header_up X-Forwarded-Proto: the reverse proxy's default behavior is to pass headers to the upstream"}
caddy | {"level":"warn","ts":1667527368.8948488,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
caddy | {"level":"warn","ts":1667527368.8954964,"logger":"admin","msg":"admin endpoint disabled"}
caddy | {"level":"warn","ts":1667527368.8956108,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
caddy | {"level":"info","ts":1667527368.9011307,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
caddy | {"level":"info","ts":1667527368.901149,"logger":"tls","msg":"finished cleaning storage units"}
caddy | {"level":"info","ts":1667527368.901227,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00026ce00"}
caddy | {"level":"info","ts":1667527368.9012327,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc00026ce00"}
caddy | Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use
redis | 1:C 04 Nov 2022 02:02:49.212 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis | 1:C 04 Nov 2022 02:02:49.216 # Redis version=7.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
redis | 1:C 04 Nov 2022 02:02:49.216 # Configuration loaded
redis | 1:M 04 Nov 2022 02:02:49.217 * monotonic clock: POSIX clock_gettime
redis | 1:M 04 Nov 2022 02:02:49.219 * Running mode=standalone, port=6379.
redis | 1:M 04 Nov 2022 02:02:49.219 # Server initialized
redis | 1:M 04 Nov 2022 02:02:49.219 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis | 1:M 04 Nov 2022 02:02:49.219 * Ready to accept connections
caddy exited with code 1
searxng | SearXNG version 2022.10.29-fc9986de
searxng | Use existing /etc/searxng/uwsgi.ini
searxng | Use existing /etc/searxng/settings.yml
searxng | Listen on 0.0.0.0:8080
searxng | [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
searxng | [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
searxng | *** Starting uWSGI 2.0.20 (64bit) on [Fri Nov 4 02:02:49 2022] ***
searxng | compiled with version: 11.2.1 20220219 on 21 December 2021 13:20:05
searxng | os: Linux-5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21)
searxng | nodename: bc0da6c4e310
searxng | machine: x86_64
searxng | clock source: unix
searxng | pcre jit disabled
searxng | detected number of CPU cores: 1
searxng | current working directory: /usr/local/searxng
searxng | detected binary path: /usr/sbin/uwsgi
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...1323 entry found
searxng | lock engine: pthread robust mutexes
searxng | thunder lock: disabled (you can enable it with --thunder-lock)
searxng | *** Cache "searxngcache" initialized: 11MB (key: 2136 bytes, keys: 4272000 bytes, data: 8192000 bytes, bitmap: 250 bytes) preallocated ***
searxng | *** Cache "searxngcache" initialized: 11MB (key: 2136 bytes, keys: 4272000 bytes, data: 8192000 bytes, bitmap: 250 bytes) preallocated ***
searxng | uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 5
searxng | Python version: 3.10.5 (main, Jul 25 2022, 15:52:08) [GCC 11.2.1 20220219]
searxng | Python main interpreter initialized at 0x7f2d5cc5ab50
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 241344 bytes (235 KB) for 4 cores
searxng | *** Operational MODE: threaded ***
searxng | added /usr/local/searxng/ to pythonpath.
searxng | spawned uWSGI master process (pid: 7)
searxng | spawned uWSGI worker 1 (pid: 10, cores: 4)
searxng | cache sweeper thread enabled
searxng | spawned 1 offload threads for uWSGI worker 1
searxng | 2022-11-04 02:02:50,147 ERROR:searx.shared: uwsgi.ini configuration error, add this line to your uwsgi.ini
searxng | cache2 = name=searxngcache,items=2000,blocks=2000,blocksize=4096,bitmap=1
searxng | 2022-11-04 02:02:50,546 ERROR:searx.shared.redis: [searxng (977)] can't connect redis DB ...
searxng | 2022-11-04 02:02:50,546 ERROR:searx.shared.redis: Error 2 connecting to unix socket: /usr/local/searxng-redis/run/redis.sock. No such file or directory.
searxng | 2022-11-04 02:02:50,547 ERROR:searx.plugins.limiter: init limiter DB failed!!!
searxng | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x7f2d5cc5ab50 pid: 10 (default app)
searxng | 2022-11-04 02:02:55,798 ERROR:searx.engines.z-library: Fail to initialize
searxng | Traceback (most recent call last):
searxng | File "/usr/lib/python3.10/site-packages/anyio/_core/_sockets.py", line 186, in connect_tcp
searxng | addr_obj = ip_address(remote_host)
searxng | File "/usr/lib/python3.10/ipaddress.py", line 54, in ip_address
searxng | raise ValueError(f'{address!r} does not appear to be an IPv4 or IPv6 address')
searxng | ValueError: 'z-lib.org' does not appear to be an IPv4 or IPv6 address
searxng |
searxng | During handling of the above exception, another exception occurred:
searxng |
searxng | Traceback (most recent call last):
searxng | File "/usr/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 101, in connect_tcp
searxng | stream: anyio.abc.ByteStream = await anyio.connect_tcp(
searxng | File "/usr/lib/python3.10/site-packages/anyio/_core/_sockets.py", line 189, in connect_tcp
searxng | gai_res = await getaddrinfo(
searxng | asyncio.exceptions.CancelledError
searxng |
searxng | During handling of the above exception, another exception occurred:
searxng |
searxng | Traceback (most recent call last):
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_exceptions.py", line 8, in map_exceptions
searxng | yield
searxng | File "/usr/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 100, in connect_tcp
searxng | with anyio.fail_after(timeout):
searxng | File "/usr/lib/python3.10/site-packages/anyio/_core/_tasks.py", line 118, in __exit__
searxng | raise TimeoutError
searxng | TimeoutError
searxng |
searxng | During handling of the above exception, another exception occurred:
searxng |
searxng | Traceback (most recent call last):
searxng | File "/usr/lib/python3.10/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
searxng | yield
searxng | File "/usr/lib/python3.10/site-packages/httpx/_transports/default.py", line 308, in handle_async_request
searxng | resp = await self._pool.handle_async_request(req)
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 253, in handle_async_request
searxng | raise exc
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 237, in handle_async_request
searxng | response = await connection.handle_async_request(request)
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_async/connection.py", line 86, in handle_async_request
searxng | raise exc
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_async/connection.py", line 63, in handle_async_request
searxng | stream = await self._connect(request)
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_async/connection.py", line 111, in _connect
searxng | stream = await self._network_backend.connect_tcp(**kwargs)
searxng | File "/usr/lib/python3.10/site-packages/httpcore/backends/auto.py", line 23, in connect_tcp
searxng | return await self._backend.connect_tcp(
searxng | File "/usr/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 99, in connect_tcp
searxng | with map_exceptions(exc_map):
searxng | File "/usr/lib/python3.10/contextlib.py", line 153, in __exit__
searxng | self.gen.throw(typ, value, traceback)
searxng | File "/usr/lib/python3.10/site-packages/httpcore/_exceptions.py", line 12, in map_exceptions
searxng | raise to_exc(exc)
searxng | httpcore.ConnectTimeout
searxng |
searxng | The above exception was the direct cause of the following exception:
searxng |
searxng | Traceback (most recent call last):
searxng | File "/usr/local/searxng/searx/search/processors/abstract.py", line 75, in initialize
searxng | self.engine.init(get_engine_from_settings(self.engine_name))
searxng | File "/usr/local/searxng/searx/engines/zlibrary.py", line 39, in init
searxng | resp = http_get('https://z-lib.org', timeout=5.0)
searxng | File "/usr/local/searxng/searx/network/__init__.py", line 165, in get
searxng | return request('get', url, **kwargs)
searxng | File "/usr/local/searxng/searx/network/__init__.py", line 96, in request
searxng | return future.result(timeout)
searxng | File "/usr/lib/python3.10/concurrent/futures/_base.py", line 446, in result
searxng | return self.__get_result()
searxng | File "/usr/lib/python3.10/concurrent/futures/_base.py", line 391, in __get_result
searxng | raise self._exception
searxng | File "/usr/local/searxng/searx/network/network.py", line 291, in request
searxng | return await self.call_client(False, method, url, **kwargs)
searxng | File "/usr/local/searxng/searx/network/network.py", line 287, in call_client
searxng | raise e
searxng | File "/usr/local/searxng/searx/network/network.py", line 272, in call_client
searxng | response = await client.request(method, url, **kwargs)
searxng | File "/usr/lib/python3.10/site-packages/httpx/_client.py", line 1513, in request
searxng | return await self.send(request, auth=auth, follow_redirects=follow_redirects)
searxng | File "/usr/lib/python3.10/site-packages/httpx/_client.py", line 1600, in send
searxng | response = await self._send_handling_auth(
searxng | File "/usr/lib/python3.10/site-packages/httpx/_client.py", line 1628, in _send_handling_auth
searxng | response = await self._send_handling_redirects(
searxng | File "/usr/lib/python3.10/site-packages/httpx/_client.py", line 1665, in _send_handling_redirects
searxng | response = await self._send_single_request(request)
searxng | File "/usr/lib/python3.10/site-packages/httpx/_client.py", line 1702, in _send_single_request
searxng | response = await transport.handle_async_request(request)
searxng | File "/usr/lib/python3.10/site-packages/httpx/_transports/default.py", line 307, in handle_async_request
searxng | with map_httpcore_exceptions():
searxng | File "/usr/lib/python3.10/contextlib.py", line 153, in __exit__
searxng | self.gen.throw(typ, value, traceback)
searxng | File "/usr/lib/python3.10/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
searxng | raise mapped_exc(message) from exc
searxng | httpx.ConnectTimeout`
i had initially tried to follow docker instructions on the docs website but it gave me its own issues.
tbh im finding this all confusing as the instructions in the repo here and on the website are different, so its hard to tell which to actually follow especially when both methods cause issues for me.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
running Debian 5.10.149-2.
followed all instructions from the readme as precisely as i could and got this error when trying to
docker-compose up
:i had initially tried to follow docker instructions on the docs website but it gave me its own issues.
tbh im finding this all confusing as the instructions in the repo here and on the website are different, so its hard to tell which to actually follow especially when both methods cause issues for me.
Beta Was this translation helpful? Give feedback.
All reactions