Hi Ad,
Thanks for the reply. The VM is quite capable and the config is reasonably simple so I assumed there was an issue with the config parser. I downloaded the config to have a look at the XML and it was 80,000 lines long! Almost all of it was BAN directives in the nginx config. That's not something we configured so it looks like the default setting is to ban IPs (on some criteria I'm not aware of) and to never release that ban. So by default, the list of banned IP will grow and grow until it produces we result we've been seeing.
I found the 'Autoblock TTL' setting in the advanced nginix config, which was set to 0. I set that to 1 day, saved the config, and the issue was resolved. The config went from 80,000 lines to 3,000 lines and the CPU problem was immediately fixed. Perhaps the default settings need to be tweaked to avoid this situation.
Thanks for the reply. The VM is quite capable and the config is reasonably simple so I assumed there was an issue with the config parser. I downloaded the config to have a look at the XML and it was 80,000 lines long! Almost all of it was BAN directives in the nginx config. That's not something we configured so it looks like the default setting is to ban IPs (on some criteria I'm not aware of) and to never release that ban. So by default, the list of banned IP will grow and grow until it produces we result we've been seeing.
I found the 'Autoblock TTL' setting in the advanced nginix config, which was set to 0. I set that to 1 day, saved the config, and the issue was resolved. The config went from 80,000 lines to 3,000 lines and the CPU problem was immediately fixed. Perhaps the default settings need to be tweaked to avoid this situation.