On Tue, Jun 22, 2021 at 04:48:26PM +0800, Siegfried Levin wrote:
> > Why have you chosen to hide information that may be useful in debugging your problem?
>
> I'm truly sorry for the inconvenience but I do have some concerns of security and privacy. I confirm it is not a broadcast address because it is the public IP of the server and this issue has a probability of 1% to happen. The address cannot just be a broadcast address at 1% of the time while not at the rest of 99%. I also double checked it by SSHing to the address I copied from the kdump, if it makes sense.
>
> > So, since the manpage mentions blocking pf, I suggest the hypothesis "it returns EACCES because pf is blocking your packets". I can think of several ways to test that; what testing have you performed to confirm or rule out that possibility? "doas pfctl -d; run test; doas pfctl -e"?
>
> This issue is really hard to reproduce because the application works at most of the time, but I think you are right. I'll be watching the pf log in next weeks.
>
Also check the various counters of netstat -s and especially pfctl -si (or
systat pf). In the pfctl output especially check memory, congestion or
state errors.
--
:wq Claudio
No comments:
Post a Comment