Hi guys, Im facing multiple problems trying importing cacti.sql schema on my new datatabase.
I tested same command on my old mysql server (ver 5.6) and worked ok.
Now on my mysql server version 8.0.11 import script doesnt work.
First attempt was:

After that I tried commenting this line but other errors apeared.
Is there some way to solve this ?
Should I downgrade my mysql server ?
Any idea would be welcome.
Regards,
Leo.

What were the other errors?

Dear , netniV.
Sorry ; i had to move on.. so I decided to use an older mysql server.
I already pass the database seting, now Im facing other situacion , please take a look to my newest post:
https://forums.cacti.net/viewtopic.php?f=2&t=58738

btw : How do I close this thread ?
Regards.
Leandro.

I, too, am facing this issue.

Environment:
* CentOS 7
* mysql-community-server-8.0.11-1.el7.x86_64
* cacti-1.1.37-1.el7.noarch

When attempting to load /usr/share/doc/cacti-1.1.37/cacti.sql into a fresh database, I receive the following error:

ERROR 1231 (42000) at line 6: Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER'

If I remove NO_AUTO_CREATE_USER, the SET SESSION line looks like this:

SET SESSION sql_mode = 'NO_ENGINE_SUBSTITUTION';

That portion of the SQL script runs successfully. However, the import then fails on the following error:

ERROR 1064 (42000) at line 462: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'system mediumint(8) unsigned NOT NULL DEFAULT '0', name varchar(255) NOT NULL ' at line 4

So, I'm not able to complete my Cacti setup because the SQL script doesn't complete. Any advice on how to proceed would be greatly appreciated.

Thanks!

Try removing the NO_ENGINE_SUBSTITUION too, see if that makes any difference?

Thanks, netniV. I ran into the same issue. I found that, for some reason, MySQL didn't like that some columns weren't marked with back ticks. For what it's worth, I also downloaded the install from cacti.net for cacti-1.1.37 and cacti-1.1.38; their SQL files had the same problem.

I've uploaded a copy of the SQL file that worked. Hopefully this helps someone else resolve their issue if using a similar setup.

Matthew

As others may have this same issue, if you can, open or find an existing MySQL 8.1 issue on the GitHub site and add your comments/files/changes to it

This helped me, thanks for the file. Now I'm stuck in another place