[Upgrading] Big jump: from 1.2.6 to 1.2.24

[gaffiere]

Hello everyone!
I'm planning to update my old and stable installation of cacti 1.2.6, and spine 1.2.6, to latest 1.2.24: yes it's a big jump

My env is a RHEL 7.9 with mariadb 5.5.68, php 5.4.16, httpd-2.4.6-99, rrdtool-1.4.8 and this will not be touched.

Do you have any particular suggestion or is it enough to follow http://docs.cacti.net/Upgrading-Cacti.md ?

Thank you for your well accepted feedback

Regards
Gaffiere

[macan]

Better to update to 1.2.x branch from here https://github.com/Cacti/cacti/tree/1.2.x
It will be new 1.2.25 version. It is better than 1.2.24

Backup, backup, backup

It is enough to follow http://docs.cacti.net/Upgrading-Cacti.md

[TheWitness]

Yes, we had a small problem with PHP7.4 vs PHP5.4-PHP5.6 support in 1.2.24. We've delayed the 1.2.25 release for quite a while for various reasons. We are hoping that we can end 1.2.25, and leave it there. We have a lot to do in for the 1.3 release.

My suggestion, that if is a new system, get off RHEL7 and move to a more supported platform with more modern PHP version. I prefer Rocky 9.2 myself.

[TheWitness]

As far as zero downtime upgrades, xmacan has been working on that process. I'm not sure if he's available for contract, but he's an expert.

[gaffiere]

Better to update to 1.2.x branch from here https://github.com/Cacti/cacti/tree/1.2.x
It will be new 1.2.25 version. It is better than 1.2.24

Backup, backup, backup

It is enough to follow http://docs.cacti.net/Upgrading-Cacti.md

This is my mantra Backup and vm snapshot before any activity.

[gaffiere]

Thank you both for your answers!
Unfortunately I cannot migrate to new RHEL and I must keep actual vm.
Version 1.2.25 has better support to old php 5.4.16, am I right?
for my personal curiosity: has any version prior 1.2.24 better support to old php, or better to update to 1.2.25?

Does the same also apply to "Spine", i.e. to download from the 1.2.x branch on github?

Thank you and have a nice day!

[macan]

Yes, 1.2.25 has better support to php 5.x than 1.2.24.
Definitelly update to 1.2.25. We don't know about any problems or errors on this version. Have a look at Changelog.

Spine - you can have different version of spine and cacti but have the same is better/safer.

[Osiris]

Almost no bugs left.

[gaffiere]

Upgrade process was quite fine, I had to install php-intl module from rscl repo.

Now I'm facing a strange issue: I've gaps in graph whose data source is custom script (bash + ssh connect).
No gaps in graphs whose datasource is "standard."

In logs I see a lot of

Code: Select all

2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: You have 16 Devices with bad SNMP Indexes. Devices: Device[88], Device[86], Device[84], Device[114], Device[124], Device[118], Device[195], Device[58], Device[297], Device[318], Device[320], Device[328], Device[384], Device[277], Device[276], Device[475] totalling 153 Data Sources. Please Either Re-Index, Delete or Disable these Data Sources.
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21770] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21765] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21760] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21755] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21750] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21745] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21739] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21734] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21729] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21724] Encountered [U] Expected[]
2023/07/28 19:59:22 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21719] Encountered [U] Expected[]
2023/07/28 19:59:21 - POLLER: Poller[1] PID[7900] WARNING: Invalid output! MULTI DS[21714] Encountered [U] Expected[]
....

my HW is
10 CPU
16 GB RAM

my.cnf

Code: Select all

[mysqld]
bind-address=127.0.0.1
character-set-server=utf8mb4
collation_server=utf8mb4_unicode_ci
max_heap_table_size=256M
max_allowed_packet=16777216
tmp_table_size=256M
join_buffer_size=128M
innodb_file_per_table=ON
innodb_buffer_pool_size=8G
innodb_doublewrite=ON
innodb_additional_mem_pool_size=128M
innodb_flush_log_at_trx_commit=2
innodb_file_format=Barracuda
innodb_large_prefix=1
max_connections=400
sort_buffer_size=256M

Datasource >14000
Graphs >9000


any hint?
Thanks in advance

[gaffiere]

found this error:

ERROR: /var/www/html/cacti-1.2.25/rra/51/6185.rrd: illegal attempt to update using time 1690576443 when last update time is 1690576443 (minimum one second step)

repeated for a lot of lines

[TheWitness]

Update RRDtool to 1.5++ then, you will not see these errors any more. You can download the source from rrdtool.org and do a make/install. It works fine on RHEL7.x. All the dependencies are available through yum.

On the multi-part, I would recommend you go the as of yet unreleased 1.2.25 and report back again. I'll look to see if there is some way to improve the logging to make the diagnostics easier.

[TheWitness]

Looking at the log again, what is the data input method for those data sources? Can you run it manually using the command prompt and show the output?

[gaffiere]

Thank you all for your feedbacks; unfortunately I had to rollback, 'cause it was an upgrade in prod
I'm pushing to create a new and updated vm and to migrate sets of checks after an efficient review of scripts used to feed datasources.

[Osiris]

Totally agree. Trust but verify is what I always say. Currently, I'm trying not to break production with the simplest of things, upgrading MariaDB.