Steps to reproduce (which actions have you made) :
When a printer fails to obtain SNMP information (e.g. it's Ethernet cable is unplugged), the column "status" from glpi_plugin_printercounters_items_recordmodels table is changed for "1" (for indicating an error status, I believe).
When I enable the function "Error items" at the plug-in settings, the crontask "PluginPrintercountersErrorItem" should be run every 24 hours when an user access GLPI, but it simply doesn't happen. I had to run the crontask manually. Even running it manually and knowing that the printer is communicable, it successfully communicates with the printer with error but the "status" column from glpi_plugin_printercounters_items_recordmodels table isn't updated, and the counters isn't updated at the "Records" tab of the printer.
When I try to do a "Immediate record" with the printer with error, I receive the following message: "No printers to search".
When I disable the "Error items" function, I can successfully query the printer through "Immediate record" buttom and the counters are updated. The column "status" from glpi_plugin_printercounters_items_recordmodels table isn't updated and keep it as "1" status.
Expected result :
The crontask "PluginPrintercountersErrorItem" should be run when a user opens GLPI when the periodicity of the crontask is reached.
It should be possible to do a "Immediate record" with error items when the "Error items" function is enabled.
The column "status" from glpi_plugin_printercounters_items_recordmodels table should be updated from "1" to "0" if a SNMP query is sucess even if the function "Error items" is disabled.
Actual result :
I believe that the root cause of the problem is somehow related to SQL query logic from "selectPrintersToSearch" function. Apparently the message "No printers to search" happens when this function could not find any suitable printer to query, even when the "Immediante record" button is pressed at the "Records" tab of a specific printer. I believe that the errorHandler logic from the function should be ignored when doing an "Immediate record", because it works normally when I disable the "Error items" function from the plug-in, so maybe something related to the errorHandler logic is changing the query to somehow exclude printers with errors to it's errors be fixed exclusively by "PluginPrintercountersErrorItem" crontask, but it should be run anyway when an "Immediate record" is made and, when sucessfully, update the "status" column from glpi_plugin_printercounters_items_recordmodels table accordly. I believe that this change is affecting the "PluginPrintercountersErrorItem" crontask from selecting printers to search.
I believe that something is blocking the automatic execution from "PluginPrintercountersErrorItem" crontask, because it didn't run even after 48 hours, even with users accessing the GLPI normally.
Version of the plugin : 1.7.0
Version of your GLPI : 9.5.2
Steps to reproduce (which actions have you made) :
When a printer fails to obtain SNMP information (e.g. it's Ethernet cable is unplugged), the column "status" from
glpi_plugin_printercounters_items_recordmodelstable is changed for "1" (for indicating an error status, I believe).When I enable the function "Error items" at the plug-in settings, the crontask "PluginPrintercountersErrorItem" should be run every 24 hours when an user access GLPI, but it simply doesn't happen. I had to run the crontask manually. Even running it manually and knowing that the printer is communicable, it successfully communicates with the printer with error but the "status" column from
glpi_plugin_printercounters_items_recordmodelstable isn't updated, and the counters isn't updated at the "Records" tab of the printer.When I try to do a "Immediate record" with the printer with error, I receive the following message: "No printers to search".
When I disable the "Error items" function, I can successfully query the printer through "Immediate record" buttom and the counters are updated. The column "status" from
glpi_plugin_printercounters_items_recordmodelstable isn't updated and keep it as "1" status.Expected result :
The crontask "PluginPrintercountersErrorItem" should be run when a user opens GLPI when the periodicity of the crontask is reached.
It should be possible to do a "Immediate record" with error items when the "Error items" function is enabled.
The column "status" from
glpi_plugin_printercounters_items_recordmodelstable should be updated from "1" to "0" if a SNMP query is sucess even if the function "Error items" is disabled.Actual result :
I believe that the root cause of the problem is somehow related to SQL query logic from "selectPrintersToSearch" function. Apparently the message "No printers to search" happens when this function could not find any suitable printer to query, even when the "Immediante record" button is pressed at the "Records" tab of a specific printer. I believe that the errorHandler logic from the function should be ignored when doing an "Immediate record", because it works normally when I disable the "Error items" function from the plug-in, so maybe something related to the errorHandler logic is changing the query to somehow exclude printers with errors to it's errors be fixed exclusively by "PluginPrintercountersErrorItem" crontask, but it should be run anyway when an "Immediate record" is made and, when sucessfully, update the "status" column from
glpi_plugin_printercounters_items_recordmodelstable accordly. I believe that this change is affecting the "PluginPrintercountersErrorItem" crontask from selecting printers to search.I believe that something is blocking the automatic execution from "PluginPrintercountersErrorItem" crontask, because it didn't run even after 48 hours, even with users accessing the GLPI normally.
URL of the page :
Screenshot of the problem (if pertinent) :