Monitor 2.3.6 A DB Exec Failed!, Error: Column 'monitor' cannot be null

Question

Monitor 2.3.6 A DB Exec Failed!, Error: Column 'monitor' cannot be null

Closed this issue 2 years ago · 9 comments

Monitor Version 2.3.6
cacti Version 1.2.9

Issue:

When you delete all devices and start from 0 devices when you attempt to add a new device either manually or through Autom8 the following error occurs

A DB Exec Failed!, Error: Column 'monitor' cannot be null
you will then see all device additions will fail

If you disable the monitor plugin the issue goes away if you re-enable monitor after the first device is created the issue with monitor is resolved as well

Answer 1 · 2020-02-24T20:24:34.000Z

I believe the issue could be the monitor colum is set to Null no

monitor | char(3) | NO | | on | |

Answer 2 · 2020-02-24T21:04:59.000Z

Ok I was able to fix this issue at least for me

ALTER TABLE host MODIFY monitor varchar(255) null;

No more errors so far still testing

Answer 3 · 2020-02-24T23:39:37.000Z

I would say that monitor should always be empty as default not null.

Answer 4 · 2020-02-25T01:50:21.000Z

Hmm ok so does the script need to be updated for that ?

By default the entry into the DB is NULL no changing it to yes seems to correct the issue
Ive tested it multiple times now in the lab without issues since that change

Answer 5 · 2020-02-28T10:23:36.000Z

not sure how you've managed to get that setup then as this is the current table addition code:

api_plugin_db_add_column ('monitor', 'host', array('name' => 'monitor', 'type' => 'char(3)', 'NULL' => false, 'default' => 'on', 'after' => 'disabled'));

As you can see, the default should be set to 'on' which means it's active. You should be able to update this to match by using:

ALTER TABLE `host` MODIFY `monitor` CHAR(3) NOT NULL default 'on';

I would suggest that before you run the above, you run the following before and after to monitor changes:

SHOW CREATE TABLE `host`\G

Answer 6 · 2020-03-02T21:24:51.000Z

Ok I made the change seems to be fine but I swear all I have is the dev branch files
are we sure something wasn't tweaked in the code that changed that ?

Answer 7 · 2020-04-29T23:06:15.000Z

Use git log -L to check the history of lines in a file. It's how I usually tell @cigamit or @TheWitness which one broke something (unless of course I did, then I just quietly fix it).

Answer 8 · 2020-04-29T23:24:30.000Z

@netniV wise guy. True though.

Answer 9 · 2023-04-12T01:56:51.000Z

This is resolved in the to be released 2.6