Problem z update supla-docker

urbi · Post Thu Feb 23, 2023 7:01 pm

Witajcie,
mam zainstalowaną suplę w kontenerach dockera, na wirtualnej maszynie ubuntu, na hoscie z ESXi. Jako, że nie miałem potrzeby aktualizacji, to zostałem się w sumie na pierwszej wersji, która obsługiwała mqtt, lecz przyszedł moment że chciałem zrobić update i tu zaczął się problem.
Najnowszą wersję jaką mogę zainstalować, to 2.3.31. Jak zrobię update do jakiejkolwiek wyższej włącznie z najnowszą, to cloud nie działa, a logi kontenerów wyglądają następująco:

supla-db

Code: Select all

2023-02-23T18:46:42.522626Z 0 [Note] Giving 0 client threads a chance to die gracefully
2023-02-23T18:46:42.522643Z 0 [Note] Shutting down slave threads
2023-02-23T18:46:42.522646Z 0 [Note] Forcefully disconnecting 0 remaining clients
2023-02-23T18:46:42.522649Z 0 [Note] Event Scheduler: Purging the queue. 0 events
2023-02-23T18:46:42.522679Z 0 [Note] Binlog end
2023-02-23T18:46:42.524204Z 0 [Note] Shutting down plugin 'ngram'
2023-02-23T18:46:42.524211Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2023-02-23T18:46:42.524216Z 0 [Note] Shutting down plugin 'partition'
2023-02-23T18:46:42.524217Z 0 [Note] Shutting down plugin 'ARCHIVE'
2023-02-23T18:46:42.524219Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
2023-02-23T18:46:42.524220Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2023-02-23T18:46:42.524222Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2023-02-23T18:46:42.524223Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2023-02-23T18:46:42.524224Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2023-02-23T18:46:42.524226Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2023-02-23T18:46:42.524227Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2023-02-23T18:46:42.524228Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2023-02-23T18:46:42.524230Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2023-02-23T18:46:42.524231Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2023-02-23T18:46:42.524232Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2023-02-23T18:46:42.524233Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2023-02-23T18:46:42.524235Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2023-02-23T18:46:42.524236Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2023-02-23T18:46:42.524237Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2023-02-23T18:46:42.524238Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2023-02-23T18:46:42.524240Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
2023-02-23T18:46:42.524241Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2023-02-23T18:46:42.524242Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2023-02-23T18:46:42.524244Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2023-02-23T18:46:42.524245Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2023-02-23T18:46:42.524246Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2023-02-23T18:46:42.524248Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2023-02-23T18:46:42.524249Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2023-02-23T18:46:42.524250Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
2023-02-23T18:46:42.524252Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2023-02-23T18:46:42.524253Z 0 [Note] Shutting down plugin 'INNODB_CMP'
2023-02-23T18:46:42.524254Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2023-02-23T18:46:42.524256Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2023-02-23T18:46:42.524257Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2023-02-23T18:46:42.524258Z 0 [Note] Shutting down plugin 'InnoDB'
2023-02-23T18:46:42.524375Z 0 [Note] InnoDB: FTS optimize thread exiting.
2023-02-23T18:46:42.524498Z 0 [Note] InnoDB: Starting shutdown...
2023-02-23T18:46:42.624833Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2023-02-23T18:46:42.625148Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 230223 18:46:42
2023-02-23T18:46:44.136827Z 0 [Note] InnoDB: Shutdown completed; log sequence number 309055782
2023-02-23T18:46:44.138057Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-02-23T18:46:44.138133Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
2023-02-23T18:46:44.138189Z 0 [Note] Shutting down plugin 'MyISAM'
2023-02-23T18:46:44.138244Z 0 [Note] Shutting down plugin 'CSV'
2023-02-23T18:46:44.138297Z 0 [Note] Shutting down plugin 'MEMORY'
2023-02-23T18:46:44.138342Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2023-02-23T18:46:44.138407Z 0 [Note] Shutting down plugin 'sha256_password'
2023-02-23T18:46:44.138451Z 0 [Note] Shutting down plugin 'mysql_native_password'
2023-02-23T18:46:44.138577Z 0 [Note] Shutting down plugin 'binlog'
2023-02-23T18:46:44.139681Z 0 [Note] mysqld: Shutdown complete
2023-02-23T18:47:10.945537Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-02-23T18:47:10.949051Z 0 [Note] mysqld (mysqld 5.7.20) starting as process 1 ...
2023-02-23T18:47:10.952614Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-02-23T18:47:10.953741Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-02-23T18:47:10.953790Z 0 [Note] InnoDB: Uses event mutexes
2023-02-23T18:47:10.953828Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-02-23T18:47:10.953879Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2023-02-23T18:47:10.953923Z 0 [Note] InnoDB: Using Linux native AIO
2023-02-23T18:47:10.954186Z 0 [Note] InnoDB: Number of pools: 1
2023-02-23T18:47:10.954319Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-02-23T18:47:10.956734Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2023-02-23T18:47:10.975258Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-02-23T18:47:10.982183Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-02-23T18:47:10.995746Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2023-02-23T18:47:11.036347Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-02-23T18:47:11.037364Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-02-23T18:47:11.075746Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-02-23T18:47:11.076261Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-02-23T18:47:11.076265Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2023-02-23T18:47:11.076450Z 0 [Note] InnoDB: Waiting for purge to start
2023-02-23T18:47:11.126554Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 309055782
2023-02-23T18:47:11.126718Z 0 [Note] Plugin 'FEDERATED' is disabled.
2023-02-23T18:47:11.130199Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-02-23T18:47:11.136773Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2023-02-23T18:47:11.143097Z 0 [Warning] CA certificate ca.pem is self signed.
2023-02-23T18:47:11.153249Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2023-02-23T18:47:11.158198Z 0 [Note] IPv6 is available.
2023-02-23T18:47:11.158232Z 0 [Note]   - '::' resolves to '::';
2023-02-23T18:47:11.158260Z 0 [Note] Server socket created on IP: '::'.
2023-02-23T18:47:11.163663Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.163713Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.163737Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.163789Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.163814Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.163843Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.173631Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.173684Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-02-23T18:47:11.192603Z 0 [Note] Event Scheduler: Loaded 0 events
2023-02-23T18:47:11.194934Z 0 [Note] mysqld: ready for connections.
Version: '5.7.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
2023-02-23T18:47:11.194965Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check. 
2023-02-23T18:47:11.194989Z 0 [Note] Beginning of list of non-natively partitioned tables
2023-02-23T18:47:11.220395Z 0 [Note] End of list of non-natively partitioned tables
2023-02-23T18:47:12.145314Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230223 18:47:12

supla-cloud:

Code: Select all

  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In Exception.php line 18:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In PDOConnection.php line 141:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]
Database connection has been established.
                                                              
                    Application Migrations                    
                                                              
Migrating up to 20221219113615 from 20210419201821
  ++ migrating 20190815154016
     -> CREATE TABLE supla_scene (id INT AUTO_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, caption VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D218E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB
Migration 20190815154016 failed during Execution. Error An exception occurred while executing 'CREATE TABLE supla_scene (id INT AUTO_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, caption VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D218E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB':
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene' already exists
In AbstractMySQLDriver.php line 57:
                                                                               
  An exception occurred while executing 'CREATE TABLE supla_scene (id INT AUT  
  O_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, capti  
  on VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT  
   DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D2  
  18E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id  
  )) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB':      
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In Exception.php line 18:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In PDOConnection.php line 141:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]
Database connection has been established.
                                                              
                    Application Migrations                    
                                                              
Migrating up to 20221219113615 from 20210419201821
  ++ migrating 20190815154016
     -> CREATE TABLE supla_scene (id INT AUTO_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, caption VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D218E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB
Migration 20190815154016 failed during Execution. Error An exception occurred while executing 'CREATE TABLE supla_scene (id INT AUTO_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, caption VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D218E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB':
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene' already exists
In AbstractMySQLDriver.php line 57:
                                                                               
  An exception occurred while executing 'CREATE TABLE supla_scene (id INT AUT  
  O_INCREMENT NOT NULL, user_id INT NOT NULL, location_id INT NOT NULL, capti  
  on VARCHAR(255) DEFAULT NULL, enabled TINYINT(1) NOT NULL, user_icon_id INT  
   DEFAULT NULL, INDEX IDX_A4825857A76ED395 (user_id), INDEX IDX_A482585764D2  
  18E (location_id), INDEX IDX_A4825857CB4C938 (user_icon_id), PRIMARY KEY(id  
  )) DEFAULT CHARACTER SET UTF8 COLLATE UTF8_unicode_ci ENGINE = InnoDB':      
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In Exception.php line 18:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
In PDOConnection.php line 141:
                                                                               
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene  
  ' already exists                                                             
                                                                               
doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]

supla-server:

Code: Select all

2023-02-23 18:47:12,093 CRIT Supervisor running as root (no user in config file)
2023-02-23 18:47:12,099 INFO supervisord started with pid 1
2023-02-23 18:47:13,100 INFO spawned: 'supla-scheduler' with pid 22
2023-02-23 18:47:13,101 INFO spawned: 'supla-server' with pid 23
INFO[18:47:13.123657] Scheduler version 22.07.01
INFO[18:47:13.125084] Started at Thu Feb 23 18:47:13 2023
INFO[18:47:13.126814] Server version 22.12.01 [Protocol v19]
INFO[18:47:13.129724] Started at Thu Feb 23 18:47:13 2023
ERR[18:47:13.131603] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:13,132 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[18:47:13.134712] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:13,135 INFO exited: supla-server (exit status 1; not expected)
2023-02-23 18:47:14,137 INFO spawned: 'supla-scheduler' with pid 24
2023-02-23 18:47:14,139 INFO spawned: 'supla-server' with pid 25
INFO[18:47:14.151804] Server version 22.12.01 [Protocol v19]
INFO[18:47:14.155180] Scheduler version 22.07.01
INFO[18:47:14.155395] Started at Thu Feb 23 18:47:14 2023
INFO[18:47:14.158434] Started at Thu Feb 23 18:47:14 2023
ERR[18:47:14.159464] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:14,160 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[18:47:14.162632] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:14,163 INFO exited: supla-server (exit status 1; not expected)
2023-02-23 18:47:16,166 INFO spawned: 'supla-scheduler' with pid 26
2023-02-23 18:47:16,167 INFO spawned: 'supla-server' with pid 27
INFO[18:47:16.173239] Server version 22.12.01 [Protocol v19]
INFO[18:47:16.176730] Scheduler version 22.07.01
INFO[18:47:16.176920] Started at Thu Feb 23 18:47:16 2023
INFO[18:47:16.177515] Started at Thu Feb 23 18:47:16 2023
ERR[18:47:16.179369] Incorrect database version! Expected: 20221219113615
ERR[18:47:16.180397] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:16,180 INFO exited: supla-server (exit status 1; not expected)
2023-02-23 18:47:16,181 INFO exited: supla-scheduler (exit status 1; not expected)
2023-02-23 18:47:19,185 INFO spawned: 'supla-scheduler' with pid 28
2023-02-23 18:47:19,186 INFO spawned: 'supla-server' with pid 29
INFO[18:47:19.197560] Scheduler version 22.07.01
INFO[18:47:19.201097] Server version 22.12.01 [Protocol v19]
INFO[18:47:19.202175] Started at Thu Feb 23 18:47:19 2023
INFO[18:47:19.204756] Started at Thu Feb 23 18:47:19 2023
ERR[18:47:19.206981] Incorrect database version! Expected: 20221219113615
ERR[18:47:19.207171] Incorrect database version! Expected: 20221219113615
2023-02-23 18:47:19,208 INFO exited: supla-scheduler (exit status 1; not expected)
2023-02-23 18:47:19,210 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
2023-02-23 18:47:19,210 INFO exited: supla-server (exit status 1; not expected)
2023-02-23 18:47:20,211 INFO gave up: supla-server entered FATAL state, too many start retries too quickly

plik .env

Code: Select all

# Where the SUPLA Cloud will be accessible? Put domain or IP address here with port.
CLOUD_DOMAIN=192.168.0.31:9999

# Initial user account details; delete these settings after the first launch
FIRST_USER_EMAIL=xxxxxxx
FIRST_USER_PASSWORD=xxxx

# Google ReCaptcha settings
RECAPTCHA_ENABLED=false
RECAPTCHA_PUBLIC_KEY=
RECAPTCHA_PRIVATE_KEY=

# Mailer settings (SMTP)
MAILER_HOST=10.0.75.1
MAILER_PORT=465
MAILER_USER=
MAILER_PASSWORD=
MAILER_ENCRYPTION=ssl
MAILER_FROM=

# If you want to be notified about some server errors, set this
ADMIN_EMAIL=

# Where to store SUPLA Cloud's data
VOLUME_DATA=./var

# On which ports the SUPLA Cloud should listen (only if standalone mode)
PORT_HTTP=9998
PORT_HTTPS=9999

REQUIRE_REGULATIONS_ACCEPTANCE=false
REQUIRE_COOKIE_POLICY_ACCEPTANCE=false
BRUTE_FORCE_AUTH_PREVENTION_ENABLED=true
ACCOUNTS_REGISTRATION_ENABLED=true

# MQTT Broker settings (you have to run the broker yourself)
MQTT_BROKER_ENABLED=true
MQTT_BROKER_HOST=192.168.0.31
MQTT_BROKER_PORT=1883
MQTT_BROKER_TLS=false
MQTT_BROKER_USERNAME=
MQTT_BROKER_PASSWORD=
MQTT_BROKER_CLIENT_ID=supla

# These options protect your application
DB_PASSWORD=UL5xxxxxxxxxxxtqHQJS
SECRET=kKcjlKtS6MSxxxxxxxxy5xgoFxZDy8

COMPOSE_PROJECT_NAME=supla
COMPOSE_PATH_SEPARATOR=:
COMPOSE_FILE=docker-compose.yml:docker-compose.standalone.yml

Z tych logów odnoszę wrażenie, że coś nie halo jest z bazą danych (SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'supla_scene ' already exists). Próbowałem jeszcze od drugiej strony zrobić:
- wyeksportowałem bazę danych ze starej supli
- zainstalowałem czystą instancję w najnowszej wersji
- zaimportowałem bazę danych
Niestety znalazłem się dokładnie w tym samym miejscu.

Może miałby ktoś pomysł, jak można temat ogarnąć. Nie znam się zbytnio na bazach danych, a wizja stawiania wszystkiego od nowa nieco mnie przeraża, tym bardziej że po mqtt mam home assistanta i znając życie tam też się coś pokrzaczy.

lesny8 · Post Thu Feb 23, 2023 7:29 pm

Z jakiegoś powodu migracja bazy się wykrzacza.
Masz backup, więc możesz dla testu usunąć tabele 'supla_scene' i powtórzyć update.

pzygmunt · Post Thu Feb 23, 2023 7:56 pm

Wygląda tak jakbyś przerwał ręcznie update i odpalił go jeszcze raz.

lesny8 · Post Thu Feb 23, 2023 9:41 pm

Też tak obstawiam, wystarczył restart kontenerów w trakcie wykonywania migracji i pozamiatane

@urbi usuń sobie tą tabele supla_scene i wystartuj ponownie kontenery
Jak będzie dalej jakiś problem z kolejnymi tabelami albo indeksami to możesz powtarzać ich usuwanie, ale prościej i szybciej będzie przywrócić bazę z backupu, tego który robi się przed upgradem, a potem puścić ponownie skrypt supla.sh

Bazy masz spakowane gz-tem w katalogu supla-docker/var/backups/

urbi · Post Thu Feb 23, 2023 11:02 pm

Na początek poszedłem po łatwiźnie i z katalogu supla-docker\var\mysql\supla\ wykasowałem pliki supla_scene.frm i supla_scene.ibd i to w zasadzie nic nie zmieniło, po update nadal to samo.
Następnie przy pomocy internetu skonstruowałem taką komendę:

Code: Select all

docker exec supla-db mysql -u root --password="UL5VwWlUtc4JBZSjJJKqbSqO5ntqHQJS" supla -e "DROP TABLE supla_scene;"

i taki wynik dostałem:

Code: Select all

mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1217 (23000) at line 1: Cannot delete or update a parent row: a foreign key constraint fails

Pytanie czy coś nie tak robię, czy coś z tą bazą?

lesny8 · Post Thu Feb 23, 2023 11:52 pm

Tak myślałem, że ta droga nie będzie taka prosta

Z tego wynika, że są klucze w innych tabelach, trzeba by je najpierw pousuwać, kupa roboty, grzebanie bez sensu, nie ma co czasu tracić.
Przywróć bazę z backapu.
Czytałeś

FAQ?

urbi · Post Fri Feb 24, 2023 12:19 pm

Mam backupy z ostatnich 2 lat, regularnie sobie robiłem. Po testach każdy z tych backupów działa z cloudem do wersji 2.3.31, a po aktualizacji jest właśnie taka sytuacja z błędną tabelą supla_scene. Chyba jednak faktycznie trzeba postawić wszystko od nowa.

pzygmunt · Post Fri Feb 24, 2023 12:37 pm

Sprawdź w backupie czy istnieje tam tabela supla_scene

urbi · Post Mon Feb 27, 2023 1:53 pm

Właśnie istnieje i wszystkie backupy, w których ta tabela jest nie działają. Znalazłem jednak jakiś bardzo stary backup, bez tej tabeli i aktualizacja wskoczyła bez problemu. Jedyne co mnie zastanawia, to że w portainerze przy kontenerach server i cloud mam status "unhealthy" pomimo, że wszystko działa i w logach brak błędów.
Dzięki za pomoc, zawsze łatwiej do starego backupu parę urządzeń dodać, niż stawiać wszystko od nowa.

edm · Post Thu Mar 02, 2023 7:57 am

urbi wrote: Mon Feb 27, 2023 1:53 pm Jedyne co mnie zastanawia, to że w portainerze przy kontenerach server i cloud mam status "unhealthy" pomimo, że wszystko działa i w logach brak błędów.

Czytaj tutaj viewtopic.php?t=12538
Nie tylko Ty masz unhealthy. Instalowałem na mini pc x86 i raspberry pi 3B+ i na każdym jest tak samo.
Natomiast suplascripts bez problemu na zielono.