Hi,
May I suggest attaching strace to your systemd unit?
[Service]
ExecStart=/usr/bin/strace -o /tmp/strace -vvfftt -e trace=%process -s
5000 /usr/sbin/uwsgi --ini /opt/ae-dir/etc/uwsgi/web2ldap.ini
With something similar to this you should be able to see in
/tmp/strace what and how / where is e
On 8/8/18 6:41 PM, Damjan Georgievski wrote:
but without either the uwsgi
.ini file or the systemd service file it's hard to tell what you're
seeing
See below.
Ciao, Michael.
#---
# uwsgi config for web2ldap service
# Ans
On 8 August 2018 at 16:17, Michael Ströder wrote:
> HI!
>
> I'm using uwsgi for starting WSGI Python apps.
>
> uwsgi itself is started with a systemd unit which also mandates that an
> AppArmor profile is load for that unit.
>
> Although I'm using pretty tight AppAmor profiles everything works.
>
On 8/8/18 4:23 PM, Riccardo Magliocchetti wrote:
Il 08/08/2018 16:17, Michael Ströder ha scritto:
HI!
I'm using uwsgi for starting WSGI Python apps.
uwsgi itself is started with a systemd unit which also mandates that
an AppArmor profile is load for that unit.
Although I'm using pretty tigh
Il 08/08/2018 16:17, Michael Ströder ha scritto:
HI!
I'm using uwsgi for starting WSGI Python apps.
uwsgi itself is started with a systemd unit which also mandates that an AppArmor
profile is load for that unit.
Although I'm using pretty tight AppAmor profiles everything works.
Now I'd like
HI!
I'm using uwsgi for starting WSGI Python apps.
uwsgi itself is started with a systemd unit which also mandates that an
AppArmor profile is load for that unit.
Although I'm using pretty tight AppAmor profiles everything works.
Now I'd like to minimize the (false-positive?) messages AppArm
