Re: [Tuto] Installation de Jeedom sur Synology avec docker en mode Host
Publié : 09 juil. 2019, 18:57
Génial merci!
Forum sur Jeedom
https://www.jeedom.com/forum/
Il me semblait l'avoir fait correctement ...Didier3L a écrit : ↑09 juil. 2019, 18:39Seul Mémoire disponible 0 % est normal
tout le reste doit etre au vert
As tu bien modifié le fichier /root/init.sh et ensuite redémarré le conteneur
Peux tu mettre une capture écran des Paramètres réseaux de Jeedom. Dans Configuration / réseaux / Accés interne
Code : Tout sélectionner
[MySQL] Error code : 42S02 (1146). Table 'jeedom.config' doesn't exist : SELECT `key`,`value` FROM config WHERE `key` IN ('session_lifetime','sso:allowRemoteUser') AND plugin=:plugin
Tu as été trop vite et tu as tout cassémitch55 a écrit : ↑09 juil. 2019, 19:20Il me semblait l'avoir fait correctement ...Didier3L a écrit : ↑09 juil. 2019, 18:39Seul Mémoire disponible 0 % est normal
tout le reste doit etre au vert
As tu bien modifié le fichier /root/init.sh et ensuite redémarré le conteneur
Peux tu mettre une capture écran des Paramètres réseaux de Jeedom. Dans Configuration / réseaux / Accés interne
J'ai tout supprimé pour recommencer l'installation.
Maintenant, avant le lancement de jeedom, j'ai ce message :
Code : Tout sélectionner
[MySQL] Error code : 42S02 (1146). Table 'jeedom.config' doesn't exist : SELECT `key`,`value` FROM config WHERE `key` IN ('session_lifetime','sso:allowRemoteUser') AND plugin=:plugin
Code : Tout sélectionner
root@jeedom:/# sudo php /var/www/html/install/restore.php
sudo: unable to send audit message: Unknown error -1
[START RESTORE]
***************Début de la restauration de Jeedom 2019-07-09 20:00:57***********
****
Envoie l'événement de début de restauration...***ERREUR*** [MySQL] Error code :
42S02 (1146). Table 'jeedom.scenario' doesn't exist : SELECT `id`, `name`, `isA
ctive`, `group`, `mode`, `schedule`, `scenarioElement`, `trigger`, `timeout`, `o
bject_id`, `isVisible`, `display`, `order`, `description`, `configuration`, `typ
e`
FROM scenario
WHERE mode != "schedule" AND isActive=1 AND `trigger` LIKE :cmd_
idErreur durant la restauration : [MySQL] Error code : 42S02 (1146). Table 'jeed
om.config' doesn't exist : SELECT `value`
FROM config
WHERE `key`=:key
AND plugin=:pluginDétails : Array
(
[0] => Array
(
[file] => /var/www/html/core/class/config.class.php
[line] => 145
[function] => Prepare
[class] => DB
[type] => ::
[args] => Array
(
[0] => SELECT `value`
FROM config
WHERE `key`=:key
AND plugin=:plugin
[1] => Array
(
[plugin] => core
[key] => backup::path
)
[2] => 0
)
)
[1] => Array
(
[file] => /var/www/html/install/restore.php
[line] => 56
[function] => byKey
[class] => config
[type] => ::
[args] => Array
(
[0] => backup::path
)
)
)
[END RESTORE ERROR]
Enable scenario : PHP Fatal error: Uncaught Exception: [MySQL] Error code : 42S
02 (1146). Table 'jeedom.config' doesn't exist : DELETE FROM config
WHERE `key`=:key
AND plugin=:plugin in /var/www/html/core/class/DB.class.
php:105
Stack trace:
#0 /var/www/html/core/class/config.class.php(121): DB::Prepare('DELETE FROM con.
..', Array, 0)
#1 /var/www/html/core/class/config.class.php(66): config::remove('enableScenario
', 'core')
#2 /var/www/html/core/class/jeedom.class.php(719): config::save('enableScenario'
, 1)
#3 /var/www/html/install/restore.php(220): jeedom::start()
#4 {main}
[2] => 0
)
)
[1] => Array
(
[file] => /var/www/html/install/restore.php
[line] => 56
[function] => byKey
[class] => config
[type] => ::
[args] => Array
(
[0] => backup::path
)
)
)
[END RESTORE ERROR]
Enable scenario : PHP Fatal error: Uncaught Exception: [MySQL] Error code : 42S
02 (1146). Table 'jeedom.config' doesn't exist : DELETE FROM config
WHERE `key`=:key
AND plugin=:plugin in /var/www/html/core/class/DB.class.
php:105
Stack trace:
#0 /var/www/html/core/class/config.class.php(121): DB::Prepare('DELETE FROM con.
..', Array, 0)
#1 /var/www/html/core/class/config.class.php(66): config::remove('enableScenario
', 'core')
#2 /var/www/html/core/class/jeedom.class.php(719): config::save('enableScenario'
, 1)
#3 /var/www/html/install/restore.php(220): jeedom::start()
#4 {main}
Par contre je constate que tourne sur Xpenology
Bonjour GlloQ ,
Code : Tout sélectionner
All init complete
Start apache2
Failed to connect to bus: No such file or directory
[....] Restarting Apache httpd web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
[ ok .
Start sshd
Failed to connect to bus: No such file or directory
[....] Restarting OpenBSD Secure Shell server: sshdstart-stop-daemon: warning: failed to kill 96: No such process
[ ok .
[....] Starting OpenBSD Secure Shell server: sshd[ ok .
Start atd
Failed to connect to bus: No such file or directory
etc...
Code : Tout sélectionner
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2019-07-11 14:05:17,096 CRIT Supervisor running as root (no user in config file)
2019-07-11 14:05:17,097 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
Unlinking stale socket /var/run/supervisor.sock
2019-07-11 14:05:17,953 INFO RPC interface 'supervisor' initialized
2019-07-11 14:05:17,954 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-07-11 14:05:17,955 INFO supervisord started with pid 296
2019-07-11 14:05:18,957 INFO spawned: 'cron' with pid 299
2019-07-11 14:05:18,966 INFO exited: cron (exit status 1; not expected)
2019-07-11 14:05:19,969 INFO spawned: 'cron' with pid 300
2019-07-11 14:05:19,978 INFO exited: cron (exit status 1; not expected)
2019-07-11 14:05:21,983 INFO spawned: 'cron' with pid 301
2019-07-11 14:05:21,992 INFO exited: cron (exit status 1; not expected)
2019-07-11 14:05:24,997 INFO spawned: 'cron' with pid 302
2019-07-11 14:05:25,008 INFO exited: cron (exit status 1; not expected)
2019-07-11 14:05:25,009 INFO gave up: cron entered FATAL state, too many start retries too quickly
Code : Tout sélectionner
/tmp/jeedom.zip 100%[==============================>] 29.50M 953KB/s in 45s
2019-07-12 12:30:12 (677 KB/s) - '/tmp/jeedom.zip' saved [30930496/30930496]
étape 6 téléchargement de jeedom réussie
All init complete
Start apache2
Failed to connect to bus: No such file or directory
[....] Restarting Apache httpd web server: apache2AH00557: apache2: apr_sockaddr_info_get() fai
led for Jeenology
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using
127.0.0.1. Set the 'ServerName' directive globally to suppress this message
. ok
Start sshd
Failed to connect to bus: No such file or directory
[ ok ] Restarting OpenBSD Secure Shell server: sshd.
/etc/init.d/cron restart
/etc/init.d/cron start