Raspberry PI - Instalacja dockerowa

Moderator: fracz

User avatar
fracz
Posts: 1598
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Thu Mar 08, 2018 11:07 am

Code: Select all

docker logs --tail=50 supla-cloud
docker logs --tail=50 supla-server
dar3cz3k_
Posts: 37
Joined: Wed Mar 07, 2018 10:20 pm
Location: Brudzowice

Thu Mar 08, 2018 11:16 am

Code: Select all

pi@raspberrypi:~/supla-docker $ docker logs --tail=50 supla-cloud
  [Doctrine\DBAL\Driver\PDOException]
  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_de
  fault' (using password: YES)

  [PDOException]
  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_de
  fault' (using password: YES)

doctrine:database:create [--shard SHARD] [--connection [CONNECTION]] [--if-not-exists] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command>

  [RuntimeException]
  Could not connect to to the database.

doctrine:database:create [--shard SHARD] [--connection [CONNECTION]] [--if-not-exists] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command>


                    Application Migrations


10:34:42 ERROR     [console] Error thrown while running command "doctrine:migrations:migrate --no-interaction --allow-no-migration". Message: "An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_default' (using password: YES)" ["error" => Doctrine\DBAL\Exception\ConnectionException { …},"command" => "doctrine:migrations:migrate --no-interaction --allow-no-migration","message" => "An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_default' (using password: YES)"] []
10:34:42 ERROR     [console] Command "doctrine:migrations:migrate --no-interaction --allow-no-migration" exited with code "1" ["command" => "doctrine:migrations:migrate --no-interaction --allow-no-migration","code" => 1] []


  [Doctrine\DBAL\Exception\ConnectionException]
  An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for us
  er 'supla'@'supla-cloud.supla_default' (using password: YES)



  [Doctrine\DBAL\Driver\PDOException]
  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_de
  fault' (using password: YES)



  [PDOException]
  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'supla-cloud.supla_de
  fault' (using password: YES)


doctrine:migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--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>]


pi@raspberrypi:~/supla-docker $ docker logs --tail=50 supla-server
INFO[1520507417.428180] Started at Thu Mar  8 11:10:17 2018
INFO[1520507417.442449] Server version 1.8.5 [Protocol v8]
INFO[1520507417.486697] Started at Thu Mar  8 11:10:17 2018
ERR[1520507417.794402] MySQL - Failed to connect to database.
2018-03-08 11:10:17,798 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-03-08 11:10:17,802 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ERR[1520507418.10121] MySQL - Failed to connect to database.
ERR[1520507418.846690] MySQL - Failed to connect to database.
ERR[1520507419.894381] MySQL - Failed to connect to database.

Pytanie, czy problem z zainstalowaniem jest tylko na RPi b i starszych modelach?
Jeśli tak to zainwestuje w RPi 2 jeśli instalacja przechodzi prawidłowo.
Last edited by dar3cz3k_ on Thu Mar 08, 2018 11:46 am, edited 1 time in total.
User avatar
fracz
Posts: 1598
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Thu Mar 08, 2018 11:38 am

To jeszcze do kompletu

Code: Select all

docker logs --tail=50 supla-db
dar3cz3k_
Posts: 37
Joined: Wed Mar 07, 2018 10:20 pm
Location: Brudzowice

Thu Mar 08, 2018 11:41 am

Proszę:

Code: Select all

[code]pi@raspberrypi:~/supla-docker $ docker logs --tail=50 supla-db
180308 10:16:08 [Note] Event Scheduler: Purging the queue. 0 events
180308 10:16:08  InnoDB: Starting shutdown...
180308 10:16:09  InnoDB: Shutdown completed; log sequence number 2658393
180308 10:16:09 [Note] mysqld: Shutdown complete

180308 10:17:36 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
180308 10:17:36 [Note] mysqld (mysqld 5.5.58-0+deb7u1) starting as process 1 ...
180308 10:17:36 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
180308 10:17:36 [Note] Plugin 'FEDERATED' is disabled.
180308 10:17:36 InnoDB: The InnoDB memory heap is disabled
180308 10:17:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180308 10:17:36 InnoDB: Compressed tables use zlib 1.2.7
180308 10:17:36 InnoDB: Using Linux native AIO
180308 10:17:37 InnoDB: Initializing buffer pool, size = 128.0M
180308 10:17:37 InnoDB: Completed initialization of buffer pool
180308 10:17:37 InnoDB: highest supported file format is Barracuda.
180308 10:17:38  InnoDB: Waiting for the background threads to start
180308 10:17:39 InnoDB: 5.5.58 started; log sequence number 2658393
180308 10:17:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180308 10:17:39 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180308 10:17:39 [Note] Server socket created on IP: '0.0.0.0'.
180308 10:17:39 [Note] Event Scheduler: Loaded 0 events
180308 10:17:39 [Note] mysqld: ready for connections.
Version: '5.5.58-0+deb7u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
180308 10:35:35 [Note] mysqld: Normal shutdown

180308 10:35:35 [Note] Event Scheduler: Purging the queue. 0 events
180308 10:35:35  InnoDB: Starting shutdown...
180308 10:35:36  InnoDB: Shutdown completed; log sequence number 2658393
180308 10:35:36 [Note] mysqld: Shutdown complete

180308 11:09:49 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
180308 11:09:49 [Note] mysqld (mysqld 5.5.58-0+deb7u1) starting as process 1 ...
180308 11:09:50 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
180308 11:09:50 [Note] Plugin 'FEDERATED' is disabled.
180308 11:09:50 InnoDB: The InnoDB memory heap is disabled
180308 11:09:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180308 11:09:50 InnoDB: Compressed tables use zlib 1.2.7
180308 11:09:50 InnoDB: Using Linux native AIO
180308 11:09:50 InnoDB: Initializing buffer pool, size = 128.0M
180308 11:09:50 InnoDB: Completed initialization of buffer pool
180308 11:09:50 InnoDB: highest supported file format is Barracuda.
180308 11:09:51  InnoDB: Waiting for the background threads to start
180308 11:09:52 InnoDB: 5.5.58 started; log sequence number 2658393
180308 11:09:52 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180308 11:09:52 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180308 11:09:52 [Note] Server socket created on IP: '0.0.0.0'.
180308 11:09:52 [Note] Event Scheduler: Loaded 0 events
180308 11:09:52 [Note] mysqld: ready for connections.
Version: '5.5.58-0+deb7u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
[/code]


Pytanie, czy problemy z instalacją nie występują na nowszych modelach RPi?
Może czas zakupić nowszy model :D
dawkor
Posts: 125
Joined: Sun Jan 07, 2018 1:20 pm

Fri Mar 09, 2018 7:32 am

Ja mam na 3 postawione 2 dockery i nie ma problemu. Jeden server cloud a drugi scripts. wiec nie jest to problem rpi3. poza tym 2 od 3 niczym za bardzo się nie rożni.
User avatar
Lector
Posts: 468
Joined: Fri Nov 17, 2017 2:26 pm
Location: Poznań
Contact:

Fri Mar 09, 2018 7:41 am

U mnie stoi to na Pi Zero W.

Może zakupię drugą sztukę i opiszę gdzieś w osobny wątku jak postawić i jak zrobić aby wstawała bo braku zasilania.
dar3cz3k_
Posts: 37
Joined: Wed Mar 07, 2018 10:20 pm
Location: Brudzowice

Fri Mar 09, 2018 8:08 am

dawkor wrote:
Fri Mar 09, 2018 7:32 am
Ja mam na 3 postawione 2 dockery i nie ma problemu. Jeden server cloud a drugi scripts. wiec nie jest to problem rpi3. poza tym 2 od 3 niczym za bardzo się nie rożni.
Ja mam RPi b - a one dość znacząco się różnią od siebie.
dar3cz3k_
Posts: 37
Joined: Wed Mar 07, 2018 10:20 pm
Location: Brudzowice

Fri Mar 09, 2018 8:11 am

Lector wrote:
Fri Mar 09, 2018 7:41 am
U mnie stoi to na Pi Zero W.

Może zakupię drugą sztukę i opiszę gdzieś w osobny wątku jak postawić i jak zrobić aby wstawała bo braku zasilania.
Było by super.
Pamiętasz może z jakiego poradnika instalowałeś to poprzednim razem, jak zadziałało?
User avatar
fracz
Posts: 1598
Joined: Fri Oct 28, 2016 10:56 pm
Location: Rybna

Fri Mar 09, 2018 8:35 am

Z logów wynika że wszystko działa. Proponuję spróbować raz jeszcze, bo być może pierwsza instalacja z nie tego brancha cos popsuła.

Code: Select all

docker stop $(docker ps -a -q)
docker system prune -fa
cd supla-docker
rm -fr var/*
git checkout .
git checkout src
./supla.sh start
dar3cz3k_
Posts: 37
Joined: Wed Mar 07, 2018 10:20 pm
Location: Brudzowice

Fri Mar 09, 2018 8:44 am

Dzięki zaraz spróbuje jeszcze raz to zainstalować.
Jak się nie uda to postawie system od nowa i spróbuje na czystym systemie.

Zapomniałeś na końcu dodać, że można to puścić i iść na "dużą kawę" :D
Post Reply