Plantage installation avec docker synology

Bonjour,

J’ai souhaité installer une nouvelle instance de jeedom sur mon synology sous docker (ma prod est sur rapsberry pi).
J’ai suivi le tuto officiel ici : https://doc.jeedom.com/fr_FR/installation/synology
Mon installation plante à l’étape 10, Je vous joins les logs ci-dessous… Merci pour toute l’aide que vous pourrez m’apporter.

Start init
Start jeedom installation
--2024-02-02 21:05:21--  https://raw.githubusercontent.com/jeedom/core/beta/install/install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133, 185.199.110.133, 185.199.108.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17382 (17K) [text/plain]
Saving to: '/root/install.sh'
     0K .......... ......                                     100% 10.6M=0.002s
2024-02-02 21:05:21 (10.6 MB/s) - '/root/install.sh' saved [17382/17382]
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 6 - download Jeedom
--2024-02-02 21:05:21--  https://codeload.github.com/jeedom/core/zip/refs/heads/beta
Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/zip]
Saving to: '/tmp/jeedom.zip'
     0K .......... .......... .......... .......... ..........  945K
    50K .......... .......... .......... .......... .......... 1.79M
   100K .......... .......... .......... .......... .......... 2.09M
   150K .......... .......... .......... .......... .......... 11.9M
 [...]
 84550K .......... .......... .......... .......... ...        55.9M=5.2s
2024-02-02 21:05:27 (15.9 MB/s) - '/tmp/jeedom.zip' saved [86623781]
Step 6 - download Jeedom done
WARNING: The host 'dom2' could not be looked up with /usr//bin/resolveip.
This probably means that your libc libraries are not 100 % compatible
with this binary MariaDB version. The MariaDB daemon, mysqld, should work
normally with the exception that host name resolving will not work.
This means that you should use IP addresses instead of hostnames
when specifying MariaDB privileges !
Installing MariaDB/MySQL system tables in '/var/lib/mysql/' ...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following command:
'/usr//bin/mysql_secure_installation'
which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.
See the MariaDB Knowledgebase at http://mariadb.com/kb
You can start the MariaDB daemon with:
cd '/usr/' ; /usr//bin/mysqld_safe --datadir='/var/lib/mysql/'
You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr//mysql-test' ; perl mysql-test-run.pl
Please report any problems at http://mariadb.org/jira
The latest information about MariaDB is available at http://mariadb.org/.
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/
Stopping MariaDB database server: mysqld.
Starting MariaDB database server: mysqld.
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 10 - Jeedom install
Begin installation of composer
--2024-02-02 21:05:39--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58167 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
     0K .......... .......... .......... .......... .......... 88% 2.45M 0s
    50K ......                                                100% 82.5M=0.02s
2024-02-02 21:05:39 (2.78 MB/s) - 'composer-setup.php' saved [58167/58167]
All settings correct for using Composer
Downloading...
Composer (version 2.6.6) successfully installed to: /var/www/html/composer.phar
Use it: php composer.phar
sudo: unable to resolve host dom2: Name or service not known
sudo: unable to resolve host dom2: Name or service not known
End installation of composer
[START INSTALL]
****Install jeedom at (2024-02-02 22:05:40)****
Installation of Jeedom
Installating database...***ERROR*** SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)
OK
Error during install : SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES)Details : Array
(
    [0] => Array

(
            [file] => /var/www/html/core/class/DB.class.php
            [line] => 40
            [function] => __construct
PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000] [1045] Access denied for user 'jeedom'@'localhost' (using password: YES) in /var/www/html/core/class/DB.class.php:40

Stack trace:
#0 /var/www/html/core/class/DB.class.php(40): PDO->__construct('mysql:host=loca...', 'jeedom', 'c3eeb9566996da5', Array)
#1 /var/www/html/core/class/DB.class.php(50): DB::initConnection()
#2 /var/www/html/core/class/DB.class.php(82): DB::getConnection()
#3 /var/www/html/core/class/config.class.php(192): DB::Prepare('SELECT `key`,`v...', Array, 1)
#4 /var/www/html/core/class/translate.class.php(51): config::byKeys(Array)
            [class] => PDO
            [type] => ->
            [args] => Array
                (
                    [0] => mysql:host=localhost;port=3306;dbname=jeedom
                    [1] => jeedom
                    [2] => c3eeb9566996da5
                    [3] => Array
                        (
                            [1002] => SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci
                            [12] => 1
                        )
                )

)
    [1] => Array

(
            [file] => /var/www/html/core/class/DB.class.php
            [line] => 50
            [function] => initConnection
            [class] => DB
            [type] => ::
            [args] => Array
                (
                )

)
    [2] => Array

(
            [file] => /var/www/html/core/class/DB.class.php
            [line] => 82
            [function] => getConnection
            [class] => DB
            [type] => ::
            [args] => Array
                (
                )

)
    [3] => Array

(
#5 /var/www/html/core/class/translate.class.php(207): translate::getConfig('language', 'fr_FR')
#6 /var/www/html/core/class/translate.class.php(102): translate::getLanguage()
#7 /var/www/html/core/class/translate.class.php(81): translate::exec('{{Chauffage}}', '/var/www/html/c...', false)
#8 /var/www/html/core/class/translate.class.php(220): translate::sentence('Chauffage', '/var/www/html/c...', false)
#9 /var/www/html/core/con in /var/www/html/core/class/DB.class.php on line 40
            [file] => /var/www/html/core/class/config.class.php
            [line] => 192
            [function] => Prepare
            [class] => DB
            [type] => ::
            [args] => Array
                (
                    [0] => SELECT `key`,`value`
		FROM config
		WHERE `key` IN ('language')
		AND plugin=:plugin
                    [1] => Array
                        (
                            [plugin] => core
                        )
                    [2] => 1
                )

)
    [4] => Array

(
            [file] => /var/www/html/core/class/translate.class.php
            [line] => 51
            [function] => byKeys
            [class] => config
            [type] => ::
            [args] => Array
                (
                    [0] => Array
                        (
                            [0] => language
                        )
                )

)
    [5] => Array

(
            [file] => /var/www/html/core/class/translate.class.php
            [line] => 207
            [function] => getConfig
            [class] => translate
            [type] => ::
            [args] => Array
                (
                    [0] => language
                    [1] => fr_FR
                )

)
    [6] => Array

(
            [file] => /var/www/html/core/class/translate.class.php
            [line] => 102
            [function] => getLanguage
            [class] => translate
            [type] => ::
            [args] => Array
                (
                )

)
    [7] => Array

(
            [file] => /var/www/html/core/class/translate.class.php
            [line] => 81
            [function] => exec
            [class] => translate
            [type] => ::
            [args] => Array
                (
                    [0] => {{Chauffage}}
                    [1] => /var/www/html/core/config/jeedom.config.php
                    [2] => 
                )

)
    [8] => Array

(
            [file] => /var/www/html/core/class/translate.class.php
            [line] => 220
            [function] => sentence
            [class] => translate
            [type] => ::
            [args] => Array
                (
                    [0] => Chauffage
                    [1] => /var/www/html/core/config/jeedom.config.php
                    [2] => 
                )

)
    [9] => Array

(
            [file] => /var/www/html/core/config/jeedom.config.php
            [line] => 23
            [function] => __
            [args] => Array
                (
                    [0] => Chauffage
                    [1] => /var/www/html/core/config/jeedom.config.php
                )

)
    [10] => Array

(
            [file] => /var/www/html/core/php/utils.inc.php
            [line] => 84
            [args] => Array
                (
                    [0] => /var/www/html/core/config/jeedom.config.php
                )
            [function] => require_once

)
    [11] => Array

(
            [file] => /var/www/html/core/php/core.inc.php
            [line] => 27
            [function] => include_file
            [args] => Array
                (
                    [0] => core/config
                    [1] => jeedom.config.php
                    [2] => config
                )

)
    [12] => Array

(
            [file] => /var/www/html/install/install.php
            [line] => 53
            [args] => Array
                (
                    [0] => /var/www/html/core/php/core.inc.php
                )
            [function] => require_once

)
)
[END INSTALL ERROR]
Cannot install Jeedom - Cancelling
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 11 - Jeedom post-install
no crontab for root
sudo: unable to resolve host dom2: Name or service not known
sudo: unable to resolve host dom2: Name or service not known
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Get:5 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [7051 B]
Get:6 http://deb.debian.org/debian-security buster/updates/main amd64 Packages [584 kB]
Fetched 638 kB in 1s (464 kB/s)
Reading package lists...
sudo: unable to resolve host dom2: Name or service not known
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
sudo: unable to resolve host dom2: Name or service not known
sudo: unable to resolve host dom2: Name or service not known
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Step 11 - Jeedom post-install done

d
Stopping deferred execution scheduler: atd.
Starting deferred execution scheduler: atd.
Starting mariadb
Stopping MariaDB database server: mysqld.
Starting MariaDB database server: mysqld.
All init complete
Start apache2
AH00557: apache2: apr_sockaddr_info_get() failed for dom2
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
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Starting Apache httpd web server: apache2Action 'start' failed.
The Apache error log may have more information.
.

Bonjour.

Vous n’avez pas utilisé une édition de Debian 12 par hasard ?
Pour Jeedom stable, il faut une édition de Debian 11.

Edit : j’ai rien dis, vous installez bien une version bêta, mais une Debian 10, pourquoi ne pas passer sur la version 11

Heuuuu en toute franchise j’ai pris l’image officielle 4.4, je n’ai pas spécifiquement cherché une bêta ou du Debian 10… Quelle image me recommanderiez vous ?

Validez ensuite la demande de version, le mieux étant de prendre la dernière (prendre la version latest). Mais pour certains modèles Sybology il peut être nécessaire de choisir la version *-buster

Ne pas oublier d’effacer les fichiers dans les répertoires sur le Synology
Docker/jeedom
A chaque nouvelle installation

Yes, j’ai tout nettoyé et recréé un conteneur tout propre en pointant sur la 4.3-buster car mon modele de syno requiert cette image (j’avais l’erreur indiquée dans le tuto officiel).
Malheureusement ça ne fonctionne toujours pas :

Start init
Start jeedom installation
--2024-02-04 17:27:21--  https://raw.githubusercontent.com/jeedom/core/beta/install/install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.108.133, 185.199.109.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17382 (17K) [text/plain]
Saving to: '/root/install.sh'
     0K .......... ......                                     100% 9.86M=0.002s
2024-02-04 17:27:21 (9.86 MB/s) - '/root/install.sh' saved [17382/17382]
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 6 - download Jeedom
--2024-02-04 17:27:21--  https://codeload.github.com/jeedom/core/zip/refs/heads/beta
Resolving codeload.github.com (codeload.github.com)... 140.82.121.9
Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/zip]
Saving to: '/tmp/jeedom.zip'
     0K .......... .......... .......... .......... ..........  981K
    50K .......... .......... .......... .......... .......... 1.81M
   100K .......... .......... .......... .......... .......... 1.87M
[...]
 84550K .......... .......... .......... .......... ...        73.2M=5.7s
2024-02-04 17:27:27 (14.5 MB/s) - '/tmp/jeedom.zip' saved [86623781]
Step 6 - download Jeedom done
Installing MariaDB/MySQL system tables in '/var/lib/mysql/' ...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following command:
'/usr//bin/mysql_secure_installation'
which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.
See the MariaDB Knowledgebase at http://mariadb.com/kb
You can start the MariaDB daemon with:
cd '/usr/' ; /usr//bin/mysqld_safe --datadir='/var/lib/mysql/'
You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr//mysql-test' ; perl mysql-test-run.pl
Please report any problems at http://mariadb.org/jira
The latest information about MariaDB is available at http://mariadb.org/.
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/
Stopping MariaDB database server: mysqld.
Starting MariaDB database server: mysqld.
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 10 - Jeedom install
Begin installation of composer
--2024-02-04 17:27:40--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58167 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
     0K .......... .......... .......... .......... .......... 88% 2.47M 0s
    50K ......                                                100% 5.20M=0.02s
2024-02-04 17:27:40 (2.64 MB/s) - 'composer-setup.php' saved [58167/58167]
All settings correct for using Composer
Downloading...
Composer (version 2.6.6) successfully installed to: /var/www/html/composer.phar
Use it: php composer.phar
rm: cannot remove '/usr/local/bin/composer': No such file or directory
End installation of composer
[START INSTALL]
****Install jeedom at (2024-02-04 18:27:42)****
Installation of Jeedom
Installating database...OK
Post install...
[START CONSISTENCY]
[START CHECK AND FIX DB]
Fix : ALTER TABLE `cmd` DROP INDEX `logicalID`;
Fix : 
CREATE INDEX `logicalID` ON `cmd` (`logicalId` ASC)[END CHECK AND FIX DB]
warning: commands will be executed using /bin/sh
job 2 at Sun Feb  4 17:27:00 2024
Can't open /var/run/atd.pid to signal atd. No atd running?
Check jeedom package...OK
Check jeedom database...
Fix : ALTER TABLE `cmd` DROP INDEX `logicalID`;
Fix : 
CREATE INDEX `logicalID` ON `cmd` (`logicalId` ASC)OK
Fix default summary...OK
Check crons...
Create plugin::cronDaily
Create jeedom::backup
Create plugin::cronHourly
Create scenario::check
Create scenario::control
Create jeedom::cronDaily
Create jeedom::cronHourly
Create jeedom::cron5
Create jeedom::cron10
Create jeedom::cron
Create plugin::cron
Create plugin::cron5
Create plugin::cron10
Create plugin::cron15
Create plugin::cron30
Create plugin::checkDeamon
Create cache::persist
Create history::archive
Create plugin::heartbeat
Check filesystem right...OK
Flush cache widget...
Check jeedom object...OK
Check jeedom cmd...OK
Create default user function...OK
Set cache hour...OK
Check composer...OK
Check nodejs...Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]
Hit:4 http://deb.debian.org/debian buster-updates InRelease
Get:5 http://deb.debian.org/debian-security buster/updates/main amd64 Packages [584 kB]
Get:6 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [7051 B]
Fetched 638 kB in 1s (524 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
OK
[END CONSISTENCY]
Creating user (admin,admin)
OK
Install duration : 20s
[END INSTALL SUCCESS]
Step 10 - Jeedom install done
Welcome to Jeedom installer
Jeedom version : beta
Web folder : /var/www/html
Installation type : standard
---------------------------------------------------------------------
Starting step 11 - Jeedom post-install
no crontab for root
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Step 11 - Jeedom post-install done

d
Stopping deferred execution scheduler: atd.
Starting deferred execution scheduler: atd.
Starting mariadb
Stopping MariaDB database server: mysqld.
Starting MariaDB database server: mysqld ..
All init complete
Start apache2
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Starting Apache httpd web server: apache2Action 'start' failed.
The Apache error log may have more information.
.

Le log apache ne donne pas d’indication très probante à mon goût :

root@localhost:/var/www/html# more /var/log/apache2/error.log 
[Thu Jan 18 17:27:31.246900 2024] [mpm_prefork:notice] [pid 46399] AH00163: Apache/2.4.38 (Debian) configured -- resuming 
normal operations
[Thu Jan 18 17:27:31.246967 2024] [core:notice] [pid 46399] AH00094: Command line: '/usr/sbin/apache2'
root@localhost:/var/www/html#

Une idée mes Obiwan kenobis ? :wink:

Dsm 6 ou 7 ?

Dsm7. Je suis bloqué en 7.1 (vieux modèle ds1815+)

Bonjour.

Je dois pas être bien réveillé, mais on dirait un log d’installation d’une version bêta en même temps qu’un log de restauration.

Si vous installez l’image de Jeedom, sans restauration, tout est ok (page santé) ?

Ensuite, votre sauvegarde, elle est sous qu’elle version de Jeedom ?

Je ne fais pas de restauration, je me contente de lancer un conteneur vierge après avoir nettoyé les volumes montés pour /html et / db.
Sur mon premier message j’étais sur la 4.4, puis je me suis cablé sur la 4.3-buster comme il m’a été recommandé de le faire.
En d’autres termes depuis le début je vous partage le log d’une première installation d’un conteneur en suivant la doc officielle de lancement d’un jeedom pour docker sous synology.

Et je précise que je ne peux ouvrir de page Web, en l’état l’installation n’est pas fonctionnelle.

Pour lancer apache

Rentrer dans le conteneur

sudo docker exec -it NONDUCONTENEUR /bin/bash

et saisir

sudo apachectl -f apache2.conf

Ps les sujets Synology c’est ici avec le bon tag
https://community.jeedom.com/tags/c/materiel-jeedom-hardware/synology-diy-faire-soit-meme/78/docker

ça me parait curieux de relancer apache alors que le lancement échoue dans le script auto d’installation de jeedom, mais par acquis de conscience j’ai tenté (d’abord ta commande puis je l’ai adapté en me disant qu’il lui manquait peut-être le chemin du script) :

sudo apachectl -f apache2.conf
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action '-f apache2.conf' failed.
The Apache error log may have more information.


root@localhost:/# sudo apachectl -f /etc/apache2/apache2.conf
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action '-f /etc/apache2/apache2.conf' failed.
The Apache error log may have more information.

J’ai tenté de recommencer de zéro en passant par l’interface de docker native à DSM au lieu de portainer, même résultat. A priori je n’ai pourtant aucun service qui tourne sur le port 9080. C’est curieux que ça bloque sur le démarrage apache tout de même. Est-ce qu’un docker adguard qui tourne sur le syno pourrait empêcher un autre apache de se lancer sur la même machine ?

J’ai tenté de bouger le port, des fois que ce soit le 9080 qui pose souci => même conclusion. Possible que l’image 4.3 soit bugguée ?