Package Details: searxng-git r8494.5986629-4

Git Clone URL: https://aur.archlinux.org/searxng-git.git (read-only, click to copy)
Package Base: searxng-git
Description: A privacy-respecting, hackable metasearch engine
Upstream URL: https://searxng.github.io/searxng/
Licenses: AGPL-3.0-or-later
Conflicts: searx, searx-git
Provides: searxng
Submitter: HLFH
Maintainer: HLFH
Last Packager: HLFH
Votes: 13
Popularity: 1.57
First Submitted: 2021-09-29 10:43 (UTC)
Last Updated: 2025-03-24 13:41 (UTC)

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

vech commented on 2025-03-31 03:39 (UTC)

@HLFH thanks for the fixes I updated the package to the latest release (right now searxng-git-r8519.7b4612e-1) and it worked, maybe my issue had something to do with SEARXNG_SETTINGS_PATH or not having redis installed

HLFH commented on 2025-03-24 14:28 (UTC) (edited on 2025-03-24 14:29 (UTC) by HLFH)

@vech I cannot reproduce your bug.

Please update to the latest release searxng-git r8494.5986629-4 with pikaur -Syu.
And to update regularly this -git VCS package, please use pikaur -Syu --devel --needed.

HLFH commented on 2025-03-24 12:25 (UTC) (edited on 2025-03-24 14:26 (UTC) by HLFH)

@vech Currently looking at your error SXNGAnswerer is not implemented.

@krs @CountMurphy @stef204 The pkgver bug has been fixed, it seems their git versioning has changed.
I have added redis as a dependency: it is now required by searx.limiter.
Please update the redis password in settings.yml: 

redis:
  url: unix:///run/redis/redis.sock?password=yourpassword&db=1 # change the password value!

Please check the redis db 1 is empty.
I have set as db 1 because redis db 0 is often used (for example for the Nextcloud app).
The SEARXNG_SETTINGS_PATH is now correctly assigned in build() with export instead of local.

searxng user has been added to the redis group.

krs commented on 2025-03-23 11:03 (UTC)

In addition to the pkgver issue it now also seems like the python executable process doesn't read the SEARXNG_SETTINGS_PATH env var that is set in the build() section, because it tries to touch the actual file in /etc/searxng/settings.yml and gets a permission denied error.

If I put SEARXNG_SETTINGS_PATH="../settings.yml" in front of both of the python commands in the build() section it does read it properly but seems like there should be a better way to set that.

CountMurphy commented on 2025-03-04 23:57 (UTC)

I think I found the issue. The PKGBUILD is trying to git the package version from the git repo using 

git describe --long | sed 's/\([^-]*-g\)/r\1/;s/v//;s/-/./g'

This line currently returns nothing. You could fix that by replacing that line with:

git describe --long --always | sed 's/\([^-]*-g\)/r\1/;s/v//;s/-/./g'

but the version scheme would turn out different than it has been

CountMurphy commented on 2025-03-03 23:05 (UTC)

Same error here as @stef204

stef204 commented on 2025-03-03 12:07 (UTC) (edited on 2025-03-03 12:07 (UTC) by stef204) 

==> Starting pkgver()...
fatal: No names found, cannot describe anything.
==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version:

vech commented on 2025-02-22 20:58 (UTC) (edited on 2025-02-22 21:04 (UTC) by vech)

Hi everyone, Did anyone experience this log after updating this package?

Feb 22 16:03:15 server uwsgi[36288]: *** Operational MODE: single process ***
Feb 22 16:03:15 server uwsgi[36288]: spawned uWSGI master process (pid: 36288)
Feb 22 16:03:15 server uwsgi[36288]: spawned uWSGI worker 1 (pid: 36289, cores: 1)
Feb 22 16:03:15 server uwsgi[36288]: cache sweeper thread enabled
Feb 22 16:03:15 server uwsgi[36288]: spawned uWSGI http 1 (pid: 36291)
Feb 22 16:03:16 server uwsgi[36288]: 2025-02-22 16:03:16,838 CRITICAL:searx.answerers: answerer searx.answerers.statistics.SXNGAnswerer is not implemented
Feb 22 16:03:16 server uwsgi[36288]: Traceback (most recent call last):
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/webapp.py", line 87, in <module>
Feb 22 16:03:16 server uwsgi[36288]:     from searx.webadapter import (
Feb 22 16:03:16 server uwsgi[36288]:     ...<3 lines>...
Feb 22 16:03:16 server uwsgi[36288]:     )
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/webadapter.py", line 8, in <module>
Feb 22 16:03:16 server uwsgi[36288]:     from searx.query import RawTextQuery
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/query.py", line 12, in <module>
Feb 22 16:03:16 server uwsgi[36288]:     from searx.search import EngineRef
Feb 22 16:03:16 server uwsgi[36286]: Sat Feb 22 16:03:16 2025 - [emperor] vassal searxng.ini is ready to accept requests
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/search/__init__.py", line 15, in <module>
Feb 22 16:03:16 server uwsgi[36288]:     import searx.answerers
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/answerers/__init__.py", line 49, in <module>
Feb 22 16:03:16 server uwsgi[36288]:     STORAGE.load_builtins()
Feb 22 16:03:16 server uwsgi[36288]:     ~~~~~~~~~~~~~~~~~~~~~^^
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/answerers/_core.py", line 110, in load_builtins
Feb 22 16:03:16 server uwsgi[36288]:     self.register_by_fqn(f"searx.answerers.{f.stem}.SXNGAnswerer")
Feb 22 16:03:16 server uwsgi[36288]:     ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 22 16:03:16 server uwsgi[36288]:   File "/var/lib/searxng/.venv/lib/python3.13/site-packages/searx/answerers/_core.py", line 132, in register_by_fqn
Feb 22 16:03:16 server uwsgi[36288]:     raise ValueError(msg)
Feb 22 16:03:16 server uwsgi[36288]: ValueError: answerer searx.answerers.statistics.SXNGAnswerer is not implemented
Feb 22 16:03:16 server uwsgi[36288]: unable to load app 0 (mountpoint='') (callable not found or import error)

This happened today when I updated the package and restarted uwsgi@emperor service

schrmh commented on 2025-02-05 05:36 (UTC)

Thanks, czardien. Previously I tried what JanH described but it did not work; showing me some error on web pages after systemctl start uwsgi@searxng that I do not recall exactly — internal error or something around the lines. What you wrote down followed by systemctl start uwsgi@searxng worked then.

czardien commented on 2025-01-30 14:56 (UTC)

I did cp /etc/uwsgi/vassals/searxng.ini /etc/uwsgi/

So this package seems to be more tailored for Searxng to be managed by uWSGI in Emperor mode. Indeed, by default the uWSGI Archlinux package will look at /etc/uwsgi/ for configuration files of services, however in Emperor mode the same files will be found under /etc/uwsgi/vassals/; where this package write the searxng.ini file.

It's all laid out quite clearly in the Archwiki page: https://wiki.archlinux.org/title/UWSGI, which links back to the official uWSGI docs on the Emperor mode: https://uwsgi-docs.readthedocs.io/en/latest/Emperor.html.

So with that package you should just be able to start uWSGI in that mode without having to move the searxng.ini file around, and you should be good to go and look at localhost:8888 (unless the port's changed):

systemctl start emperor.uwsgi.socket
# Or:
systemctl start emperor.uwsgi.service

At least that's what worked for me.

1 2 3 4 5 6 .. 13 Next › Last »