You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If SELinux is enabled and its mode is set to enforcing, the controller should
have failed to start. A look at /var/log/messages should reveal the following
error:
The command sudo audit2allow -w -a can be used to translates the SELinux audit
messages into a description of why the access was denied.
The current solution is to enable the boolean allow_execmem. This solution is
probably too permissive and should ideally be more restrictive, for example by
targetting a single Java program.
sudo setsebool -P allow_execmem 1getsebool -a | grep allow_execmem # should be "on"
Restart the container (docker restart unifi-controller) and then check its logs
to check that the controller has successfully started (docker logs unifi-controller).
The text was updated successfully, but these errors were encountered:
If SELinux is enabled and its mode is set to
enforcing
, the controller shouldhave failed to start. A look at
/var/log/messages
should reveal the followingerror:
The command
sudo audit2allow -w -a
can be used to translates the SELinux auditmessages into a description of why the access was denied.
The current solution is to enable the boolean
allow_execmem
. This solution isprobably too permissive and should ideally be more restrictive, for example by
targetting a single Java program.
Restart the container (
docker restart unifi-controller
) and then check its logsto check that the controller has successfully started (
docker logs unifi-controller
).The text was updated successfully, but these errors were encountered: