Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Starting SearXNG with systemd: Unexpected error when forwarding signal #81

Open
schindlershadow opened this issue Sep 1, 2022 · 3 comments
Open

Starting SearXNG with systemd: Unexpected error when forwarding signal #81

schindlershadow opened this issue Sep 1, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@schindlershadow
Copy link

When starting SearXNG with systemd I'm getting the following error:

searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 40 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 18 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 22 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 14 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 51 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 11 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 58 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 29 (default app)
searxng    | [FATAL tini (1)] Unexpected error when forwarding signal: 'Operation not permitted'
searxng exited with code 1

strangely it works fine with docker-compose up
@Gettre
Copy link

Gettre commented Oct 27, 2022

I have the same error but from docker-compose.
Installed with the whole stack from the script

@NamesCode
Copy link

When starting SearXNG with systemd I'm getting the following error:

searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 40 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 18 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 22 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 14 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 51 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 11 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 58 (default app)
searxng    | WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x7fef6cc32b50 pid: 29 (default app)
searxng    | [FATAL tini (1)] Unexpected error when forwarding signal: 'Operation not permitted'
searxng exited with code 1

strangely it works fine with docker-compose up

Same for me

@predmijat
Copy link

Same thing...on each reboot I get the [FATAL tini (1)] Unexpected error when forwarding signal: 'Operation not permitted', and then after docker-compose restart everything works. I don't see other errors.

@unixfox unixfox added the bug Something isn't working label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@unixfox @schindlershadow @predmijat @Gettre @NamesCode