search

Cacti / plugin_monitor

Monitor Plugin for Cacti
GNU General Public License v2.0
36 stars 39 forks source link

Cacti 1.2.16 Monitor 2.5 #137

Closed bmfmancini closed 1 year ago

bmfmancini commented 3 years ago

Hey All,

I just moved our Lab over to 1.2.16 with Monitor 2.5 I notice that when the plugin is disabled device addition either manually or through automation fails with the below error

2021-01-05 15:41:02 - CMDPHP ERROR: A DB Exec Failed!, Error: Column 'monitor' cannot be null

bmfmancini commented 3 years ago

Ok I found a work around

If the Monitor device setting is set to off this problem will arise if you click it on the issue goes away image

bmfmancini commented 3 years ago

Another alternate fix in settings set the monitor to be on by default and whether you have the monitor setting on or off in the device setting it will work

image

TheWitness commented 3 years ago

The column was missing. Somehow it's been added now.

bmfmancini commented 3 years ago

The remote collectors are not happy they add the device but it goes into a weird state stays in unknown status forever this is via automation

2021-01-06 13:36:59 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:54 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:46 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:43 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:37 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:31 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:25 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save! 2021-01-06 13:36:19 - DBCALL ERROR: SQL Save on table 'host': Column 'monitor' does not exist, unable to save!

TheWitness commented 1 year ago

This issue is resolved and will be included in 2.6.