-
Notifications
You must be signed in to change notification settings - Fork 62
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
Page Code Trouble in inventory #44
Comments
I also found this log for the same inventory period! GLPI sql-errors.log[2022-01-06 11:03:10] glpisqllog.ERROR: DBmysql::query() in /usr/share/glpi/src/DBmysql.php line 352 *** MySQL query error: SQL: INSERT INTO `glpi_devicefirmwares` (`date`, `version`, `manufacturers_id`, `designation`, `devicefirmwaretypes_id`, `date_creation`, `date_mod`) VALUES ('2021-16-08', 'GL703GM.314', '2', 'American Megatrends Inc. BIOS', '1', '2022-01-06 11:03:08', '2022-01-06 11:03:08') Error: Incorrect date value: '2021-16-08' for column `glpi_db`.`glpi_devicefirmwares`.`date` at row 1 Backtrace : src/DBmysql.php:1180 src/CommonDBTM.php:652 DBmysql->insert() src/CommonDBTM.php:1242 CommonDBTM->addToDB() src/CommonDevice.php:482 CommonDBTM->add() src/Inventory/Asset/Device.php:113 CommonDevice->import() src/Inventory/Asset/Bios.php:85 Glpi\Inventory\Asset\Device->handle() src/Inventory/Asset/MainAsset.php:751 Glpi\Inventory\Asset\Bios->handle() src/Inventory/Asset/MainAsset.php:672 Glpi\Inventory\Asset\MainAsset->handleAssets() src/RuleImportAsset.php:954 Glpi\Inventory\Asset\MainAsset->rulepassed() src/Rule.php:1496 RuleImportAsset->executeActions() src/RuleCollection.php:1583 Rule->process() src/Inventory/Asset/MainAsset.php:515 RuleCollection->processAllRules() src/Inventory/Inventory.php:674 Glpi\Inventory\Asset\MainAsset->handle() src/Inventory/Inventory.php:324 Glpi\Inventory\Inventory->handleItem() src/Inventory/Request.php:318 Glpi\Inventory\Inventory->doInventory() src/Inventory/Request.php:83 Glpi\Inventory\Request->inventory() src/Agent/Communication/AbstractRequest.php:292 Glpi\Inventory\Request->handleAction() src/Agent/Communication/AbstractRequest.php:212 Glpi\Agent\Communication\AbstractRequest->handleJSONRequest() front/inventory.php:57 Glpi\Agent\Communication\AbstractRequest->handleRequest() |
Hi @Jagor |
can you test with latest GLPI-Agent nightly build as 2559b0b should probably fix this problem ? |
Hi, GLPI-Agent v1.1-git3042142e fixes Cyrillic rendering issue, thanks. |
Hello / Bonsoir @g-bougard, GLPI 10 master.72d9190 + GLPI-Agent-1.1-git3042142e-x64 work fine with french rendering issue too, " Merci beaucoup :-) " |
I'm closing the issue as I released today GLPI-Agent v1.1. |
Bug reporting acknowledgment
Yes, I read it
Professional support
I still have but want a public following to keep the community aware
Describe the bug
GLPI-Agent (MS-Windows x64) inventories send with page code char anomaly.
To reproduce
Fresh GLPI 10 beta installation ( GLPI master.0f54d02 nightly builds ) in french environment
Run fine
Latest Windows x64 GLPI Agent ( GLPI-Agent-1.1-git31840f5c-x64.msi nightly builds ) in french environment
Inventory planned has system service and run fine => computer is created in GLPI.
Some Assets, like " Software " returns with some text with diacritical characters (see screen capture bellow).
Informations sur le système, l'installation et la configuration
Server
GLPI constants
Libraries
SQL replicas
Notifications
Plugins list
GLPI MariaDB Database build with : CHARACTER SET utf8 COLLATE utf8_general_ci
Log files
glpi-agent.log debug Level 1 log file
GLPI php-errors.log
Expected behavior
The problem is the same with manual agent inventory, from an administrator elevated PowerShell terminal, even with an active code page 65001 (UTF-8).
Texts should be displayed in UTF-8 with the correct diacritics
Operating system
Windows
GLPI Agent version
Nightly build (git version in additional context below)
GLPI version
10.0.0-beta, development release (See additional context below)
GLPIInventory plugin or FusionInventory for GLPI plugin version
Not applicable
Additional context
No response
The text was updated successfully, but these errors were encountered: