[SMOKEPING] fping does not work with default options

[karypid]

SCALE version
TrueNAS-SCALE-22.02-RC.2

App Version
1.18.6_9.0.37

Application Events
N/A

Application Logs
N/A

Application Configuration
DEFAULTS IN EVERYTHING

Describe the bug
When selecting defaults for everything, smokeping was only working for DNS probes. All other graphs for ping latency (Internet Sites/Europe/North America/DNS) were NOT populating.

To Reproduce

1. Go to 'Available Applications'
2. Click on 'Install' on smokeping
3. Click 'Next' for all the default options
4. Wait for some time
5. Check graphs on web portal of smokeping, they will be empty except DNS probes
6. Open shell for smokeping
7. Type su - abc -s /bin/bash to become the user running smokeping service
8. Type fping facebook.com
9. OBSERVE ERROR: You get fping: can't create socket (must run as root)

Expected behavior
The abc user which is configured to run smokeping shoule be able to use fping to generate graph data

FIX FOR THIS
According to this bug filed in LinuxServer with title 'Fping Probe not functioning as non-root' the fping process is installed with special set-uid permissions and therefore requires that the privilege escalation is configured to be allowed. Truecharts does not do this by default.

To fix this I re-created the application and changed the following configuration options:

1. In "Security and Permissions" selected "Show Advanced Security Settings"
2. In "Security Context" selected "Allow Privilege Escalation" (default is NOT selected, which causes the problem)

Additional context
I went on the Discord support channel and they suggested I raise a bug. There are screenshots and analysis on support thread "smokeping does not ping" started 18 January 2022.

[stavros-k]

Thanks for the in-depth research. PR is coming.

[PrivatePuffin]

@all-contributors please add @karypid for bugs

[allcontributors]

@Ornias1993

I've put up a pull request to add @karypid! 🎉

[truecharts-admin]

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists