Arch Linux User Repository

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

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.

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.

@HLFH Thank you, that's been the helpful hint I needed :)

For reference, I did cp /etc/uwsgi/vassals/searxng.ini /etc/uwsgi/, changed the port number in that file to :8080, and then could start it successfully with your command.

@zynex @JanH We do not provide any systemd service because it is started with uWSGI: systemctl start uwsgi@searxng. And it is all we need.

@zynex, would you mind sharing the systemd service file?

@HLFH Updated python-msgspec and searx-ng. It all works now. Although the systemd service pointed to /usr/bin/searxng-run, and had to change it to /var/lib/searxng/.venv/bin/searxng-run (might have created the systemd service myself?). The /var/lib/searxng/.venv/bin/searxng-run pointed to a python in my home folder though for some reason? But changed the first line to #!/var/lib/searxng/.venv/bin/python, then it worked :)

I know it's not a discussion here but I'll do it anyway : Thank you very much for this !!! It works great (I tested docker but it wasn't as good, specially with suspend on my computer).

@stef204 @morsmortium @liquidsky @DanSman @sen @krs @zynex @flylightning @backd00r @AlexBocken

The package has been fixed.
The requirements from requirements.txt are now perfectly matched.
searxng-git now uses a python virtual environment which is the best Arch Linux setup for python packages.

@morsmortium
thanks. I ended up using this (it uses a docker network, avoids anonymous volumes, addresses restart policy) YMMV:
sudo docker network create searxng-net
sudo docker run -d -p 8888:8080 --name searxng --network searxng-net --restart=unless-stopped -v searxng_data:/etc/searxng searxng/searxng
hopefully, we can go back to local install once the requirements can be met.