M BUZZ CRAZE NEWS
// news

uwSGI as service

By Mia Morrison

Version: Linux: Ubuntu 20.04.3 LTS uwsgi: 2.0.18-debian

I have this config "/etc/uwsgi/lemonldap.ini":

[uwsgi]
plugins = psgi
socket = 127.0.0.1:5000
psgi = /usr/share/lemonldap-ng/llng-server/llng-server.psgi
master = true
processes = 5
single-interpreter = true
uid = www-data
gid = www-data
vacuum = true
daemonize=/var/log/lemonldap-ng/lemonldap_trace.log
chown-socket = www-data:www-data
chmod-socket = 660

This config work when I use command "uwsgi --ini /etc/uwsgi/lemonldap.ini" I make service config:

[Unit] Description=LemonLdap
[Service] Environment=LLNG_DEFAULTCONFFILE=/etc/lemonldap-ng/lemonldap-ng.ini ExecStart=/usr/bin/uwsgi --ini /etc/uwsgi/lemonldap.ini KillSignal=SIGQUIT Type=forking NotifyAccess=all User=www-data Group=www-data
[Install] WantedBy=multi-user.target

I try start it, but get:

● ulemonldap.service - LemonLdap Loaded: loaded (/lib/systemd/system/ulemonldap.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2021-11-23 02:25:05 UTC; 3min 18s ago Process: 319431 ExecStart=/usr/bin/uwsgi --ini /etc/uwsgi/lemonldap.ini (code=exited, status=0/SUCCESS) Main PID: 319441 (code=exited, status=0/SUCCESS) Status: "initializing uWSGI"
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file o
r directory
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Child 319441 belongs to ulemonldap.service.
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Main process exited, code=exited, status=0/SUCCESS
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Changed running -> stop-sigterm
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Child 319442 belongs to ulemonldap.service.
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Control group is empty.
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Succeeded.
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Service will not restart (restart setting)
Nov 23 02:25:05 rproxy systemd[1]: ulemonldap.service: Changed stop-sigterm -> dead

On version "Ubuntu 20.04.1 LTS" and "uwsgi: 2.0.18-debian", almost identical service (diff only user) work without problem.

What am I doing wrong? And what does it mean: "Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory"

Reset to default

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy