> I seem to understand this is the check on the innodb main tablespace.
>
> Sounds like an overflow in munin check that builds the graph,
> due to the type of check ("MySQL InnoDB free tablespace") I would not mind
> too much(There's no such critical thing like too much free space!),
> apart from p
Hi,
I seem to understand this is the check on the innodb main tablespace.
Sounds like an overflow in munin check that builds the graph,
due to the type of check ("MySQL InnoDB free tablespace") I would not
mind too much(There's no such critical thing like too much free space!),
apart from patc
> I have 4 out of 6 mysql graphs working in munin. "MySQL isam/myisam
> table-space usage" is a broken image and "MySQL InnoDB free
> tablespace" says:
>
> "This service is in CRITICAL state because one of the values reported
> is outside the allowed range.
> Field Internal name TypeWarn
I have 4 out of 6 mysql graphs working in munin. "MySQL isam/myisam
table-space usage" is a broken image and "MySQL InnoDB free
tablespace" says:
"This service is in CRITICAL state because one of the values reported
is outside the allowed range.
Field Internal name TypeWarnCritInf
