Upgrade from 1.1.37 to 1.2.23 - Import database not working. -SOLVED

[krw]

Update:

Going over errors the one at the end was glaringly obvious:

ERROR 1839 (HY000) at line 24: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON

I redumped the database on the original server with this:

mysqldump --set-gtid-purged=off cacti -u root -p > cacti.sql

The new dump imported and all data is now there in the new cacti database.

-----------




Building a new VM for cacti.

Moving from 1.1.37 to 1.2.23.

mysqldump cacti -u root -p > cacti.sql

Have a good dump of the database.

Import into new cacti:

mysqldump -u root -p cacti < cacti.sql

Data from the dump flashes by on the screen and ends with:

LOCK TABLES `version` WRITE;
/*!40000 ALTER TABLE `version` DISABLE KEYS */;
INSERT INTO `version` VALUES ('1.2.23');
/*!40000 ALTER TABLE `version` ENABLE KEYS */;
UNLOCK TABLES;
SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

-- Dump completed on 2023-09-25 16:25:12

But I see nothing actually was imported into the new database.

Going back over the screen output I don't see any errors.

Tried this:

> mysql -u root -p cacti < cacti.sql

ERROR 3546 (HY000) at line 24: @@GLOBAL.GTID_PURGED cannot be changed: the new value must be a superset of the old value

I moved a different cacti database on another server a while ago from a pre v1 server to a 1.2.15 and that seemed to work ok.

Server info:

-- MySQL dump 10.13 Distrib 8.0.32, for FreeBSD13.1 (amd64)
--
-- Host: localhost Database: cacti
-- ------------------------------------------------------
-- Server version 8.0.32

Is there something I need to do on the new server before importing?

Thanks.

[TheWitness]

Move instead to 1.2.25. It's proving to be a keeper, though we are solving a few corner cases still in the planned 1.2.26.

[TheWitness]

If the other server is being replicated, you have to be careful with some table types. The ones that are MEMORY storage engine may be marginally supported on a replicated setup. Thankfully, it's not important that the memory tables be replicated so long as your pollers are going to the write service only. In order to be prepared for failover though, you may need to create them separately on the replica's. Not testing it on MySQL as I'm pretty much using MariaDB these days.

[krw]

This is a straight upgrade and migration to a newer VM, no replication involved.

I'll look at updating to 1.2.25.

Thank you.