Custom Probe spawn EPERM error
Describe the bug If you deploy a custom probe with Docker, the probe connects but cannot execute any Monitors.
To Reproduce Steps to reproduce the behaviour:
- Deploy a custom probe with Docker per documentation on Linux per:
docker run --name oneuptime-probe --network host -e PROBE_KEY=
The container starts and connects to OneUptime.
- Create a Monitor in the OneUptime Cloud Portal of Type Ping
- Attempt to Ping a host by name or IP on the private network
- Ping (and for that matter any Monitor Type) always fails
- Debugging the container yields the following error. I've verified that the container itself can reach hosts by name or IP on the internal network (e.g. via exec ping)
Pinging host: d777bc0a-74ec-4109-8a23-a5d476e37001 fs01 - Retry: 1
Pinging host d777bc0a-74ec-4109-8a23-a5d476e37001 fs01 error:
Error: spawn EPERM
at ChildProcess.spawn (node:internal/child_process:421:11)
at Object.spawn (node:child_process:753:9)
at /usr/src/app/node_modules/ping/lib/ping-promise.js:43:23
at new Promise (
Expected behaviour The Probe should be able to ping hosts.
Screenshots No screenshots
Desktop (please complete the following information):
- OS: Windows 11 22H2
- Browser: Firefox
- Version: 139.0.1
Smartphone (please complete the following information): Not applicable
Deployment Type SaaS + on-premises probe running on Rocky Linux 9.6 VM.
Additional context None