ERROR 1118 (42000) at line 1278: Row size too large (> 8126).

[FildaSmile]

Hello, i recieving this error while installing zabbix - when i want import initial schema and data. You will be prompted to enter your newly created password.

Version of zabbix: 5.0.1

Version of Linux Ubuntu: 20.04 LTS

Version of MariaDB: 10.3.22

Command line:


root@zabbix:~# mysql -uroot -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 48
Server version: 10.3.22-MariaDB-1ubuntu1 Ubuntu 20.04

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> create database zabbix character set utf8 collate utf8_bin;
Query OK, 1 row affected (0.002 sec)

MariaDB [(none)]> create user zabbix@localhost identified by 'password';
Query OK, 0 rows affected (0.001 sec)

MariaDB [(none)]> grant all privileges on zabbix.* to zabbix@localhost;
Query OK, 0 rows affected (0.001 sec)

MariaDB [(none)]> quit;
Bye
root@zabbix:~# zcat /usr/share/doc/zabbix-server-mysql*/create.sql.gz | mysql -uzabbix -p zabbix
Enter password:
ERROR 1118 (42000) at line 1278: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

Can anyone advice how to solve it quickly ?

I did same installation month ago, same ZBX version, same linux and same DB version and i didnt recieve this error --strange.

Thank you in advance

[jdcowpland]

Did you ever get this fixed?

[tim.mooney]

Many people have run into the issue you're seeing, I've posted in quite a few threads related to this now, for example post #4 in https://www.zabbix.com/forum/zabbix-...ariadb-upgrade

You're most likely to see it on upgrade, rather than a fresh install, but if you don't adhere to the installation requirements you might even see it on a fresh install.

If you provide some information about your environment either myself or someone else can probably walk you through what you need to do.

Is this a fresh install, or is it an upgrade of an existing install?

Whether it's a fresh install or upgrade, please provide these 5 bits of information:

1. what version of Zabbix?
2. what database (MySQL, MariaDB, or Percona) are you using AND what's the exact version of the database software?
3. what Linux distro and version?
4. when you connect as the database root user and run the following command, what lines does it output:

   SHOW GLOBAL VARIABLES LIKE 'innodb_file%';

5. Also while connected to the database as the database root user, what does this output:

   SHOW GLOBAL VARIABLES LIKE 'innodb%prefix';

If it's an upgrade of an existing install, then please also provide this info:

1. what version of Zabbix are you upgrading from (in addition to question 1 above)?
2. you don't need to show the full output of this command, but it's likely that every table reports the same row_format from this query, so what format is that:

   SELECT name,row_format FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES WHERE NAME like 'zabbix%';

[tim.mooney]

See my post #4 in this recent thread: https://www.zabbix.com/forum/zabbix-...chema-and-data

Basically, a fresh install of Zabbix 4.0.x LTS may not have been as thoroughly tested with that version of MariaDB as Zabbix 5.0.x LTS has been. If you're starting fresh, you'll probably have better luck using the 5.x LTS install.

[alexis600]

Hi Tim! I gave up 4.0, and installed the 5.0 version, I am having an issue with the frontend, When restarting the service I get the message zabbix-server.service can't open pid file /run/zabbix/zabbix_server.pid, and I cannot access from the host PC. I will continue my researching, regards!!!

[alexis600]

Finally, I could finish the installation! Reading this forum was the key!!!

[jdcowpland]

It's basically a combination of both :P I'm migrating from one machine to another. Old machine is Zabbix 4.0.4 (appliance install) I think and new one is Zabbix 5 on a clean Debian10, so I've done a dump of the database from the old machine and am trying to import it into mariadb on the new machine. I managed to get round the problem by setting my default table format to MyISAM instead of innodb and by setting the innodb_strict_mode = 0. Not sure if this was the best way to do it as I found some comments about it not being a good idea, but it allowed me to get my database imported and now I'm all up and running on the new machine with no problems so far. Would be interested to know what you would have suggested though.

[tim.mooney]

Without knowing answers to the database-related questions I asked, I can't really provide any suggestions.

There are several factors that go into large index size support with MySQL and MariaDB. That's why I asked so many questions about your database environment.

[Gutsycat]

Try to set innodb_default_row_format = DYNAMIC in your configuration file

[FildaSmile]

Hello, im very sorry for not answering your questions, i was relocated to another project for some time.

In the end i was able to solve it by changing row format to dynamic

Thanks for support and once more sorry for late reaction, from now i will work on zabbix continuously.

[thommen]

I have a problem with the same.

I have installed Zabbix → https://www.tecmint.com/install-zabbix-on-debian-10/
I have
1.

zabbix-agent - 1:4.2.8-1+buster
zabbix-frontend-php - 1:4.2.8-1+buster
zabbix-server-mysql - 1:4.2.8-1+buster

2. mariadb Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

3. Debian 10

4.

MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'innodb_file%';
+-----------------------+-----------+
| Variable_name | Value |
+-----------------------+-----------+
| innodb_file_format | Barracuda |
| innodb_file_per_table | ON |
+-----------------------+-----------+

5.

MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'innodb%prefix';
+---------------------+-------+
| Variable_name | Value |
+---------------------+-------+
| innodb_large_prefix | 1 |
+---------------------+-------+

I have completely removed the previous version. This is a fresh install.

I also read → https://mariadb.com/kb/en/troublesho...s-with-innodb/.

MariaDB [(none)]> SELECT NAME, ROW_FORMAT
-> FROM information_schema.INNODB_SYS_TABLES
-> WHERE ROW_FORMAT IN('Redundant', 'Compact')
-> AND NAME NOT IN('SYS_DATAFILES', 'SYS_FOREIGN', 'SYS_FOREIGN_COLS', 'SYS_TABLESPACES', 'SYS_VIRTUAL', 'SYS_ZIP_DICT', 'SYS_ZIP_DICT_COLS');
Empty set (0.003 sec)

I really don't know what to change in order not to do any damage. Please help

[thommen]

In my case, I used the clue from → https://mariadb.com/kb/en/troublesho...archar-columns. I have replaced "varchar (*)" with "varchar (256)"

[seanac]

Help with importing the zabbix data would be appreciated.

I have run into this issue (ERROR 1118 (42000) at line 9415: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.). Row 9415 is "CREATE TABLE `host_inventory` (".

I have installed a new VM with debian 11, zabbix_server (Zabbix) 6.0.6 Revision 3f7597e3ea3 27 June 2022, 10.6.8-MariaDB-1:10.6.8+maria~bullseye. The old/running VM is on debian 8.7, zabbix_server (Zabbix) 3.4.15 Revision 86739 12 November 2018, and mysql 5.5.54-0+deb8u1.

On the new VM:
MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'innodb_file%';
+-----------------------+-------+
| Variable_name | Value |
+-----------------------+-------+
| innodb_file_per_table | ON |
+-----
MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'innodb%prefix';
Empty set (0.002 sec)
------------------+-------+

The row format is DYNAMIC on the new VM while COMPACT on the old.

When I import with sudo zcat /usr/share/doc/zabbix-sql-scripts/mysql/server.sql.gz | mysql -uzabbix -p'XXXXXXX' zabbix it works fine and zabbix web interface is working.

Thanks.