You are not logged in.

Announcement

 Téléchargez la dernière version stable de GLPI      -     Et vous, que pouvez vous faire pour le projet GLPI ? :  Contribuer
 Download last stable version of GLPI                      -     What can you do for GLPI ? :  Contribute

#1 2017-06-01 16:07:46

didimons
Member
Registered: 2015-03-09
Posts: 6

root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

After the upgrade from GLPI 0.90.1 to 9.1.3 the root entity page ( under administration - entities - root entity ) is completely blank
I'm not sure how to reslove this problem

Same problem with all of our assets, e.g. I can see the list with inventoried PC's but when you click on them you get a blank page.

Any help would be appreciated

Offline

#2 2017-06-01 16:57:25

eric.le-corre
Member
Registered: 2013-01-07
Posts: 1,005

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

do you have plugin ?

if yes, disable plugin or update

Offline

#3 2017-06-01 17:03:44

didimons
Member
Registered: 2015-03-09
Posts: 6

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

fusioninventory plugin was disabled during upgrade, after upgrade it was updateed to the latest version and activated

Offline

#4 2017-06-01 17:10:04

eric.le-corre
Member
Registered: 2013-01-07
Posts: 1,005

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

active the debug mode in preference

Offline

#5 2017-06-01 18:47:08

yllen
GLPI-DEV
From: Sillery (51)
Registered: 2008-01-14
Posts: 15,278

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

Do you have some errors in GLPI logs? in apache logs?
Have you some tebles to repair in your database?


CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

Offline

#6 2017-06-01 20:35:31

didimons
Member
Registered: 2015-03-09
Posts: 6

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

Eric,

how do I activate debug mode?

-----------------------------------------------------------------

Yllen,

How can you check if there are tables in need of repair?

Concerning the log files:

found the following error in mysql.log:

170601 22:18:52 [Note] Plugin 'FEDERATED' is disabled.
170601 22:18:52 InnoDB: The InnoDB memory heap is disabled
170601 22:18:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170601 22:18:52 InnoDB: Compressed tables use zlib 1.2.8
170601 22:18:52 InnoDB: Using Linux native AIO
170601 22:18:52 InnoDB: Initializing buffer pool, size = 128.0M
170601 22:18:52 InnoDB: Completed initialization of buffer pool
170601 22:18:52 InnoDB: highest supported file format is Barracuda.
170601 22:18:52  InnoDB: Waiting for the background threads to start
170601 22:18:53 InnoDB: 5.5.55 started; log sequence number 1595705
170601 22:18:53 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170601 22:18:53 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
170601 22:18:53 [Note] Server socket created on IP: '127.0.0.1'.
170601 22:18:53 [Note] Event Scheduler: Loaded 0 events
170601 22:18:53 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.55-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
170601 22:18:54 [ERROR] /usr/sbin/mysqld: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
170601 22:18:54 [ERROR] /usr/sbin/mysqld: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
(END)


In apache2 error.log:

[Thu Jun 01 22:18:52.215613 2017] [:error] [pid 660] python_init: Python version mismatch, expected '2.7.5+', found '2.7.9'.
[Thu Jun 01 22:18:52.217993 2017] [:error] [pid 660] python_init: Python executable found '/usr/bin/python'.
[Thu Jun 01 22:18:52.218011 2017] [:error] [pid 660] python_init: Python path being used '/usr/lib/python2.7/:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
[Thu Jun 01 22:18:52.218023 2017] [:notice] [pid 660] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
[Thu Jun 01 22:18:52.218026 2017] [:notice] [pid 660] mod_python: using mutex_directory /tmp
[Thu Jun 01 22:18:52.246529 2017] [mpm_prefork:notice] [pid 660] AH00163: Apache/2.4.10 (Debian) mod_python/3.3.1 Python/2.7.9 OpenSSL/1.0.1t mod_perl/2.0.9dev Perl/v5.20.2 configured -- resuming normal operations
[Thu Jun 01 22:18:52.246580 2017] [core:notice] [pid 660] AH00094: Command line: '/usr/sbin/apache2'
[Thu Jun 01 22:26:41.267180 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP Fatal error:  Call to a member function fetch_assoc() on boolean in /var/www/glpi/inc/dbmysql.class.php on line 308, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267200 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP Stack trace:, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267208 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   1. {main}() /var/www/glpi/front/computer.form.php:0, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267214 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   2. CommonGLPI->display() /var/www/glpi/front/computer.form.php:107, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267220 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   3. CommonGLPI->showTabsContent() /var/www/glpi/inc/commonglpi.class.php:1152, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267225 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   4. CommonGLPI->defineAllTabs() /var/www/glpi/inc/commonglpi.class.php:707, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267230 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   5. Computer->defineTabs() /var/www/glpi/inc/commonglpi.class.php:158, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267234 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   6. CommonGLPI->addStandardTab() /var/www/glpi/inc/computer.class.php:132, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267239 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   7. Log->getTabNameForItem() /var/www/glpi/inc/commonglpi.class.php:208, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267243 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   8. countElementsInTable() /var/www/glpi/inc/log.class.php:93, referer: http://192.168.0.11/front/computer.php
[Thu Jun 01 22:26:41.267248 2017] [:error] [pid 2130] [client 192.168.0.89:58886] PHP   9. DBmysql->fetch_assoc() /var/www/glpi/inc/db.function.php:320, referer: http://192.168.0.11/front/computer.php
(END)

In the SQL errors.log:

  SQL: SELECT COUNT(*) AS cpt
             FROM `glpi_logs` WHERE itemtype = \'Entity\'
                                          AND items_id = \'0\'
  Error: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
  Backtrace :
  inc/db.function.php:319
  inc/log.class.php:93                               countElementsInTable()
  inc/commonglpi.class.php:208                       Log->getTabNameForItem()
  inc/entity.class.php:298                           CommonGLPI->addStandardTab()
  inc/commonglpi.class.php:158                       Entity->defineTabs()
  inc/commonglpi.class.php:707                       CommonGLPI->defineAllTabs()
  inc/commonglpi.class.php:1152                      CommonGLPI->showTabsContent()
  front/dropdown.common.form.php:132                 CommonGLPI->display()
  front/entity.form.php:48                           include()
2017-06-01 17:59:57 [2@lamp]
  *** MySQL query error:
  SQL: INSERT INTO `glpi_logs`
                       (`items_id`, `itemtype`, `itemtype_link`, `linked_action`, `user_name`,
                        `date_mod`, `id_search_option`, `old_value`, `new_value`)
                VALUES (\'2\', \'User\', \'\', \'0\',
                        \'glpi (2)\', \'2017-06-01 17:59:57\', \'17\',
                        \'nl_NL\', \'NULL\')
  Error: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
  Backtrace :
  inc/log.class.php:240
  inc/log.class.php:179                              Log::history()
  inc/commondbtm.class.php:381                       Log::constructHistory()
  inc/commondbtm.class.php:1146                      CommonDBTM->updateInDB()
  front/preference.php:60                            CommonDBTM->update()
2017-06-01 18:00:06 [2@lamp]
  *** MySQL query error:
  SQL: SELECT COUNT(*) AS cpt
             FROM `glpi_logs` WHERE itemtype = \'Entity\'
                                          AND items_id = \'0\'
  Error: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
  Backtrace :
  inc/db.function.php:319
  inc/log.class.php:93                               countElementsInTable()
  inc/commonglpi.class.php:208                       Log->getTabNameForItem()
  inc/entity.class.php:298                           CommonGLPI->addStandardTab()
  inc/commonglpi.class.php:158                       Entity->defineTabs()
  inc/commonglpi.class.php:707                       CommonGLPI->defineAllTabs()
  inc/commonglpi.class.php:1152                      CommonGLPI->showTabsContent()
  front/dropdown.common.form.php:132                 CommonGLPI->display()
  front/entity.form.php:48                           include()
2017-06-01 22:26:41 [2@lamp]
  *** MySQL query error:
  SQL: SELECT COUNT(*) AS cpt
             FROM `glpi_logs` WHERE itemtype = \'Computer\'
                                          AND items_id = \'20\'
  Error: Table './glpi/glpi_logs' is marked as crashed and last (automatic?) repair failed
  Backtrace :
  inc/db.function.php:319
  inc/log.class.php:93                               countElementsInTable()
  inc/commonglpi.class.php:208                       Log->getTabNameForItem()
  inc/computer.class.php:132                         CommonGLPI->addStandardTab()
  inc/commonglpi.class.php:158                       Computer->defineTabs()
  inc/commonglpi.class.php:707                       CommonGLPI->defineAllTabs()
  inc/commonglpi.class.php:1152                      CommonGLPI->showTabsContent()
  front/computer.form.php:107                        CommonGLPI->display()
(END)

Offline

#7 2017-06-01 21:14:07

didimons
Member
Registered: 2015-03-09
Posts: 6

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

Managed to solve the problem by performing the following steps:
service mysql stop
cd /var/lib/mysql/glpi
myisamchk -r -v -f  glpi_logs
service mysql start

everything is now working smile

I do want to be able to prevent this if possible. I cloned my live machine to a vm in order to test the upgrade and I'd like to avoid this issue with the upgrade of my live machine.
Any hints on how to avoid this would be appreciated.

Last edited by didimons (2017-06-01 21:26:38)

Offline

#8 2017-06-06 11:48:42

yllen
GLPI-DEV
From: Sillery (51)
Registered: 2008-01-14
Posts: 15,278

Re: root entity page empty after upgrade from GLPI 0.90.1 to 9.1.3

Repair table crashed is a job for your DBA administrator.


CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

Offline

Board footer

Powered by FluxBB