Scan agent is timing out when scan large subnets

[paulng30]

Hi,

I am using version 1.4 (not 1.4.1)

I just started deploying scan agents to scan remote networks. The problem I am experiencing is when I add a large subnet (/21) or adding more than four subnets (/24 and /22) to be scanned by the agent, the agent will scan all subnets but then throws this error at the end and nothing gets updated in the database.

---

Error: Could not connect to database! SQLSTATE[HY000] [2002] Connection timed out

Has anyone experienced this issue?

[Kendzione]

You can increase dadabase connection limit and/or connection timeout values in database config file. Please find configurable values in database documentation. śr., 2 wrz 2020, 15:01 użytkownik paulng30 <notifications@github.com> napisał:

…

Hi, I am using version 1.4 (not 1.4.1) I just started deploying scan agents to scan remote networks. The problem I am experiencing is when I add a large subnet (/21) or adding more than four subnets (/24 and /22) to be scanned by the agent, the agent will scan all subnets but then throws this error at the end and nothing gets updated in the database. ------------------------------ Error: Could not connect to database! SQLSTATE[HY000] [2002] Connection timed out Has anyone experienced this issue? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#70>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APNDURQZFNS2MJYKJUBQE5DSDY63VANCNFSM4QS7KW5Q> .