czekałem długo, wpisałem adres ip maliny.
a tak wyglądają logi, dla mnie to czarna magia i nic tam nie widzę po za słówkiem ERROR :] więc może tam jest jakiś problem.
Kod: Zaznacz cały
pi@raspberrypi:~ $ docker logs --tail=50 supla-cloud
Application Migrations
No migrations to execute.
// Warming up the cache for the prod environment with debug
// false
[OK] Cache for the "prod" environment (debug=false) was successfully warmed.
11:44:50 ERROR [console] Error thrown while running command "supla:create-co nfirmed-user 'marek.supla.org' marek --no-interaction --if-not-exists". Message: "Invalid e-mail address" ["error" => RuntimeException { …},"command" => "supla: create-confirmed-user 'marek.supla.org' marek --no-interaction --if-not-exists", "message" => "Invalid e-mail address"] []
In CreateConfirmedUserCommand.php line 69:
Invalid e-mail address
supla:create-confirmed-user [--if-not-exists] [-h|--help] [-q|--quiet] [-v|vv|vv v|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<username>] [<password>]
Database connection has been established.
Application Migrations
No migrations to execute.
// Warming up the cache for the prod environment with debug
// false
[OK] Cache for the "prod" environment (debug=false) was successfully warmed.
11:45:30 ERROR [console] Error thrown while running command "supla:create-co nfirmed-user 'marek.supla.org' marek --no-interaction --if-not-exists". Message: "Invalid e-mail address" ["error" => RuntimeException { …},"command" => "supla: create-confirmed-user 'marek.supla.org' marek --no-interaction --if-not-exists", "message" => "Invalid e-mail address"] []
In CreateConfirmedUserCommand.php line 69:
Invalid e-mail address
supla:create-confirmed-user [--if-not-exists] [-h|--help] [-q|--quiet] [-v|vv|vv v|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<username>] [<password>]
Database connection has been established.
Application Migrations
No migrations to execute.
// Warming up the cache for the prod environment with debug
// false
pi@raspberrypi:~ $ docker logs --tail=50 supla-server
INFO[1543489361.241911] Started at Thu Nov 29 11:02:41 2018
INFO[1543489361.247100] Server version 2.2.0 [Protocol v9], 32
INFO[1543489361.247385] Started at Thu Nov 29 11:02:41 2018
ERR[1543489361.250986] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489361.251199] The version of the database can not be determined!
2018-11-29 11:02:41,254 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1543489361.258479] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489361.258660] The version of the database can not be determined!
2018-11-29 11:02:41,261 INFO exited: supla-server (exit status 1; not expected)
2018-11-29 11:02:43,270 INFO spawned: 'supla-scheduler' with pid 20
2018-11-29 11:02:45,294 INFO spawned: 'supla-server' with pid 22
INFO[1543489363.318889] Scheduler version 2.2.0
INFO[1543489363.319153] Started at Thu Nov 29 11:02:43 2018
ERR[1543489363.331894] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489363.332185] The version of the database can not be determined!
2018-11-29 11:02:45,299 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[1543489365.346450] Server version 2.2.0 [Protocol v9], 32
2018-11-29 11:02:45,353 INFO spawned: 'supla-scheduler' with pid 24
INFO[1543489365.346814] Started at Thu Nov 29 11:02:45 2018
ERR[1543489365.362272] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489365.362591] The version of the database can not be determined!
2018-11-29 11:02:45,367 INFO exited: supla-server (exit status 1; not expected)
INFO[1543489365.403274] Scheduler version 2.2.0
INFO[1543489365.403463] Started at Thu Nov 29 11:02:45 2018
ERR[1543489365.410549] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489365.410726] The version of the database can not be determined!
2018-11-29 11:02:45,412 INFO exited: supla-scheduler (exit status 1; not expected)
2018-11-29 11:02:46,417 INFO spawned: 'supla-scheduler' with pid 26
INFO[1543489366.441717] Scheduler version 2.2.0
INFO[1543489366.441878] Started at Thu Nov 29 11:02:46 2018
ERR[1543489366.449289] MySQL - stmt prepare error - Table 'supla.migration_versions' doesn't exist
ERR[1543489366.449463] The version of the database can not be determined!
2018-11-29 11:02:46,451 INFO exited: supla-scheduler (exit status 1; not expected)
2018-11-29 11:02:48,460 INFO spawned: 'supla-scheduler' with pid 28
2018-11-29 11:02:48,467 INFO spawned: 'supla-server' with pid 29
INFO[1543489368.519763] Scheduler version 2.2.0
INFO[1543489368.520153] Started at Thu Nov 29 11:02:48 2018
INFO[1543489368.522434] Server version 2.2.0 [Protocol v9], 32
INFO[1543489368.522815] Started at Thu Nov 29 11:02:48 2018
ERR[1543489368.539586] Incorrect database version!
ERR[1543489368.539389] Incorrect database version!
2018-11-29 11:02:48,542 INFO exited: supla-scheduler (exit status 1; not expected)
2018-11-29 11:02:48,543 INFO exited: supla-server (exit status 1; not expected)
2018-11-29 11:02:49,545 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2018-11-29 11:02:51,553 INFO spawned: 'supla-scheduler' with pid 32
INFO[1543489371.601925] Scheduler version 2.2.0
INFO[1543489371.602240] Started at Thu Nov 29 11:02:51 2018
ERR[1543489371.618419] Incorrect database version!
2018-11-29 11:02:51,622 INFO exited: supla-scheduler (exit status 1; not expected)
2018-11-29 11:02:52,625 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
pi@raspberrypi:~ $
P. S Czy jeśli już mi to ruszy, to będę mógł normalnie dodawać urządzenia, smartfony i korzystać z podłączonych modolow zarówno w domu będąc w sieci lokalnej jak i poza domem gdy w tej sieci nie będę? Czy muszę jeszcze dodatkowo coś ustawiać?