Cacti (home)ForumsDocumentation
Cacti: offical forums and support
It is currently Wed Jul 17, 2019 3:33 am

All times are UTC - 5 hours




Post new topic Reply to topic  [ 1 post ] 
Author Message
 Post subject: Load isn't measured correctly - current load always equals 0
PostPosted: Mon Apr 01, 2019 7:20 am 
Offline

Joined: Fri Jun 23, 2017 5:14 am
Posts: 6
Hello, I'm using Cacti 1.1.36 and thold plugin 1.0.4. I've noticed that load measurement is not detected correctly. On hosts where SNMPv3 is used, current load always equals 0. I've one host, which is using SNMPv2 and load measurement works correctly on it. Could you advice me what could be configured wrong or what can be the root cause? In attachments I've added screenshot where tholds are visible. Highlighted loads are from hosts where SNMPv2 is configured. Please also advise me what other information could I post here to debug issue.

Additional information:
Quote:
General Information
Date Mon, 01 Apr 2019 14:18:32 +0200
Cacti Version 1.1.36
Cacti OS unix
RSA Fingerprint db:e2:75:65:d2:27:93:5b:d9:7e:ff:dd:78:b2:44:7b
NET-SNMP Version NET-SNMP version: 5.7.2.1
RRDtool Version RRDtool 1.4.x
Devices 23
Graphs 84
Data Sources Script/Command: 5
SNMP Get: 52
SNMP Query: 60
Script Query: 2
Script Query - Script Server: 1
Total: 120
Poller Information
Interval 300
Type cmd.php
Items Action[0]: 172
Action[1]: 9
Action[2]: 2
Total: 183
Concurrent Processes 5
Max Threads 20
PHP Servers 5
Script Timeout 25
Max OID 50
Last Run Statistics Time:4.5544 Method:cmd.php Processes:5 Threads:N/A Hosts:23 HostsPerProcess:5 DataSources:183 RRDsProcessed:120
System Memory
MemTotal 8.00 K MB
MemFree 5.47 K MB
Buffers 362.50 MB
Cached 1.42 K MB
Active 1.91 K MB
Inactive 392.44 MB
SwapTotal 3.81 K MB
SwapFree 3.81 K MB
PHP Information
PHP Version 5.6.33-0+deb8u1
PHP OS Linux
PHP uname Linux ta-026 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64
PHP SNMP Not Installed
max_execution_time 30
memory_limit 128M
MySQL Tuning (/etc/my.cnf) - [ Documentation ] Note: Many changes below require a database restart
Variable
Current Value
Recommended Value
Comments
version 5.5.59-0+deb8u1 >= 5.6 MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
collation_server latin1_swedish_ci utf8_general_ci When using Cacti with languages other than English, it is important to use the utf8_general_ci collation type as some characters take more than a single byte. If you are first just now installing Cacti, stop, make the changes and start over again. If your Cacti has been running and is in production, see the internet for instructions on converting your databases and tables if you plan on supporting other languages.
character_set_client latin1 utf8 When using Cacti with languages other than English, it is important to use the utf8 character set as some characters take more than a single byte. If you are first just now installing Cacti, stop, make the changes and start over again. If your Cacti has been running and is in production, see the internet for instructions on converting your databases and tables if you plan on supporting other languages.
max_connections 151 >= 100 Depending on the number of logins and use of spine data collector, MySQL will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts.
max_heap_table_size 391M >=391M If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
max_allowed_packet 16777216 >= 16777216 With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M.
tmp_table_size 64M >= 64M When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
join_buffer_size 64M >= 64M When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file.
innodb_file_per_table OFF ON When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of MySQL. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.
innodb_buffer_pool_size 1953M >=1953M InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25% of your systems total memory, but your requirements will vary depending on your systems size.
innodb_doublewrite ON OFF With modern SSD type storage, this operation actually degrades the disk more rapidly and adds a 50% overhead on all write operations.
innodb_additional_mem_pool_size 80M >= 80M This is where metadata is stored. If you had a lot of tables, it would be useful to increase this.
innodb_lock_wait_timeout 50 >= 50 Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system.
innodb_flush_log_at_trx_commit 2 2 Setting this value to 2 means that you will flush all transactions every second rather than at commit. This allows MySQL to perform writing less often.


Attachments:
measurment.jpg
measurment.jpg [ 67 KiB | Viewed 169 times ]
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group