Clay Oster
Clay Oster
The DeprecationWarning message is now occurring in version 3007.1. I'm also only noticing it when using `state.apply` for state files which include pkg state modules. This only seems to be...
> We are also seeing this problem, running v3007.0 on Ubuntu 22.04. Salt Master seems to run fine for a while and then locks up with same errors as seen...
@jsansone-pw - Yes that did successfully prevent the issue for me. I used a local firewall (nftables) to block connections to TCP 4505-4506 from the scan engine IPs and that...
A quick band-aid fix is to configure the local firewall on the master server(s) to drop incoming connections to TCP 4506 from the IP addresses of the vulnerability scanning systems...
@dynek That sounds like a different issue to me. In my environment, normal minion/master communication does not cause any instability or error logs. All minions and masters are on 3007.1.
I have noticed that the number of errors that are logged before the master becomes unresponsive seems to match the number of worker threads defined. This makes me think that...
@jsansone-pw - I think there is a high likelihood that you would see the same issue. In a previous environment I managed, Rapid7 was in use and triggered the issue...
I have confirmed this is still an issue in 3007.2. Switching `break` to `continue` in the request_handler function's exception block (shown in https://github.com/saltstack/salt/issues/66519#issuecomment-2312612796) still provides a band-aid fix for now.
Confirmed this issue is still present in 3007.3.
Confirmed this issue is still present in 3007.4.