Ns8-patchmon testing

App
, ,
21

No need to apologize. That’s just how it is; it’s part of the development process.

I now have PatchMon, Pulse, and PegaProxy running as standalone VMs/LXCs, and I think they’re real gems.

The new compliance scans in Patchmon are producing interesting results that could be considered for hardening the servers.

However, these scans seem to consume considerable resources.

While they run without any problems on classic Debian systems, they time out on the NS8 servers.

I’ve already adjusted a few .env parameters…

DB_TRANSACTION_TIMEOUT=120000
DB_TRANSACTION_LONG_TIMEOUT=300000
JSON_BODY_LIMIT=50mb
AGENT_UPDATE_BODY_LIMIT=50mb

…but it’s still not running satisfactorily.

1 Like
22

Hi, I’ve released v0.5.0 of ns8-patchmon, packaging PatchMon 2.0.2
It’s a complete rewrite in Go and a lot of major changes please make a snapshot before upgrade.
New in PatchMon 2.x: Linux patching, notifications (SMTP/webhook/ntfy), OpenSCAP/CIS compliance, Windows agent (beta), FreeBSD support.
Upgrading from 1.4.x is automatic the module should handles env migration and DB migrations on its own.

changelog: v2.0 · Releases · PatchMon/PatchMon · GitHub
docs: 2.0.0 (Major) | PatchMon Documentation

2 Likes