We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fusioninventory-agent Version 2.6 fusioninventory-for-glpi Version 10.0.6+1.1
I have two stacked H3C WX3520H
I can do the SNMP Inventory manually with fusioninventory-netinventory --debug and get the exported xml: WX3520H.xml.txt
But when I execute the inventory task from fusioninventory-for-glpi, only get the error:
[Sat Apr 1 16:03:06 2023][debug] [thread 2] #17, full match for sysobjectID .1.3.6.1.4.1.25506.1.1183 in database [Sat Apr 1 16:04:15 2023][error] [thread 2] #17, [http client] unknown content format
[Sat Apr 1 16:03:06 2023][debug] [thread 2] #17, full match for sysobjectID .1.3.6.1.4.1.25506.1.1183 in database
[Sat Apr 1 16:04:15 2023][error] [thread 2] #17, [http client] unknown content format
Anyone has any idea? Is there any other log or debug info i can look at?
Here's the snmpwalk output: WX3520H.walk.txt
The text was updated successfully, but these errors were encountered:
No branches or pull requests
fusioninventory-agent Version 2.6
fusioninventory-for-glpi Version 10.0.6+1.1
I have two stacked H3C WX3520H
I can do the SNMP Inventory manually with fusioninventory-netinventory --debug and get the exported xml:
WX3520H.xml.txt
But when I execute the inventory task from fusioninventory-for-glpi, only get the error:
[Sat Apr 1 16:03:06 2023][debug] [thread 2] #17, full match for sysobjectID .1.3.6.1.4.1.25506.1.1183 in database
[Sat Apr 1 16:04:15 2023][error] [thread 2] #17, [http client] unknown content format
Anyone has any idea? Is there any other log or debug info i can look at?
Here's the snmpwalk output:
WX3520H.walk.txt
The text was updated successfully, but these errors were encountered: