Hi Victor,
The 2.2.9 Upgrade solved all issues
everything works just great!!
Regards
Clifford Dsouza
			The 2.2.9 Upgrade solved all issues
everything works just great!!
Regards
Clifford Dsouza
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts Menu
Quote from: clifford on August 08, 2018, 09:17:25 AMQuote from: clifford on August 08, 2018, 09:16:21 AMQuote from: clifford on August 08, 2018, 08:40:18 AMQuote from: clifford on August 07, 2018, 02:31:00 PM
Thanks,
i changed the values to 512, hope this helps..
however i could not find the ThreadPool.Syncer.MaxSize parameter in the server configuration., so i manually created one, when you say it should be greater than 1, what could be the recommended value based on the stats i posted.
netxmsd: show threads
MAIN
Threads: 8 (8/512)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
POLLERS
Threads: 509 (10/512)
Load average: 51.59 54.84 62.20
Current load: 8%
Usage: 99%
Active requests: 44
Scheduled requests: 0
DATACOLL
Threads: 250 (10/250)
Load average: 4.68 4.33 2.69
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
Thanks
Clifford
When everything is fine and the CPU is at 3% to 25 % Usage
netxmsd: show threads
MAIN
Threads: 36 (8/512)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 7%
Active requests: 0
Scheduled requests: 0
POLLERS
Threads: 510 (10/512)
Load average: 41.75 112.32 76.88
Current load: 44%
Usage: 99%
Active requests: 226
Scheduled requests: 0
DATACOLL
Threads: 249 (10/250)
Load average: 0.72 6.04 4.81
Current load: 0%
Usage: 99%
Active requests: 2
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
SYNCER
Threads: 10 (1/10)
Load average: 17.84 29.54 14.71
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
When things are bad
netxmsd: show threads
MAIN
Threads: 2048 (8/2048)
Load average: 2996493.60 2968151.86 2119779.01
Current load: 145523%
Usage: 100%
Active requests: 2980327
Scheduled requests: 0
POLLERS
Threads: 1003 (10/1024)
Load average: 51.45 48.24 45.01
Current load: 5%
Usage: 97%
Active requests: 51
Scheduled requests: 0
DATACOLL
Threads: 512 (10/512)
Load average: 5.44 2.90 1.57
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
SYNCER
Threads: 7 (1/10)
Load average: 0.00 1.44 5.04
Current load: 0%
Usage: 70%
Active requests: 0
Scheduled requests: 0
System stats
all this is just snmp traffic
things got normal when i quit the console and all is well since reconnecting the console again
Regards
Clifford

Quote from: clifford on August 08, 2018, 09:16:21 AMQuote from: clifford on August 08, 2018, 08:40:18 AMQuote from: clifford on August 07, 2018, 02:31:00 PM
Thanks,
i changed the values to 512, hope this helps..
however i could not find the ThreadPool.Syncer.MaxSize parameter in the server configuration., so i manually created one, when you say it should be greater than 1, what could be the recommended value based on the stats i posted.
netxmsd: show threads
MAIN
Threads: 8 (8/512)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
POLLERS
Threads: 509 (10/512)
Load average: 51.59 54.84 62.20
Current load: 8%
Usage: 99%
Active requests: 44
Scheduled requests: 0
DATACOLL
Threads: 250 (10/250)
Load average: 4.68 4.33 2.69
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
Thanks
Clifford
When everything is fine and the CPU is at 3% to 25 % Usage
netxmsd: show threads
MAIN
Threads: 36 (8/512)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 7%
Active requests: 0
Scheduled requests: 0
POLLERS
Threads: 510 (10/512)
Load average: 41.75 112.32 76.88
Current load: 44%
Usage: 99%
Active requests: 226
Scheduled requests: 0
DATACOLL
Threads: 249 (10/250)
Load average: 0.72 6.04 4.81
Current load: 0%
Usage: 99%
Active requests: 2
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
SYNCER
Threads: 10 (1/10)
Load average: 17.84 29.54 14.71
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
When things are bad
netxmsd: show threads
MAIN
Threads: 2048 (8/2048)
Load average: 2996493.60 2968151.86 2119779.01
Current load: 145523%
Usage: 100%
Active requests: 2980327
Scheduled requests: 0
POLLERS
Threads: 1003 (10/1024)
Load average: 51.45 48.24 45.01
Current load: 5%
Usage: 97%
Active requests: 51
Scheduled requests: 0
DATACOLL
Threads: 512 (10/512)
Load average: 5.44 2.90 1.57
Current load: 0%
Usage: 100%
Active requests: 0
Scheduled requests: 0
SCHEDULER
Threads: 1 (1/64)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
AGENT
Threads: 4 (4/256)
Load average: 0.00 0.00 0.00
Current load: 0%
Usage: 1%
Active requests: 0
Scheduled requests: 0
SYNCER
Threads: 7 (1/10)
Load average: 0.00 1.44 5.04
Current load: 0%
Usage: 70%
Active requests: 0
Scheduled requests: 0
System stats
all this is just snmp traffic