-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
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
Agent not create new computer #235
Comments
Hi @NicolasPHP please configure your agent with debug=2 in registry and restart the service. |
Hi @g-bougard I found nothing about this error in other sections of the glpi github. In the agent log, before is the complete inventory, and the lines after are :
Here the full stack on server side error log
|
It seems related to software import. Can you share the full output of the following command ?
You should anonymize personal datas under "content" -> "operatingsystem" node. |
|
I cannot reproduce on latest GLPI nightly build, your issue should already have been fixed. |
Bug reporting acknowledgment
Yes, I read it
Professional support
Yes, I know
Describe the bug
Hello,
GLPI Agent don't create computer into GLPI.
The GLPI Agent is correctly created in GLPI, but not the computer.
On the computer, glpi-agent.log contains the following error line :
[Wed Oct 12 18:10:21 2022][error] [http client] communication error: 500 Internal Server Error
On the server, php-errors.log contains the following error line :
[2022-10-12 18:10:21] glpiphplog.ERROR: *** PHP User Error (256): Column 'manufacturers_id' cannot be null in /var/www/glpi/src/DBmysql.php at line 1961
Test on several computers : same problem
Delete agent in GLPI change nothing
Reseting rules for import change nothing
To reproduce
Install a new agent
Force an inventory
Expected behavior
Creation of a new computer linked with the agent
Operating system
Windows
GLPI Agent version
1.4
GLPI version
10.0.3
GLPIInventory plugin or FusionInventory for GLPI plugin version
1.0.4
Additional context
No response
The text was updated successfully, but these errors were encountered: