Open ejaecker opened 6 years ago
Hi,
Do you have the TAG plugin to install on your GLPI instance?
Thanks for replying. No, i don't have this plugin installed, is it a preqequisite to printercounters ?
No but there is a conflict between these two plugins and it generates SQL errors of the same type as the one reported.
Can you put a screenshot of the "Item records" page by putting yourself in debug mode?
here is the screen shot you asked for :
What plugins have you installed? Because we tried with a blank instance and no problems when consulting the history.
No other plugin installed. As i said on OP this is a Fresh 9.2 install with only Printercounters plugin.
My config is :
Operating system: Windows NT SRV2K16AZURE 10.0 build 14393 (Windows Server 2016) AMD64
PHP 7.2.2 cgi-fcgi (Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, calendar, cgi-fcgi, ctype, curl, date,
dom, fileinfo, filter, gd, hash, iconv, imap, json, ldap, libxml, mbstring, mysqli, mysqlnd, pcre, readline, session, snmp,
standard, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, zip, zlib)
Setup: max_execution_time="300" memory_limit="128M" post_max_size="8M" safe_mode="" session.save_handler="files" upload_max_filesize="2M"
Software: Microsoft-IIS/10.0 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
Server Software: MySQL Community Server (GPL) Server Version: 5.7.19-log Server SQL Mode: Parameters: root@localhost/glpi92 Host info: localhost via TCP/IP
--
Perhaps should i try with 9.2.2....
Hi, Can you test with the new release of the plugin to see if this problem is solved?
Hi, Just installed and configured this plugin (on a fresh vanilla glpi 9.2) snmp seems to work after a
immediate record
as toner levels show welland counters are well stored on table
glpi_plugin_printercounters_counters
but i just don't figure out how to see counters... Printers/Records/record History i still empty...no historical...
also clickin on
Add a manual record
orAdd a lower record
seems somewhat inefective.should it be of some help here is a backtrace :
and a slq-errors.log wich is fired upon accessing printer object
thanks in advance for any help.