bogdan54

Problems wint SearXNG

Jan 2nd, 2023
264
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.39 KB | None | 0 0
  1. Starting searxng ... done
  2. Starting caddy ... done
  3. Starting redis ... done
  4. Attaching to caddy, searxng, redis
  5. caddy | {"level":"info","ts":1672693414.9038935,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"caddyfile"}
  6. caddy | {"level":"warn","ts":1672693414.9159214,"logger":"caddyfile","msg":"Unnecessary header_up X-Forwarded-Proto: the reverse proxy's default behavior is to pass headers to the upstream"}
  7. caddy | {"level":"warn","ts":1672693414.919997,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":2}
  8. caddy | {"level":"warn","ts":1672693414.923307,"logger":"admin","msg":"admin endpoint disabled"}
  9. caddy | {"level":"info","ts":1672693414.9236903,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
  10. caddy | {"level":"info","ts":1672693414.9237292,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
  11. caddy | {"level":"info","ts":1672693414.928622,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0003f1260"}
  12. caddy | {"level":"info","ts":1672693414.9294813,"logger":"http","msg":"enabling HTTP/3 listener","addr":":443"}
  13. caddy | {"level":"info","ts":1672693414.9319785,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
  14. caddy | {"level":"info","ts":1672693414.932342,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
  15. caddy | {"level":"info","ts":1672693414.9325,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc0003f1260"}
  16. caddy | Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: address already in use
  17. caddy exited with code 1
  18. redis | 1:C 02 Jan 2023 21:03:35.908 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
  19. redis | 1:C 02 Jan 2023 21:03:35.912 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
  20. redis | 1:C 02 Jan 2023 21:03:35.912 # Configuration loaded
  21. redis | 1:M 02 Jan 2023 21:03:35.914 * monotonic clock: POSIX clock_gettime
  22. redis | 1:M 02 Jan 2023 21:03:35.919 * Running mode=standalone, port=6379.
  23. redis | 1:M 02 Jan 2023 21:03:35.920 # Server initialized
  24. redis | 1:M 02 Jan 2023 21:03:35.920 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
  25. redis | 1:M 02 Jan 2023 21:03:35.924 * Ready to accept connections
  26. searxng | SearXNG version 2022.12.30-647a0aa9
  27. searxng | Use existing /etc/searxng/uwsgi.ini
  28. searxng | Use existing /etc/searxng/settings.yml
  29. searxng | Listen on 0.0.0.0:8080
  30. searxng | [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
  31. searxng | [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
  32. searxng | *** Starting uWSGI 2.0.21 (64bit) on [Mon Jan 2 21:03:36 2023] ***
  33. searxng | compiled with version: 12.2.1 20220924 on 09 November 2022 12:47:28
  34. searxng | os: Linux-5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020
  35. searxng | nodename: bde4ac712fe7
  36. searxng | machine: x86_64
  37. searxng | clock source: unix
  38. searxng | pcre jit disabled
  39. searxng | detected number of CPU cores: 1
  40. searxng | current working directory: /usr/local/searxng
  41. searxng | detected binary path: /usr/sbin/uwsgi
  42. searxng | chdir() to /usr/local/searxng/searx/
  43. searxng | your memory page size is 4096 bytes
  44. searxng | detected max file descriptor number: 1048576
  45. searxng | building mime-types dictionary from file /etc/mime.types...1323 entry found
  46. searxng | lock engine: pthread robust mutexes
  47. searxng | thunder lock: disabled (you can enable it with --thunder-lock)
  48. searxng | *** Cache "searxngcache" initialized: 11MB (key: 2136 bytes, keys: 4272000 bytes, data: 8192000 bytes, bitmap: 250 bytes) preallocated ***
  49. searxng | uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 4
  50. searxng | Python version: 3.10.9 (main, Dec 12 2022, 17:52:15) [GCC 12.2.1 20220924]
  51. searxng | Python main interpreter initialized at 0x7f1db8beeb50
  52. searxng | python threads support enabled
  53. searxng | your server socket listen backlog is limited to 100 connections
  54. searxng | your mercy for graceful operations on workers is 60 seconds
  55. searxng | mapped 241344 bytes (235 KB) for 4 cores
  56. searxng | *** Operational MODE: threaded ***
  57. searxng | added /usr/local/searxng/ to pythonpath.
  58. searxng | spawned uWSGI master process (pid: 7)
  59. searxng | spawned uWSGI worker 1 (pid: 10, cores: 4)
  60. searxng | cache sweeper thread enabled
  61. searxng | spawned 1 offload threads for uWSGI worker 1
  62. searxng | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7f1db8beeb50 pid: 10 (default app)
Add Comment
Please, Sign In to add comment