Ad Widget

**tim.mooney** · 08-09-2020, 06:05

When you see "the table <whatever> is full" from MySQL (or MariaDB or Percona), the first two places you should look are

is the volume where the database files reside full?
since this is a 32 bit OS (I wouldn't recommend that, at this point) you probably need to determine if the file containing the history_uint table has reached the maximum supported size that MySQL allows on 32 bit CentOS. Since you are using "innodb_file_per_table" (that's good!), how big is the history_uint.ibd file?

**csid2174** · 08-09-2020, 08:38

Thank you Tim for your very useful feedback. I should actually install mysql in a larger partition, I don't know what I was thinking. I think I was having amateur moment and it didn't quite occur to me whilst installing the packages and since you've mentioned this, I am having a light bulb moment since my /root partition is only configured to be 22GB and the damn history_uint.ibd is 30GB. Like I said, I should have been more careful, as a network guy I really didn't give too much thought on these constraints while installing Zabbix 4.4, but thanks to you, I'll go to my office at some stage and do a re-install with smarter allocation of space and do the install in the system partition which is 260GB in size.

Due to this pandemic I am unable to fix this issue immediately cause of travel restriction ,but if you don't mind can I give you my feedback in three weeks time. I am pretty certain that harddisk space is my problem as you've correctly identified and I'll rectify this issue soon-ish.

Thanks again for your useful feedback and I really appreciate it. Also I am surprised at my ineptness since I've been managing Zabbix 2.4.5 for last 5 years and I just remembered that I kind of had the same issue in the beginning where I moved the mysql install to the larger partition after the install and used sym-links for Zabbix to access mysql directory structure. Anyhow thanks again for the help.

**tim.mooney** · 09-09-2020, 05:08

Glad to help.

If you can remotely access the system (I know that not every organization allows that kind of access), you may be able to do most of the fixing remotely, depending on a few factors. For example, if you're using LVM on the system and there is unconfigured free space in an appropriate LVM volume group, you may just be able to grow a volume to make more space available to it. That generally doesn't work with the / partition (usually you don't put that under LVM), but depending on how you want to arrange things, it still may be possible to grow space elsewhere and then move the database onto the new volume.

PS: if you do end up reinstalling, remember that CentOS 6.x is end-of-life in just a couple months. If your company allows it, using 64 bit CentOS 7 or CentOS 8 puts you in better shape to be able to upgrade to recent Zabbix versions.

Ad Widget

Zabbix 4.4 error - [Z3005] query failed: [1114] The table 'history_uint' is full

Zabbix 4.4 error - [Z3005] query failed: [1114] The table 'history_uint' is full

Comment

Comment

Comment