Forum GLPI-Project

Emelman

Member

Registered: 2018-07-20

Posts: 9

GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

After updating GLPI 9.2.4 to version 9.3, it was found that in the tickets where the solutions were not approved, the dates of solutions were lost and the itself was doubled four times. With the help of the program "MySQL Workbench" in the table "glpi_itilsolutions" I found problem solutions and the "date_creation" field is equal to "NULL". I can change this value to the date from the "History" of the tickets, but three other duplicates remain without a date. I can't understand exactly where they were duplicated and how to remove them now?

KKAdmin

Member

From: Germany

Registered: 2010-03-05

Posts: 959

Re: GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

Please check the logs if you got a problem during migration

---

You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3

ktlpachonr

Member

Registered: 2017-06-01

Posts: 9

Re: GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

PLEASE HELP ME ..!

I have installed version 9.3 of GLPI, but it is not executing the automatic action correctly: queuednotificación , the ticktes are not created, automatically, it touches the recovery of the receiver manually and in this way, it complies with the creation of the ticktes.

We have read and tested all the solutions they have proposed, but it has not worked.

Please, if someone knows or has the solution, he is very grateful that you share it with us.

Thank you

LuisH

My environment is

GLPI versión 9.3.0
S.O. CENTOS
php 7.7
BD mariaDB

PD. I offer apologies for my English is not very good.

Emelman

Member

Registered: 2018-07-20

Posts: 9

Re: GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

Please check the logs if you got a problem during migration

I looked the logs and didn't find anything criminal.
migration_to_9.3.log

2018-07-18 17:15:29 [680@glpi-new]
3 минут 1 секунд for "Изменение структуры БД - glpi_itilsolutions" @ 2018-07-18 17:15:30 [325@glpi-new]
1 секунда for "Изменение структуры БД - glpi_itilsolutions" @ 2018-07-18 17:15:53 [325@glpi-new]
23 секунд for "Изменение структуры БД - glpi_itilsolutions" @ 2018-07-18 17:15:53 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_itilsolutions" @ 2018-07-18 17:16:00 [325@glpi-new]
7 секунд for "Изменение структуры БД - glpi_tickets" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_problems" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_changes" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_computermodels" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_monitormodels" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_networkequipmentmodels" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_peripheralmodels" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_states" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_locations" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_items_disks" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_users" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_authldaps" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Изменение структуры БД - glpi_computers_softwarelicenses" @ 2018-07-18 17:16:00 [325@glpi-new]
0 секунд for "Добавление полнотекстового индекса - glpi_knowbaseitemtranslations" @ 2018-07-18 17:16:03 [325@glpi-new]
3 секунд for "Добавление полнотекстового индекса - glpi_knowbaseitems" @ 2018-07-18 17:16:03 [325@glpi-new]
0 секунд for "Значения настроек добавлены для purge_computer_software_install, purge_software_computer_install, purge_software_version_install, purge_infocom_creation, purge_profile_user, purge_group_user, purge_adddevice, purge_updatedevice, purge_deletedevice, purge_connectdevice, purge_disconnectdevice, purge_userdeletedfromldap, purge_addrelation, purge_deleterelation, purge_createitem, purge_deleteitem, purge_restoreitem, purge_updateitem, purge_comments, purge_datemod, purge_all, purge_user_auth_changes, purge_plugins" @ 

sql-errors.log

[2018-07-18 17:15:29] glpisqllog.ERROR: DBmysql::query() in /var/www/glpi/inc/dbmysql.class.php line 180
  *** MySQL query error:
  SQL: ALTER TABLE `glpi_itilsolutions` DROP INDEX `migration_unicity` 
  Error: Can't DROP 'migration_unicity'; check that column/key exists
  Backtrace :
  inc/dbmysql.class.php:209                          
  inc/migration.class.php:657                        DBmysql->queryOrDie()
  install/update_92_93.php:195                       Migration->migrationOneTable()
  inc/update.class.php:422                           update92to93()
  install/update.php:460                             Update->doUpdates()
  install/update.php:573                             doUpdateDb()
  {"user":"680@glpi-new","mem_usage":"180.732\", 2.07Mio)"} 
[2018-07-18 17:15:29] glpisqllog.ERROR: DBmysql::query() in /var/www/glpi/inc/dbmysql.class.php line 180
  *** MySQL query error:
  SQL: ALTER TABLE `glpi_itilsolutions` DROP INDEX `migration_unicity` 
  Error: Can't DROP 'migration_unicity'; check that column/key exists
  Backtrace :
  inc/dbmysql.class.php:209                          
  inc/migration.class.php:657                        DBmysql->queryOrDie()
  install/update_92_93.php:195                       Migration->migrationOneTable()
  inc/update.class.php:422                           update92to93()
  install/update.php:460                             Update->doUpdates()
  install/update.php:573                             doUpdateDb()
  {"user":"@glpi-new","mem_usage":"93.646\", 1.83Mio)"} 

The table "glpi_itilsolutions" really doesn't have a column "migration_unicity". And what I have to do? Create it?
New tickets created after the migration, don't have any problems.

KKAdmin

Member

From: Germany

Registered: 2010-03-05

Posts: 959

Re: GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

I believe you have this bug https://github.com/glpi-project/glpi/issues/4315 from 9.3.0

---

You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3

Emelman

Member

Registered: 2018-07-20

Posts: 9

Re: GLPI 9.2.4 -> 9.3 - Duplication of disapproved solutions

I apologize for not responding for a long time. I went to the hospital.

I believe you have this bug https://github.com/glpi-project/glpi/issues/4315 from 9.3.0

We do not have this problem. We do not have the table "glp_solutions", but similar errors are not registered in "sql-ervors.log".
I managed to find duplicate solutions in the table "glp_itilsolutions". The earliest solution was registered with ID 196609, and duplicates of problem solutions were with random IDs with a much smaller serial number.
As a result, it was not possible to find out the cause of this bug and the ways of its automatic correction. All duplicate solutions I deleted manually. So the ticket can be closed.