Patrick Maroney

Note that this issue was introduced a number of versions back. Not sure at which point it appeared but I first saw it as far back as ~4/8/22 - 4/15/22.

Data Point. After github-germ purged and started rebuild of correlations table, I still see the following artifacts: I just ran  show correlations in mysql and still see 10 million+ correlation...

_I think I'm tracking this correctly(???):_ Why not simply 'fix' the definition.json? [Either directly or have the author do so]

Thanks for the timely response. The issue exists with the SSL Proxy between the client and server. I've tried setting Timeout previously (and again this AM), but it has no...

To show how a "timeout" issue would manifest itself in our environment, I set timeout=30: `ReadTimeout: HTTPSConnectionPool(host='misp.cso.att.com', port=443): Read timed out. (read timeout=30) ` Full error log: ``` --------------------------------------------------------------------------- timeout...

Please have a look earlier in the thread: What we've tried to date: We've tried setting the following on the DataBrick 'client' side %sh #========================== sysctl -w \ net.ipv4.tcp_keepalive_time=60 \...

Note that the above values are accepted on the Linux server that executes PyMISP: ``` %sh 2 sysctl -a 2>/dev/null | grep -i keepalive net.ipv4.tcp_keepalive_intvl = 60 net.ipv4.tcp_keepalive_probes = 9...

pcaps will be a little tricky - let me see what I can do...

No impact - same error.

Update: I made some changes to do pcaps and restarted the Databricks cluster. So far it seems to be working (at least gets past 2 minutes without failing)