HPE 3PAR StoreServ Storage
1753532 Members
6142 Online
108795 Solutions
New Discussion юеВ

Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client address

 
neiraj
New Member

Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client address

Hello community,

"Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client address 10.xxx.xx.xx"

Our red team in our environment pen-tests the whole environment and these alerts get generated everytime auto-generating incident tickets. Is there any way we can stop this alert? Is there any-way to silence this if we cant stop?

 

3 REPLIES 3
Dennis Handly
Acclaimed Contributor

Re: Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client add

The only way to stop them is to make sure you don't use that many connections.

What does showuserconn show?  And it is reasonable to have that many?

neiraj
New Member

Re: Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client add

Thank You for reply Dennis,

Those connections get created as part of "pen-test" done by red team and they are automated to go far beyond 64 even if we increase the limit. And these are temporary but the error shows up every-month when they do the audit. I was wondering if there was a way to stop this alert changing the 3par setting.

Dennis Handly
Acclaimed Contributor

Re: Max allowable tpdtcl processes of 64 exceeded, no process created for connection from client add

>Those connections get created as part of "pen-test" done by red team and they are automated to go far beyond 64

 

There is no way to change this and security concerns require this to be always logged.