Closed frimdo closed 5 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This smells like a Synology 3.x kernel issue to me. I can't replicate this on a normal Linux host with a non-EOL kernel. Using your compose:
$ docker exec -it smokeping bash
root@5943263a3588:/# /usr/sbin/fping -C 20 -q -B1 -r1 -i10 8.8.8.8
8.8.8.8 : 28.8 23.1 18.0 16.7 20.5 20.6 17.4 17.1 17.9 16.8 27.8 17.0 22.8 17.5 20.6 16.5 14.8 22.7 18.0 20.9
root@5943263a3588:/#
I suspect it to be due to user permissions, as in my case the fping does not work for user (uid 1026), but does work in the shell of the container as root (uid 0). Is there any way I could get more data? Running smokeping in debugging mode (the environment variable DEBUG=1 seems to do nothing)? Running fping in debugging/verbose mode?
Indeed, if I docker exec
as user (1026), the fping does not work.
$ docker exec -it -u 1026 smokeping sh
Password:
abc@657538c2f711:/$ id $(whoami)
uid=1026(abc) gid=100(abc) groups=100(abc),1000(users)
abc@657538c2f711:/$ /usr/sbin/fping -C 20 -q -B1 -r1 -i10 8.8.8.8
abc@657538c2f711:/$ /usr/sbin/fping 8.8.8.8
/usr/sbin/fping: can't create socket (must run as root?)
Still unable to replicate the behaviour on my Ubuntu host:
abc@77b9fb161616:/$ id abc
uid=1000(abc) gid=1000(users) groups=1000(users),1000(users)
abc@77b9fb161616:/$ /usr/sbin/fping -C 20 -q -B1 -r1 -i10 8.8.8.8
8.8.8.8 : 22.0 22.2 18.2 23.5 19.3 20.5 18.1 17.0 27.9 20.1 18.8 18.4 22.0 21.3 22.0 21.9 17.8 17.4 18.0 20.6
abc@77b9fb161616:/$ /usr/sbin/fping 8.8.8.8
8.8.8.8 is alive
Is there any way I could run smokeping/fping in debug mode to obtain more data, since you are not able to replicate the behavior? I tried to add the environment variable DEBUG=1
to smokeping docker-compose file, but I see no difference in logs after restarting the container.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
I am also unable to replicate this, there is no debug mode and given that it's the fping command that is going wrong (even manually) this does rule out smokeping. I'd suggest that the earlier suggestion of the EOL kernel possibly being the issue, and suggest updating to some different hardware where possible (or using a low cost VPS).
Current Behavior
All fping targets results in 100% packet loss.
I have internet connection, as for example if I run the problematic command as root, the results are reasonable:
Expected Behavior
At least some fping targets results successfull. As for example for DNS probes.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs