Crash after updating to v1.21.0

[ian-mcdowell]

Describe the bug

After updating teslamate to version v1.21.0, the docker container fails to start.

Relevant entries from the logs

Crash dump is being written to: erl_crash.dump...done
2021-01-04 21:02:19.751 [info] Migrations already up
2021-01-04 21:02:23.492 [info] Version: 1.21.0

2021-01-04 21:02:31.624 [info] Application teslamate exited: TeslaMate.Application.start(:normal, []) returned an error: shutdown: failed to start child: TeslaMate.Api

** (EXIT) an exception was raised:
** (CaseClauseError) no case clause matching: {:error, "non-existing domain"}

(teslamate 1.21.0) lib/tesla_api/auth.ex:44: TeslaApi.Auth.handle_response/1
(teslamate 1.21.0) lib/teslamate/api.ex:171: TeslaMate.Api.refresh_tokens/1
(teslamate 1.21.0) lib/teslamate/api.ex:99: TeslaMate.Api.init/1
(stdlib 3.14) gen_server.erl:417: :gen_server.init_it/2
(stdlib 3.14) gen_server.erl:385: :gen_server.init_it/6
(stdlib 3.14) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
{"Kernel pid terminated",application_controller,"{application_start_failure,teslamate,{{shutdown,{failed_to_start_child,'Elixir.TeslaMate.Api',{{case_clause,{error,<<\"non-existing domain\">>}},[{'Elixir.TeslaApi.Auth',handle_response,1,[{file,\"lib/tesla_api/auth.ex\"},{line,44}]},{'Elixir.TeslaMate.Api',refresh_tokens,1,[{file,\"lib/teslamate/api.ex\"},{line,171}]},{'Elixir.TeslaMate.Api',init,1,[{file,\"lib/teslamate/api.ex\"},{line,99}]},{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,417}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,385}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,226}]}]}}},{'Elixir.TeslaMate.Application',start,[normal,[]]}}}"}

Environment

• TeslaMate version: 1.21.0
• Type of installation: Docker

[trulow]

Did you double check your docker-compose or your .env file?

Looks like you might have an invalid Fqdn in your settings

[frietbakker]

I have this same error with a fresh install on a Synology

[ian-mcdowell]

Here's my docker command:

docker run -d --name='TeslaMate' --net='private' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'DATABASE_USER'='teslamate' -e 'DATABASE_PASS'='<redacted>' -e 'DATABASE_NAME'='teslamate' -e 'DATABASE_HOST'='TeslaMate-postgres' -e 'MQTT_HOST'='TeslaMate-mosquitto' -v '/mnt/user/appdata/teslamate/import':'/opt/app/import':'rw' 'teslamate/teslamate:latest'

The FQDN has not changed since I initially configured it. It may not be resolvable from the container, since it's in a private network. This has not been a problem in the past, however.

[teslaballa]

I had the same problem upgrading (on a QNAP)) and I solved it only by deleting the docker, restarting the server and creating it again.
Fortunately I didn't loose any data :-)

[JonasPerssonSE]

Having a similar problem on my Synology NAS:

2021-01-26 19:50:56	stdout	waiting for postgres at database:5432 (2sec)
2021-01-26 19:51:04	stdout	2021-01-26 19:51:04.160 [info] Migrations already up
2021-01-26 19:51:06	stdout	2021-01-26 19:51:06.371 [info] Version: 1.21.1
2021-01-26 19:51:09	stdout	
2021-01-26 19:51:09	stdout	
2021-01-26 19:51:09	stdout	
2021-01-26 19:51:09	stdout	2021-01-26 19:51:09.373 [info] Application teslamate exited: TeslaMate.Application.start(:normal, []) returned an error: shutdown: failed to start child: TeslaMate.Api
2021-01-26 19:51:09	stdout	  1. Tracking down slow queries and making sure they are running fast enough
2021-01-26 19:51:09	stdout	  2. Increasing the pool_size (albeit it increases resource consumption)
2021-01-26 19:51:09	stdout	  3. Allowing requests to wait longer by increasing :queue_target and :queue_interval
2021-01-26 19:51:09	stdout	            (ecto 3.5.5) lib/ecto/repo/queryable.ex:17: Ecto.Repo.Queryable.all/3
2021-01-26 19:51:09	stdout	            (ecto 3.5.5) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
2021-01-26 19:51:09	stdout	            (ecto_sql 3.5.3) lib/ecto/adapters/sql.ex:684: Ecto.Adapters.SQL.execute/5
2021-01-26 19:51:09	stdout	            (ecto_sql 3.5.3) lib/ecto/adapters/sql.ex:751: Ecto.Adapters.SQL.raise_sql_call_error/1
2021-01-26 19:51:09	stdout	            (stdlib 3.14) gen_server.erl:385: :gen_server.init_it/6
2021-01-26 19:51:09	stdout	            (stdlib 3.14) gen_server.erl:417: :gen_server.init_it/2
2021-01-26 19:51:09	stdout	            (teslamate 1.21.1) lib/teslamate/api.ex:96: TeslaMate.Api.init/1
2021-01-26 19:51:09	stdout	            (teslamate 1.21.1) lib/teslamate/auth.ex:22: TeslaMate.Auth.get_tokens/0
2021-01-26 19:51:09	stdout	        ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
2021-01-26 19:51:09	stdout	    ** (EXIT) an exception was raised:
2021-01-26 19:51:09	stdout	See DBConnection.start_link/2 for more information
2021-01-26 19:51:10	stderr	
2021-01-26 19:51:10	stderr	Kernel pid terminated (application_controller) ({application_start_failure,teslamate,{{shutdown,{failed_to_start_child,'Elixir.TeslaMate.Api',{#{'__exception__' => true,'__struct__' => 'Elixir.DBConne
2021-01-26 19:51:10	stdout	{"Kernel pid terminated",application_controller,"{application_start_failure,teslamate,{{shutdown,{failed_to_start_child,'Elixir.TeslaMate.Api',{#{'__exception__' => true,'__struct__' => 'Elixir.DBConnection.ConnectionError',message => <<\"connection not available and request was dropped from queue after 2999ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n  1. Tracking down slow queries and making sure they are running fast enough\n  2. Increasing the pool_size (albeit it increases resource consumption)\n  3. Allowing requests to wait longer by increasing :queue_target and :queue_interval\n\nSee DBConnection.start_link/2 for more information\n\">>,reason => queue_timeout,severity => error},[{'Elixir.Ecto.Adapters.SQL',raise_sql_call_error,1,[{file,\"lib/ecto/adapters/sql.ex\"},{line,751}]},{'Elixir.Ecto.Adapters.SQL',execute,5,[{file,\"lib/ecto/adapters/sql.ex\"},{line,684}]},{'Elixir.Ecto.Repo.Queryable',execute,4,[{file,\"lib/ecto/repo/queryable.ex\"},{line,229}]},{'Elixir.Ecto.Repo.Queryable',all,3,[{file,\"lib/ecto/repo/queryable.ex\"},{line,17}]},{'Elixir.TeslaMate.Auth',get_tokens,0,[{file,\"lib/teslamate/auth.ex\"},{line,22}]},{'Elixir.TeslaMate.Api',init,1,[{file,\"lib/teslamate/api.ex\"},{line,96}]},{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,417}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,385}]}]}}},{'Elixir.TeslaMate.Application',start,[normal,[]]}}}"}
2021-01-26 19:51:11	stderr	Crash dump is being written to: erl_crash.dump...done

I cannot open Teslamate page. Only Grafana. Any suggestions?

Edit:

• I have never got it to work.
• Fresh install and tried many times reinstall it.
• Have tried earlier version of Docker as suggested in different post. But as I can understand, that bug is fixed in newer version of Docker.
• Ports are open and are ping-able
• Had to manually create "import" folder in "@docker" and that fixed the installation problem I had in the beginning.
• Using standard docker-compose.yml file

[JonasPerssonSE]

So, I'm about to give up on this... Anyone know what to do?

[JonasPerssonSE]

ping @adriankumpf

[teslaballa]

Sorry, I’m not an expert. I solved the problem removing the docker and reinstalling it.

…

Il giorno 31 gen 2021, alle ore 13:06, JonasPerssonSE ***@***.***> ha scritto: So, I'm about to give up on this... Anyone know what to do? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1238 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASQHHSFQ3PFLAYAAR6BK3RLS4VBU3ANCNFSM4WU2QOLA>.