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
As I compiled source with no-root user,
could you tell me why /apps/opt/icingadir2/lib64/icinga2/sbin/icinga2 is required to run as root?
I asked because for sure my SA (System Administrator) will ask.
The text was updated successfully, but these errors were encountered:
Icinga 2 isn't built for custom environments which don't require root permissions. There's an ongoing discussion about changing this in #4947. Don't expect it to happen any time soon as our officially supported packages work just fine. I'm closing this as duplicate.
Expected Behavior
I expect to enable feature without being root user.
Current Behavior
When I'm logged with non-root user "icinga" for example, I perform following command and I got message error:
Possible Solution
The solution that worked for me is to allow icinga to sudo the binary command /apps/opt/icingadir2/lib64/icinga2/sbin/icinga2
and change last line in the script ./sbin/icinga2 to use sudo
exec sudo $ICINGA2_BIN "$@"
Steps to Reproduce (for bugs)
Context
This is custom installation from source.
Your Environment
icinga2 --version
):icinga2 - The Icinga 2 network monitoring daemon (version: r2.6.3-1)
Linux version 2.6.32-642.11.1.el6.x86_64 (mockbuild@c1bm.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC) ) Add notes about certificate permission #1 SMP Fri Nov 18 19:25:05 UTC 2016
icinga2 feature list
):Disabled features: api command compatlog debuglog gelf graphite influxdb livestatus logstash opentsdb perfdata redis statusdata syslog
Enabled features: checker ido-mysql mainlog notification
Concern
As I compiled source with no-root user,
could you tell me why /apps/opt/icingadir2/lib64/icinga2/sbin/icinga2 is required to run as root?
I asked because for sure my SA (System Administrator) will ask.
The text was updated successfully, but these errors were encountered: