Passage en V4 loupé

Bonjour à tous,

Je possède un rpi3 +ssd(msata) avec Jeedom V3.
J’ai voulu passer sur la V4, après un essai sur mon Synology (Docker) concluant.

Lors de la mise à jour, le rpi est resté bloqué pendant plusieurs heures, sans finir l’installation.
Je l’ai relancé et, bien évidemment, Jeedom ne fonctionne plus.
18

Est-ce rattrapable ou dois-je tout réinstaller ?
J’ai bien évidemment une sauvegarde de Jeedom V3 du rpi3.

Edit: Merci Franck!
J’ai suivi la méthode de @Loic, SSH en root et envoyer la commande:
php /var/www/html/install/database.php

Bonjour
Regarde la documentation pour remonter des bugs ça te dira exactement ce qu’il faut nous remonter pour qu’on puisse te fournir une aide précise et rapide

Je n’ai plus aucun accès à Jeedom…
F12 ne fonctionne pas (je suis sur mac).

Par contre, j’ai accès en SSH au rpi3.
Mais je ne sais pas où sont les logs de Jeedom

C’est dans /var/www/HTML/logs

Merci Loic,

Voici la copie du log de l’update:

[START UPDATE]
****Update from 3.3.38 (2019-12-07 19:14:47)****
Parameters : {"preUpdate":"0","backup::before":"1","plugins":"1","core":"1","force":"0","update::reapply":""}
Send begin of update event...OK
Check update...
OK
Check rights...
OK
[START BACKUP]
***************Start of Jeedom backup at 2019-12-07 19:14:53***************
Envoi l'évènement de début de sauvegarde...OK
Vérification des droits sur les fichiers...
OK
Vérification de la base de données...
OK
Sauvegarde la base de données...
OK
Persistance du cache : 
OK
Création de l'archive...
OK
Nettoyage de l'ancienne sauvegarde...OK
Limitation de la taille des sauvegardes à 500 Mo...
OK
Nom de la sauvegarde : /var/www/html/core/php/../../backup/backup-Jeedom_RPI3-3.3.38-2019-12-07-19h14.tar.gz
Vérification des droits sur les fichiers...
OK
Envoi l'évènement de fin de sauvegarde...OK
Durée de la sauvegarde : 76s
***************Fin de la sauvegarde de Jeedom***************
[END BACKUP SUCCESS]
Disable all task
.. OK
Disable all scenario........... OK
Download url : https://github.com/jeedom/core/archive/V4-stable.zip
Download in progress...--2019-12-07 18:16:11--  https://github.com/jeedom/core/archive/V4-stable.zip
Resolving github.com (github.com)... 140.82.118.4
Connecting to github.com (github.com)|140.82.118.4|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/jeedom/core/zip/V4-stable [following]
--2019-12-07 18:16:12--  https://codeload.github.com/jeedom/core/zip/V4-stable
Resolving codeload.github.com (codeload.github.com)... 140.82.114.9
Connecting to codeload.github.com (codeload.github.com)|140.82.114.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 45795278 (44M) [application/zip]
Saving to: '/tmp/jeedom/install/jeedom_update.zip'

     0K ........ ........ ..
...... ........ ........ ........  6%  278K 2m30s
  3072K .
......
. ...
..... ..
.....
. ...
..... ........ ........ 13%  258K 2m24s
  6144K ........ ........ ........ .....
... ........ ........ 20%  369K 2m0s
  9216K .
....... .....
... ...
..... ........ ........ ........ 27%  350K 1m46s
 12288K ........ .
....
... ........ .......
. ..
...
... .
...
...
. 34%  220K 1m43s
 15360K ........ ...
...
.. ...
..... ........
 ......
.. .....
... 41%  209K 98s
 18432K ........
 ........
 .......
. ...
...
.. ....
.... .
...
.... 48%  204K 90s
 21504K ........ .....
... ........ ........ .....
... ........ 54%  237K 79s
 24576K .
....... ........ ........ ....
.... .
.......
 ........ 61%  198K 69s

 27648K ........ ..
...... .....
... ........ ........ ........ 68%  510K 54s
 30720K ......
.. .....
... .....
... .
.....
.. ....
.... .......
. 75%  265K 42s
 33792K ...
..... ........ .......
. ...
....
. ..
......
 ....
.... 82%  199K 31s
 36864K ..
...... .......
. ......
.. ........
 ......
.. .......
. 89%  383K 18s
 39936K .....
... ...
..... ..
....
.. ...
.....
 .....
... ..
....
.. 96%  265K 7s
 43008K ..
....
.. .
....
... ....
.... ..
                        100%  226K=2m53s

2019-12-07 18:19:06 (259 KB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [45795278/45795278]

OK
Cleaning folders...OK
Create temporary folder...OK
Unzip in progress...
OK
Clean temporary files (tmp)...OK
Moving files...
OK
Remove temporary files...OK
Update system into : 3.4.0...Suppression theme /var/www/html/install/update/../../core/themes/amber/Suppression theme /var/www/html/install/update/../../core/themes/blue/Suppression theme /var/www/html/install/update/../../core/themes/blue_grey/Suppression theme /var/www/html/install/update/../../core/themes/bootable/Suppression theme /var/www/html/install/update/../../core/themes/brown/Suppression theme /var/www/html/install/update/../../core/themes/cyan/Suppression theme /var/www/html/install/update/../../core/themes/darksobre/Suppression theme /var/www/html/install/update/../../core/themes/deep_orange/Suppression theme /var/www/html/install/update/../../core/themes/deep_purple/Suppression theme /var/www/html/install/update/../../core/themes/green/Suppression theme /var/www/html/install/update/../../core/themes/grey/Suppression theme /var/www/html/install/update/../../core/themes/light_blue/Suppression theme /var/www/html/install/update/../../core/themes/light_green/Suppression theme /var/www/html/install/update/../../core/themes/lime/Suppression theme /var/www/html/install/update/../../core/themes/orange/Suppression theme /var/www/html/install/update/../../core/themes/pink/Suppression theme /var/www/html/install/update/../../core/themes/purple/Suppression theme /var/www/html/install/update/../../core/themes/red/Suppression theme /var/www/html/install/update/../../core/themes/teal/Suppression theme /var/www/html/install/update/../../core/themes/yellow/OK
Update system into : 4.0.1...
OK
Update system into : 4.0.2...
OK
Update system into : 4.0.3...Copy widget of plugin widget to jeedom custom widget dir...OK
Update system into : 4.0.4...
OK
Update system into : 4.0.5...
OK
Update system into : 4.0.6...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
dpkg-preconfigure: unable to re-open stdin: 

C’est pas l’update qu’il faut mais la http.error

Désolé.
Voici le http.error:

#0 /var/www/html/core/class/DB.class.php(41): PDO->__construct('mysql:host=loca...', 'jeedom', '8eb063558b4aafb', Array)
#1 /var/www/html/core/class/DB.class.php(54): DB->__construct()
#2 /var/www/html/core/class/DB.class.php(86): DB::getConnection()
#3 /var/www/html/core/class/config.class.php(145): DB::Prepare('SELECT `value`
...', Array, 0)
#4 /var/www/html/core/class/jeedom.class.php(361): config::byKey('api', 'core')
#5 /var/www/html/core/class/jeedom.class.php(405): jeedom::getApiKey('core')
#6 /var/www/html/core/class/jeedom.class.php(399): jeedom::apiAccess('ec8TJKglOCC6E4Z...')
#7 /var/www/html/plugins/xiaomihome/core/php/jeeXiaomiHome.php(21): jeedom::apiAccess('ec8TJKglOCC6E4Z...', 'xiaomihome')
#8 {main}
  thrown in /var/www/html/core/class/DB.class.php on line 41
[Tue Apr 16 11:31:48.339985 2019] [:error] [pid 30030] [client 127.0.0.1:52210] PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000] [2002] No such file or directory in /var/www/html/core/class/DB.class.php:41
Stack trace:
#0 /var/www/html/core/class/DB.class.php(41): PDO->__construct('mysql:host=loca...', 'jeedom', '8eb063558b4aafb', Array)
#1 /var/www/html/core/class/DB.class.php(54): DB->__construct()
#2 /var/www/html/core/class/DB.class.php(86): DB::getConnection()
#3 /var/www/html/core/class/config.class.php(145): DB::Prepare('SELECT `value`
...', Array, 0)
#4 /var/www/html/core/class/jeedom.class.php(361): config::byKey('api', 'core')
#5 /var/www/html/core/class/jeedom.class.php(405): jeedom::getApiKey('core')
#6 /var/www/html/core/class/jeedom.class.php(399): jeedom::apiAccess('ec8TJKglOCC6E4Z...')
#7 /var/www/html/plugins/xiaomihome/core/php/jeeXiaomiHome.php(21): jeedom::apiAccess('ec8TJKglOCC6E4Z...', 'xiaomihome')
#8 {main}
  thrown in /var/www/html/core/class/DB.class.php on line 41
[Tue Apr 16 11:31:48.353904 2019] [:error] [pid 30093] [client 127.0.0.1:52212] PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000] [2002] No such file or directory in /var/www/html/core/class/DB.class.php:41
Stack trace:
#0 /var/www/html/core/class/DB.class.php(41): PDO->__construct('mysql:host=loca...', 'jeedom', '8eb063558b4aafb', Array)
#1 /var/www/html/core/class/DB.class.php(54): DB->__construct()
#2 /var/www/html/core/class/DB.class.php(86): DB::getConnection()
#3 /var/www/html/core/class/config.class.php(145): DB::Prepare('SELECT `value`
...', Array, 0)
#4 /var/www/html/core/class/jeedom.class.php(361): config::byKey('api', 'core')
#5 /var/www/html/core/class/jeedom.class.php(405): jeedom::getApiKey('core')
#6 /var/www/html/core/class/jeedom.class.php(399): jeedom::apiAccess('ec8TJKglOCC6E4Z...')
#7 /var/www/html/plugins/xiaomihome/core/php/jeeXiaomiHome.php(21): jeedom::apiAccess('ec8TJKglOCC6E4Z...', 'xiaomihome')
#8 {main}
  thrown in /var/www/html/core/class/DB.class.php on line 41
[Tue Apr 16 11:31:48.367268 2019] [:error] [pid 30031] [client 127.0.0.1:52214] PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000] [2002] No such file or directory in /var/www/html/core/class/DB.class.php:41
Stack trace:
#0 /var/www/html/core/class/DB.class.php(41): PDO->__construct('mysql:host=loca...', 'jeedom', '8eb063558b4aafb', Array)
#1 /var/www/html/core/class/DB.class.php(54): DB->__construct()
#2 /var/www/html/core/class/DB.class.php(86): DB::getConnection()
#3 /var/www/html/core/class/config.class.php(145): DB::Prepare('SELECT `value`
...', Array, 0)
#4 /var/www/html/core/class/jeedom.class.php(361): config::byKey('api', 'core')
#5 /var/www/html/core/class/jeedom.class.php(405): jeedom::getApiKey('core')
#6 /var/www/html/core/class/jeedom.class.php(399): jeedom::apiAccess('ec8TJKglOCC6E4Z...')
#7 /var/www/html/plugins/xiaomihome/core/php/jeeXiaomiHome.php(21): jeedom::apiAccess('ec8TJKglOCC6E4Z...', 'xiaomihome')
#8 {main}
  thrown in /var/www/html/core/class/DB.class.php on line 41
[Wed Apr 17 11:50:19.023255 2019] [:error] [pid 19270] [client 192.168.1.15:50147] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/camera/3rdparty/ponvif.php:1040
Stack trace:
#0 /var/www/html/plugins/camera/3rdparty/ponvif.php(1088): Ponvif->_xml2array('<?xml version="...')
#1 /var/www/html/plugins/camera/3rdparty/ponvif.php(209): Ponvif->_send_request('http://192.168....', '<s:Envelope xml...')
#2 /var/www/html/plugins/camera/3rdparty/ponvif.php(178): Ponvif->core_GetSystemDateAndTime()
#3 /var/www/html/plugins/camera/core/class/camera.class.php(288): Ponvif->initialize()
#4 /var/www/html/plugins/camera/core/class/camera.class.php(582): camera->configOnvif()
#5 /var/www/html/plugins/camera/core/class/camera.class.php(339): camera->applyModuleConfiguration()
#6 /var/www/html/core/class/DB.class.php(202): camera->postSave()
#7 /var/www/html/core/class/eqLogic.class.php(984): DB::save(Object(camera), false)
#8 /var/www/html/core/ajax/eqLogic.ajax.php(343): eqLogic->save()
#9 {main}
  thrown in /var/www/html/plugins/camera/3rdparty/ponvif.php on line 1040, referer: http://192.168.1.30/index.php?v=d&p=camera&m=camera&id=65
[Wed Apr 17 12:10:09.140635 2019] [core:notice] [pid 30016] AH00052: child pid 30032 exit signal Bus error (7)
[Wed Apr 17 12:10:09.140960 2019] [core:notice] [pid 30016] AH00052: child pid 19270 exit signal Bus error (7)
[Wed Apr 17 12:10:09.141469 2019] [core:notice] [pid 30016] AH00052: child pid 16914 exit signal Bus error (7)
[Wed Apr 17 12:10:09.141860 2019] [mpm_prefork:notice] [pid 30016] AH00169: caught SIGTERM, shutting down
[Wed Apr 17 12:10:19.072272 2019] [mpm_prefork:notice] [pid 517] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Apr 17 12:10:19.075120 2019] [core:notice] [pid 517] AH00094: Command line: '/usr/sbin/apache2'
[Wed Apr 17 14:44:43.457583 2019] [:error] [pid 1293] [client 192.168.1.15:58493] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/camera/3rdparty/ponvif.php:1040
Stack trace:
#0 /var/www/html/plugins/camera/3rdparty/ponvif.php(1088): Ponvif->_xml2array('<?xml version="...')
#1 /var/www/html/plugins/camera/3rdparty/ponvif.php(209): Ponvif->_send_request('http://192.168....', '<s:Envelope xml...')
#2 /var/www/html/plugins/camera/3rdparty/ponvif.php(178): Ponvif->core_GetSystemDateAndTime()
#3 /var/www/html/plugins/camera/core/class/camera.class.php(288): Ponvif->initialize()
#4 /var/www/html/plugins/camera/core/class/camera.class.php(582): camera->configOnvif()
#5 /var/www/html/plugins/camera/core/class/camera.class.php(339): camera->applyModuleConfiguration()
#6 /var/www/html/core/class/DB.class.php(202): camera->postSave()
#7 /var/www/html/core/class/eqLogic.class.php(984): DB::save(Object(camera), false)
#8 /var/www/html/core/ajax/eqLogic.ajax.php(343): eqLogic->save()
#9 {main}
  thrown in /var/www/html/plugins/camera/3rdparty/ponvif.php on line 1040, referer: http://192.168.1.30/index.php?v=d&p=camera&m=camera&id=65
warning: commands will be executed using /bin/sh
job 10 at Wed Apr 17 18:24:00 2019
warning: commands will be executed using /bin/sh
job 11 at Wed Apr 17 18:55:00 2019
[Sun Apr 21 19:17:05.543535 2019] [mpm_prefork:notice] [pid 490] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sun Apr 21 19:17:05.549242 2019] [core:notice] [pid 490] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 12 at Thu Apr 25 18:36:00 2019
[Wed May 08 10:17:06.342164 2019] [mpm_prefork:notice] [pid 475] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed May 08 10:17:06.345127 2019] [core:notice] [pid 475] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 13 at Wed May  8 17:46:00 2019
[Tue May 21 18:17:06.491785 2019] [mpm_prefork:notice] [pid 479] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Tue May 21 18:17:06.503825 2019] [core:notice] [pid 479] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 14 at Tue May 21 19:16:00 2019
[Tue May 21 19:17:06.506059 2019] [mpm_prefork:notice] [pid 502] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Tue May 21 19:17:06.516709 2019] [core:notice] [pid 502] AH00094: Command line: '/usr/sbin/apache2'
[Wed May 22 19:17:05.704849 2019] [mpm_prefork:notice] [pid 491] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed May 22 19:17:05.709496 2019] [core:notice] [pid 491] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 15 at Thu May 23 22:48:00 2019
[Fri May 24 12:17:07.050400 2019] [mpm_prefork:notice] [pid 525] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Fri May 24 12:17:07.053446 2019] [core:notice] [pid 525] AH00094: Command line: '/usr/sbin/apache2'
[Wed Jun 12 13:17:05.925881 2019] [mpm_prefork:notice] [pid 515] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Jun 12 13:17:05.929294 2019] [core:notice] [pid 515] AH00094: Command line: '/usr/sbin/apache2'
[Mon Jun 17 04:17:05.685687 2019] [mpm_prefork:notice] [pid 500] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Jun 17 04:17:05.686761 2019] [core:notice] [pid 500] AH00094: Command line: '/usr/sbin/apache2'
[Mon Jun 17 21:17:05.815220 2019] [mpm_prefork:notice] [pid 511] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Jun 17 21:17:05.816204 2019] [core:notice] [pid 511] AH00094: Command line: '/usr/sbin/apache2'
[Sat Jun 22 06:17:06.738093 2019] [mpm_prefork:notice] [pid 504] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Jun 22 06:17:06.739108 2019] [core:notice] [pid 504] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 16 at Wed Jul 10 15:28:00 2019
[Wed Jul 10 15:43:50.177248 2019] [core:notice] [pid 504] AH00052: child pid 1413 exit signal Bus error (7)
[Wed Jul 10 15:43:50.193489 2019] [core:notice] [pid 504] AH00052: child pid 24542 exit signal Bus error (7)
[Wed Jul 10 15:43:50.196767 2019] [core:notice] [pid 504] AH00052: child pid 26903 exit signal Bus error (7)
[Wed Jul 10 15:43:50.197834 2019] [core:notice] [pid 504] AH00052: child pid 29703 exit signal Bus error (7)
[Wed Jul 10 15:43:51.202654 2019] [mpm_prefork:notice] [pid 504] AH00169: caught SIGTERM, shutting down
[Wed Jul 10 15:43:58.672844 2019] [mpm_prefork:notice] [pid 499] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Jul 10 15:43:58.676529 2019] [core:notice] [pid 499] AH00094: Command line: '/usr/sbin/apache2'
[Thu Jul 25 08:17:05.662539 2019] [mpm_prefork:notice] [pid 489] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Thu Jul 25 08:17:05.665293 2019] [core:notice] [pid 489] AH00094: Command line: '/usr/sbin/apache2'
[Fri Jul 26 19:17:05.667882 2019] [mpm_prefork:notice] [pid 508] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Fri Jul 26 19:17:05.670951 2019] [core:notice] [pid 508] AH00094: Command line: '/usr/sbin/apache2'
[Fri Jul 26 20:17:05.839708 2019] [mpm_prefork:notice] [pid 511] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Fri Jul 26 20:17:05.841878 2019] [core:notice] [pid 511] AH00094: Command line: '/usr/sbin/apache2'
[Sat Aug 03 10:37:26.707885 2019] [core:notice] [pid 511] AH00052: child pid 17099 exit signal Bus error (7)
[Sat Aug 03 10:37:27.027015 2019] [core:notice] [pid 511] AH00052: child pid 31375 exit signal Bus error (7)
[Sat Aug 03 10:37:27.028280 2019] [core:notice] [pid 511] AH00052: child pid 30240 exit signal Bus error (7)
[Sat Aug 03 10:37:27.028983 2019] [mpm_prefork:notice] [pid 511] AH00169: caught SIGTERM, shutting down
[Sat Aug 03 10:37:34.956137 2019] [mpm_prefork:notice] [pid 481] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Aug 03 10:37:34.968151 2019] [core:notice] [pid 481] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 17 at Sat Aug  3 12:32:00 2019
[Mon Aug 05 15:33:24.317741 2019] [core:notice] [pid 481] AH00052: child pid 27395 exit signal Bus error (7)
[Mon Aug 05 15:33:24.337980 2019] [core:notice] [pid 481] AH00052: child pid 1211 exit signal Bus error (7)
[Mon Aug 05 15:33:25.340252 2019] [mpm_prefork:notice] [pid 481] AH00169: caught SIGTERM, shutting down
[Mon Aug 05 15:33:32.709818 2019] [mpm_prefork:notice] [pid 484] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Aug 05 15:33:32.712442 2019] [core:notice] [pid 484] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 18 at Mon Aug  5 15:52:00 2019
[Thu Aug 08 09:09:51.668045 2019] [core:notice] [pid 484] AH00052: child pid 24525 exit signal Bus error (7)
[Thu Aug 08 09:09:51.940770 2019] [core:notice] [pid 484] AH00052: child pid 12161 exit signal Bus error (7)
[Thu Aug 08 09:09:51.941123 2019] [core:notice] [pid 484] AH00052: child pid 27649 exit signal Bus error (7)
[Thu Aug 08 09:09:51.942143 2019] [core:notice] [pid 484] AH00052: child pid 27726 exit signal Bus error (7)
[Thu Aug 08 09:09:52.943167 2019] [mpm_prefork:notice] [pid 484] AH00169: caught SIGTERM, shutting down
[Thu Aug 08 09:09:58.802358 2019] [mpm_prefork:notice] [pid 510] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Thu Aug 08 09:09:58.806721 2019] [core:notice] [pid 510] AH00094: Command line: '/usr/sbin/apache2'
[Sat Aug 10 11:17:07.257539 2019] [mpm_prefork:notice] [pid 598] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Aug 10 11:17:07.275987 2019] [core:notice] [pid 598] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 19 at Sun Sep  8 18:24:00 2019
[Mon Sep 09 18:17:06.756608 2019] [mpm_prefork:notice] [pid 504] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Sep 09 18:17:06.758517 2019] [core:notice] [pid 504] AH00094: Command line: '/usr/sbin/apache2'
[Tue Sep 10 06:17:05.657032 2019] [mpm_prefork:notice] [pid 494] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Tue Sep 10 06:17:05.658149 2019] [core:notice] [pid 494] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 20 at Tue Sep 10 21:20:00 2019
warning: commands will be executed using /bin/sh
job 21 at Tue Sep 10 21:31:00 2019
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.

Suite:

DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying
[Wed Sep 11 17:52:54.753452 2019] [core:notice] [pid 494] AH00052: child pid 1093 exit signal Bus error (7)
[Wed Sep 11 17:52:55.049954 2019] [core:notice] [pid 494] AH00052: child pid 22446 exit signal Bus error (7)
[Wed Sep 11 17:52:56.051584 2019] [core:notice] [pid 494] AH00052: child pid 14524 exit signal Bus error (7)
[Wed Sep 11 17:52:56.052378 2019] [mpm_prefork:notice] [pid 494] AH00169: caught SIGTERM, shutting down
[Wed Sep 11 17:53:04.489028 2019] [mpm_prefork:notice] [pid 493] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Sep 11 17:53:04.498596 2019] [core:notice] [pid 493] AH00094: Command line: '/usr/sbin/apache2'
[Wed Sep 11 18:44:38.542369 2019] [mpm_prefork:notice] [pid 493] AH00169: caught SIGTERM, shutting down
[Wed Sep 11 18:49:11.390939 2019] [mpm_prefork:notice] [pid 11875] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Sep 11 18:49:11.396852 2019] [core:notice] [pid 11875] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 23 at Wed Sep 11 19:01:00 2019
[Thu Sep 12 20:42:40.569133 2019] [core:notice] [pid 11875] AH00052: child pid 11900 exit signal Bus error (7)
[Thu Sep 12 20:42:40.575599 2019] [core:notice] [pid 11875] AH00052: child pid 11901 exit signal Bus error (7)
[Thu Sep 12 20:42:41.578723 2019] [mpm_prefork:notice] [pid 11875] AH00169: caught SIGTERM, shutting down
[Thu Sep 12 20:42:49.754957 2019] [mpm_prefork:notice] [pid 511] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Thu Sep 12 20:42:49.758331 2019] [core:notice] [pid 511] AH00094: Command line: '/usr/sbin/apache2'
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
warning: commands will be executed using /bin/sh
job 24 at Thu Sep 12 21:07:00 2019
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
[Thu Sep 19 05:52:41.025419 2019] [:error] [pid 27244] [client 192.168.1.46:49413] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:52:41.113368 2019] [:error] [pid 18352] [client 192.168.1.46:49415] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:52:52.160996 2019] [:error] [pid 4271] [client 192.168.1.46:49419] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:52:52.261316 2019] [:error] [pid 4270] [client 192.168.1.46:49422] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:55:05.098546 2019] [:error] [pid 18352] [client 192.168.1.46:49436] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:55:05.184499 2019] [:error] [pid 6994] [client 192.168.1.46:49438] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:55:52.649380 2019] [:error] [pid 10858] [client 192.168.1.46:49450] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 05:55:52.753810 2019] [:error] [pid 8043] [client 192.168.1.46:49452] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:11:49.291256 2019] [:error] [pid 10857] [client 192.168.1.46:49506] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:11:49.436233 2019] [:error] [pid 4271] [client 192.168.1.46:49508] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:12:01.486064 2019] [:error] [pid 8043] [client 192.168.1.46:49510] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:12:01.579900 2019] [:error] [pid 18352] [client 192.168.1.46:49512] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:17:24.851610 2019] [core:notice] [pid 511] AH00052: child pid 14465 exit signal Bus error (7)
[Thu Sep 19 07:17:24.852859 2019] [core:notice] [pid 511] AH00052: child pid 4270 exit signal Bus error (7)
[Thu Sep 19 07:17:25.855317 2019] [mpm_prefork:notice] [pid 511] AH00169: caught SIGTERM, shutting down
[Thu Sep 19 07:17:33.942959 2019] [mpm_prefork:notice] [pid 503] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Thu Sep 19 07:17:33.944657 2019] [core:notice] [pid 503] AH00094: Command line: '/usr/sbin/apache2'
[Thu Sep 19 07:40:47.935663 2019] [:error] [pid 629] [client 192.168.1.46:49721] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:40:48.112866 2019] [:error] [pid 1019] [client 192.168.1.46:49723] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:41:49.194254 2019] [:error] [pid 1336] [client 192.168.1.46:49730] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:41:57.915949 2019] [:error] [pid 629] [client 192.168.1.46:49733] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:41:58.002080 2019] [:error] [pid 632] [client 192.168.1.46:49735] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:42:11.388576 2019] [:error] [pid 631] [client 192.168.1.46:49737] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
[Thu Sep 19 07:42:11.464319 2019] [:error] [pid 632] [client 192.168.1.46:49739] PHP Fatal error:  Uncaught Error: Call to a member function getName() on boolean in /var/www/html/plugins/mobile/core/class/mobile.class.php:39
Stack trace:
#0 /var/www/html/plugins/mobile/core/api/mobile.api.php(33): mobile::whoIsIq('kwVmcCL4VUqNLxG...')
#1 /var/www/html/core/php/utils.inc.php(64): require_once('/var/www/html/p...')
#2 /var/www/html/core/api/jeeApi.php(1057): include_file('plugins/mobile/...', 'mobile.api.php', 'api', 'mobile')
#3 {main}
  thrown in /var/www/html/plugins/mobile/core/class/mobile.class.php on line 39
warning: commands will be executed using /bin/sh
job 25 at Fri Sep 20 15:37:00 2019
[Sat Sep 21 15:51:17.326764 2019] [core:notice] [pid 503] AH00052: child pid 1019 exit signal Bus error (7)
[Sat Sep 21 15:51:17.328961 2019] [core:notice] [pid 503] AH00052: child pid 15849 exit signal Bus error (7)
[Sat Sep 21 15:51:17.329670 2019] [core:notice] [pid 503] AH00052: child pid 14138 exit signal Bus error (7)
[Sat Sep 21 15:51:17.330095 2019] [core:notice] [pid 503] AH00052: child pid 21008 exit signal Bus error (7)
[Sat Sep 21 15:51:18.332875 2019] [mpm_prefork:notice] [pid 503] AH00169: caught SIGTERM, shutting down
[Sat Sep 21 15:51:25.915714 2019] [mpm_prefork:notice] [pid 508] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Sep 21 15:51:25.918896 2019] [core:notice] [pid 508] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 26 at Sat Sep 21 20:03:00 2019
warning: commands will be executed using /bin/sh
job 27 at Wed Sep 25 20:45:00 2019
[Wed Sep 25 21:04:26.818954 2019] [core:notice] [pid 508] AH00052: child pid 24253 exit signal Bus error (7)
[Wed Sep 25 21:04:26.827138 2019] [core:notice] [pid 508] AH00052: child pid 23284 exit signal Bus error (7)
[Wed Sep 25 21:04:27.829132 2019] [core:notice] [pid 508] AH00052: child pid 640 exit signal Bus error (7)
[Wed Sep 25 21:04:27.830981 2019] [mpm_prefork:notice] [pid 508] AH00169: caught SIGTERM, shutting down
[Wed Sep 25 21:04:36.039453 2019] [mpm_prefork:notice] [pid 520] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Wed Sep 25 21:04:36.043149 2019] [core:notice] [pid 520] AH00094: Command line: '/usr/sbin/apache2'
[Sat Sep 28 15:15:36.190424 2019] [core:notice] [pid 520] AH00052: child pid 653 exit signal Bus error (7)
[Sat Sep 28 15:15:36.199343 2019] [core:notice] [pid 520] AH00052: child pid 1075 exit signal Bus error (7)
[Sat Sep 28 15:15:36.199968 2019] [core:notice] [pid 520] AH00052: child pid 1076 exit signal Bus error (7)
[Sat Sep 28 15:15:37.203036 2019] [mpm_prefork:notice] [pid 520] AH00169: caught SIGTERM, shutting down
[Sat Sep 28 15:15:45.539439 2019] [mpm_prefork:notice] [pid 514] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Sep 28 15:15:45.545335 2019] [core:notice] [pid 514] AH00094: Command line: '/usr/sbin/apache2'
[Sat Sep 28 15:16:26.278795 2019] [core:notice] [pid 514] AH00052: child pid 649 exit signal Bus error (7)
[Sat Sep 28 15:16:26.279180 2019] [core:notice] [pid 514] AH00052: child pid 1048 exit signal Bus error (7)
[Sat Sep 28 15:16:26.367018 2019] [core:notice] [pid 514] AH00052: child pid 646 exit signal Bus error (7)
[Sat Sep 28 15:16:26.367255 2019] [core:notice] [pid 514] AH00052: child pid 1436 exit signal Bus error (7)
[Sat Sep 28 15:16:26.630179 2019] [core:notice] [pid 514] AH00052: child pid 650 exit signal Bus error (7)
[Sat Sep 28 15:16:26.630485 2019] [mpm_prefork:notice] [pid 514] AH00169: caught SIGTERM, shutting down
[Sat Sep 28 15:16:33.538052 2019] [mpm_prefork:notice] [pid 507] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Sep 28 15:16:33.543391 2019] [core:notice] [pid 507] AH00094: Command line: '/usr/sbin/apache2'
[Sat Sep 28 16:17:06.776332 2019] [mpm_prefork:notice] [pid 522] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Sep 28 16:17:06.778825 2019] [core:notice] [pid 522] AH00094: Command line: '/usr/sbin/apache2'
[Sat Sep 28 16:54:10.779744 2019] [core:notice] [pid 522] AH00052: child pid 645 exit signal Bus error (7)
[Sat Sep 28 16:54:10.783466 2019] [core:notice] [pid 522] AH00052: child pid 5426 exit signal Bus error (7)
[Sat Sep 28 16:54:11.786562 2019] [mpm_prefork:notice] [pid 522] AH00169: caught SIGTERM, shutting down
[Sat Sep 28 16:54:18.769000 2019] [mpm_prefork:notice] [pid 522] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Sep 28 16:54:18.769895 2019] [core:notice] [pid 522] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 28 at Sat Sep 28 17:34:00 2019
warning: commands will be executed using /bin/sh
job 29 at Tue Oct  1 17:22:00 2019
[Tue Oct 01 17:31:07.384057 2019] [core:notice] [pid 522] AH00052: child pid 7915 exit signal Bus error (7)
[Tue Oct 01 17:31:07.386637 2019] [core:notice] [pid 522] AH00052: child pid 7944 exit signal Bus error (7)
[Tue Oct 01 17:31:07.719048 2019] [mpm_prefork:notice] [pid 522] AH00169: caught SIGTERM, shutting down
[Tue Oct 01 17:31:15.830046 2019] [mpm_prefork:notice] [pid 526] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Tue Oct 01 17:31:15.833335 2019] [core:notice] [pid 526] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 30 at Tue Oct  1 18:04:00 2019
[Tue Oct 01 18:11:54.920675 2019] [core:notice] [pid 526] AH00052: child pid 1053 exit signal Bus error (7)
[Tue Oct 01 18:11:55.183949 2019] [core:notice] [pid 526] AH00052: child pid 630 exit signal Bus error (7)
[Tue Oct 01 18:11:55.184302 2019] [core:notice] [pid 526] AH00052: child pid 631 exit signal Bus error (7)
[Tue Oct 01 18:11:55.184708 2019] [core:notice] [pid 526] AH00052: child pid 1038 exit signal Bus error (7)
[Tue Oct 01 18:11:55.185945 2019] [core:notice] [pid 526] AH00052: child pid 1074 exit signal Bus error (7)
[Tue Oct 01 18:11:55.186204 2019] [mpm_prefork:notice] [pid 526] AH00169: caught SIGTERM, shutting down
[Tue Oct 01 18:12:02.275065 2019] [mpm_prefork:notice] [pid 522] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Tue Oct 01 18:12:02.280315 2019] [core:notice] [pid 522] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 31 at Fri Oct 18 11:15:00 2019
warning: commands will be executed using /bin/sh
job 32 at Mon Oct 21 16:05:00 2019
warning: commands will be executed using /bin/sh
job 33 at Sun Nov 10 11:05:00 2019
[Fri Nov 15 18:17:06.778435 2019] [mpm_prefork:notice] [pid 515] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Fri Nov 15 18:17:06.781462 2019] [core:notice] [pid 515] AH00094: Command line: '/usr/sbin/apache2'
warning: commands will be executed using /bin/sh
job 34 at Sat Nov 23 19:20:00 2019
[Sat Dec 07 12:17:06.745596 2019] [mpm_prefork:notice] [pid 508] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Dec 07 12:17:06.764441 2019] [core:notice] [pid 508] AH00094: Command line: '/usr/sbin/apache2'
[Sat Dec 07 19:17:07.122643 2019] [mpm_prefork:notice] [pid 526] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Dec 07 19:17:07.124855 2019] [core:notice] [pid 526] AH00094: Command line: '/usr/sbin/apache2'
[Sat Dec 07 19:17:06.010035 2019] [mpm_prefork:notice] [pid 528] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Dec 07 19:17:06.012128 2019] [core:notice] [pid 528] AH00094: Command line: '/usr/sbin/apache2'
[Sat Dec 07 20:17:06.267397 2019] [mpm_prefork:notice] [pid 557] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Dec 07 20:17:06.269414 2019] [core:notice] [pid 557] AH00094: Command line: '/usr/sbin/apache2'
[Sun Dec 08 09:17:06.049453 2019] [mpm_prefork:notice] [pid 513] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sun Dec 08 09:17:06.050574 2019] [core:notice] [pid 513] AH00094: Command line: '/usr/sbin/apache2'

Ben je vois aucune erreur donc là je sais pas faut fouiller tous les logs

Je ne suis pas informaticien, un log ne me dit pas grand-chose…
Il n’y a pas de solutions?

Ben non faut lire tous les logs jusqu’à trouvé l’êrreur de base (sûrement un plugin tierce pas compatible)

J’ai regardé tous les logs, sans voir d’erreurs.

Bizarrement, le log « homebridge daemon » montre que Jeedom rpi3 fonctionne toujours en arrière-plan…

Vous me parlez d’un plugin tiers, mais sur mon Synology, avec Jeedom en Docker fait avec une sauvegarde du rpi, donc les mêmes plugins, il fonctionne parfaitement

Ben je sais pas du tout alors… Peut être la version de php

Il faut que je réinstalle tout?

Bonjour,

Regarde ce post, je pense que tu as le même problème

Un très grand merci @Franck
J’ai suivi la méthode de @Loic, SSH en root et envoyer la commande:
php /var/www/html/install/database.php

Loic a dû passer un dimanche difficile, ou un samedi soir difficile…

Bonne soirée

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.