API tools faq
paste
Advertisement
Guest User

(DBConnection.ConnectionError) connection not available and request was dropped from queue after 298

a guest
Jan 17th, 2024
31
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.66 KB | None | 0 0
raw download clone embed print report
  1. 2024-01-17 11:55:31 08:55:31.732 [info] Loading 140 CA(s) from :otp store
  2. 2024-01-17 11:55:31 08:55:31.875 [notice] Application mnesia exited: :stopped
  3. 2024-01-17 11:55:31 08:55:31.921 [error] Postgrex.Protocol (#PID<0.3938.0>) failed to connect: ** (Postgrex.Error) ssl not available
  4. 2024-01-17 11:55:31 08:55:31.923 [error] Postgrex.Protocol (#PID<0.3945.0>) failed to connect: ** (Postgrex.Error) ssl not available
  5. 2024-01-17 11:55:31 08:55:31.923 [error] Postgrex.Protocol (#PID<0.3946.0>) failed to connect: ** (Postgrex.Error) ssl not available
  6. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3937.0>) failed to connect: ** (Postgrex.Error) ssl not available
  7. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3947.0>) failed to connect: ** (Postgrex.Error) ssl not available
  8. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3948.0>) failed to connect: ** (Postgrex.Error) ssl not available
  9. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3939.0>) failed to connect: ** (Postgrex.Error) ssl not available
  10. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3942.0>) failed to connect: ** (Postgrex.Error) ssl not available
  11. 2024-01-17 11:55:31 08:55:31.924 [error] Postgrex.Protocol (#PID<0.3944.0>) failed to connect: ** (Postgrex.Error) ssl not available
  12. 2024-01-17 11:55:31 08:55:31.927 [error] Postgrex.Protocol (#PID<0.3943.0>) failed to connect: ** (Postgrex.Error) ssl not available
  13. 2024-01-17 11:55:33 08:55:33.123 [error] Postgrex.Protocol (#PID<0.3947.0>) failed to connect: ** (Postgrex.Error) ssl not available
  14. 2024-01-17 11:55:33 08:55:33.211 [error] Postgrex.Protocol (#PID<0.3939.0>) failed to connect: ** (Postgrex.Error) ssl not available
  15. 2024-01-17 11:55:33 08:55:33.869 [error] Postgrex.Protocol (#PID<0.3948.0>) failed to connect: ** (Postgrex.Error) ssl not available
  16. 2024-01-17 11:55:34 08:55:34.069 [error] Postgrex.Protocol (#PID<0.3938.0>) failed to connect: ** (Postgrex.Error) ssl not available
  17. 2024-01-17 11:55:34 08:55:34.265 [error] Postgrex.Protocol (#PID<0.3943.0>) failed to connect: ** (Postgrex.Error) ssl not available
  18. 2024-01-17 11:55:34 08:55:34.483 [error] Postgrex.Protocol (#PID<0.3945.0>) failed to connect: ** (Postgrex.Error) ssl not available
  19. 2024-01-17 11:55:34 08:55:34.600 [error] Postgrex.Protocol (#PID<0.3944.0>) failed to connect: ** (Postgrex.Error) ssl not available
  20. 2024-01-17 11:55:34 08:55:34.602 [error] Postgrex.Protocol (#PID<0.3946.0>) failed to connect: ** (Postgrex.Error) ssl not available
  21. 2024-01-17 11:55:34 08:55:34.690 [error] Postgrex.Protocol (#PID<0.3942.0>) failed to connect: ** (Postgrex.Error) ssl not available
  22. 2024-01-17 11:55:34 08:55:34.887 [error] Postgrex.Protocol (#PID<0.3937.0>) failed to connect: ** (Postgrex.Error) ssl not available
  23. 2024-01-17 11:55:34 08:55:34.909 [error] GenServer {Oban.Registry, {Oban, Oban.Peer}} terminating
  24. 2024-01-17 11:55:34 ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2988ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
  25. 2024-01-17 11:55:34
  26. 2024-01-17 11:55:34 1. Ensuring your database is available and that you can connect to it
  27. 2024-01-17 11:55:34 2. Tracking down slow queries and making sure they are running fast enough
  28. 2024-01-17 11:55:34 3. Increasing the pool_size (although this increases resource consumption)
  29. 2024-01-17 11:55:34 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
  30. 2024-01-17 11:55:34
  31. 2024-01-17 11:55:34 See DBConnection.start_link/2 for more information
  32. 2024-01-17 11:55:34
  33. 2024-01-17 11:55:34 (db_connection 2.6.0) lib/db_connection.ex:1059: DBConnection.transaction/3
  34. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/peers/postgres.ex:94: anonymous fn/2 in Oban.Peers.Postgres.handle_info/2
  35. 2024-01-17 11:55:34 (telemetry 1.2.1) /app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
  36. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/peers/postgres.ex:92: Oban.Peers.Postgres.handle_info/2
  37. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:1067: :gen_server.try_handle_continue/3
  38. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:977: :gen_server.loop/7
  39. 2024-01-17 11:55:34 (stdlib 5.0.2) proc_lib.erl:241: :proc_lib.init_p_do_apply/3
  40. 2024-01-17 11:55:34 Last message: {:continue, :start}
  41. 2024-01-17 11:55:34 08:55:34.911 [error] GenServer {Oban.Registry, {Oban, Oban.Stager}} terminating
  42. 2024-01-17 11:55:34 ** (stop) exited in: GenServer.call(#PID<0.3951.0>, :leader?, 5000)
  43. 2024-01-17 11:55:34 ** (EXIT) an exception was raised:
  44. 2024-01-17 11:55:34 ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 2988ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
  45. 2024-01-17 11:55:34
  46. 2024-01-17 11:55:34 1. Ensuring your database is available and that you can connect to it
  47. 2024-01-17 11:55:34 2. Tracking down slow queries and making sure they are running fast enough
  48. 2024-01-17 11:55:34 3. Increasing the pool_size (although this increases resource consumption)
  49. 2024-01-17 11:55:34 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
  50. 2024-01-17 11:55:34
  51. 2024-01-17 11:55:34 See DBConnection.start_link/2 for more information
  52. 2024-01-17 11:55:34
  53. 2024-01-17 11:55:34 (db_connection 2.6.0) lib/db_connection.ex:1059: DBConnection.transaction/3
  54. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/peers/postgres.ex:94: anonymous fn/2 in Oban.Peers.Postgres.handle_info/2
  55. 2024-01-17 11:55:34 (telemetry 1.2.1) /app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
  56. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/peers/postgres.ex:92: Oban.Peers.Postgres.handle_info/2
  57. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:1067: :gen_server.try_handle_continue/3
  58. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:977: :gen_server.loop/7
  59. 2024-01-17 11:55:34 (stdlib 5.0.2) proc_lib.erl:241: :proc_lib.init_p_do_apply/3
  60. 2024-01-17 11:55:34 (elixir 1.15.4) lib/gen_server.ex:1074: GenServer.call/3
  61. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/peer.ex:99: Oban.Peer.leader?/2
  62. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/stager.ex:101: Oban.Stager.check_leadership_and_stage/1
  63. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/stager.ex:75: anonymous fn/2 in Oban.Stager.handle_info/2
  64. 2024-01-17 11:55:34 (telemetry 1.2.1) /app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
  65. 2024-01-17 11:55:34 (oban 2.16.2) lib/oban/stager.ex:74: Oban.Stager.handle_info/2
  66. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:1077: :gen_server.try_handle_info/3
  67. 2024-01-17 11:55:34 (stdlib 5.0.2) gen_server.erl:1165: :gen_server.handle_msg/6
  68. 2024-01-17 11:55:34 Last message: :stage
  69. 2024-01-17 11:55:34 08:55:34.935 [error] Postgrex.Protocol (#PID<0.3939.0>) failed to connect: ** (Postgrex.Error) ssl not available
  70. 2024-01-17 11:55:35 08:55:35.203 [error] Postgrex.Protocol (#PID<0.3947.0>) failed to connect: ** (Postgrex.Error) ssl not available
  71. 2024-01-17 11:55:36 08:55:36.142 [info] tzdata release in place is from a file last modified Fri, 22 Oct 2021 02:20:47 GMT. Release file on server was last modified Fri, 22 Dec 2023 09:25:37 GMT.
  72. 2024-01-17 11:55:36 08:55:36.906 [error] GenServer {Oban.Registry, {Oban, Oban.Peer}} terminating
  73. 2024-01-17 11:55:36 ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 1993ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:
  74. 2024-01-17 11:55:36
  75. 2024-01-17 11:55:36 1. Ensuring your database is available and that you can connect to it
  76. 2024-01-17 11:55:36 2. Tracking down slow queries and making sure they are running fast enough
  77. 2024-01-17 11:55:36 3. Increasing the pool_size (although this increases resource consumption)
  78. 2024-01-17 11:55:36 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval
  79. 2024-01-17 11:55:36
  80. 2024-01-17 11:55:36 See DBConnection.start_link/2 for more information
  81. 2024-01-17 11:55:36
  82. 2024-01-17 11:55:36 (db_connection 2.6.0) lib/db_connection.ex:1059: DBConnection.transaction/3
  83. 2024-01-17 11:55:36 (oban 2.16.2) lib/oban/peers/postgres.ex:94: anonymous fn/2 in Oban.Peers.Postgres.handle_info/2
  84. 2024-01-17 11:55:36 (telemetry 1.2.1) /app/deps/telemetry/src/telemetry.erl:321: :telemetry.span/3
  85. 2024-01-17 11:55:36 (oban 2.16.2) lib/oban/peers/postgres.ex:92: Oban.Peers.Postgres.handle_info/2
  86. 2024-01-17 11:55:36 (stdlib 5.0.2) gen_server.erl:1067: :gen_server.try_handle_continue/3
  87. 2024-01-17 11:55:36 (stdlib 5.0.2) gen_server.erl:977: :gen_server.loop/7
  88. 2024-01-17 11:55:36 (stdlib 5.0.2) proc_lib.erl:241: :proc_lib.init_p_do_apply/3
  89. 2024-01-17 11:55:36 Last message: {:continue, :start}
  90. 2024-01-17 11:55:36 08:55:36.909 [notice] Application lightning exited: Lightning.Application.start(:normal, [:timex]) returned an error: shutdown: failed to start child: Cachex
  91. 2024-01-17 11:55:36 ** (EXIT) an exception was raised:
  92. 2024-01-17 11:55:36 ** (MatchError) no match of right hand side value: {:error, {:shutdown, {:failed_to_start_child, Cachex.Services.Incubator, {:shutdown, {:failed_to_start_child, Lightning.AuthProviders.CacheWarmer, {%DBConnection.ConnectionError{message: "connection not available and request was dropped from queue after 2962ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n 1. Ensuring your database is available and that you can connect to it\n 2. Tracking down slow queries and making sure they are running fast enough\n 3. Increasing the pool_size (although this increases resource consumption)\n 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\n\nSee DBConnection.start_link/2 for more information\n", severity: :error, reason: :queue_timeout}, [{Ecto.Adapters.SQL, :raise_sql_call_error, 1, [file: ~c"lib/ecto/adapters/sql.ex", line: 1047, error_info: %{module: Exception}]}, {Ecto.Adapters.SQL, :execute, 6, [file: ~c"lib/ecto/adapters/sql.ex", line: 945]}, {Ecto.Repo.Queryable, :execute, 4, [file: ~c"lib/ecto/repo/queryable.ex", line: 229]}, {Ecto.Repo.Queryable, :all, 3, [file: ~c"lib/ecto/repo/queryable.ex", line: 19]}, {Ecto.Repo.Queryable, :one, 3, [file: ~c"lib/ecto/repo/queryable.ex", line: 151]}, {Lightning.AuthProviders.CacheWarmer, :execute, 1, [file: ~c"lib/lightning/auth_providers/cache_warmer.ex", line: 24]}, {Lightning.AuthProviders.CacheWarmer, :handle_info, 2, [file: ~c"deps/cachex/lib/cachex/warmer.ex", line: 95]}, {Lightning.AuthProviders.CacheWarmer, :init, 1, [file: ~c"deps/cachex/lib/cachex/warmer.ex", line: 79]}]}}}}}}
  93. 2024-01-17 11:55:36 (cachex 3.6.0) lib/cachex.ex:301: Cachex.start_link/1
  94. 2024-01-17 11:55:36 (stdlib 5.0.2) supervisor.erl:420: :supervisor.do_start_child_i/3
  95. 2024-01-17 11:55:36 (stdlib 5.0.2) supervisor.erl:406: :supervisor.do_start_child/2
  96. 2024-01-17 11:55:36 (stdlib 5.0.2) supervisor.erl:390: anonymous fn/3 in :supervisor.start_children/2
  97. 2024-01-17 11:55:36 (stdlib 5.0.2) supervisor.erl:1256: :supervisor.children_map/4
  98. 2024-01-17 11:55:36 (stdlib 5.0.2) supervisor.erl:350: :supervisor.init_children/2
  99. 2024-01-17 11:55:36 (stdlib 5.0.2) gen_server.erl:962: :gen_server.init_it/2
  100. 2024-01-17 11:55:36 (stdlib 5.0.2) gen_server.erl:917: :gen_server.init_it/6
  101. 2024-01-17 11:55:38 Kernel pid terminated (application_controller) ({application_start_failure,lightning,{{shutdown,{failed_to_start_child,'Elixir.Cachex',{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,'Elixir.Cachex.Services.Incubator',{shutdown,{failed_to_start_child,'Elixir.Lightning.AuthProviders.CacheWarmer',{#{message => <<"connection not available and request was dropped from queue after 2962ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n 1. Ensuring your database is available and that you can connect to it\n 2. Tracking down slow queries and making sure they are running fast enough\n 3. Increasing the pool_size (although this increases resource consumption)\n 4. 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,'__struct__' => 'Elixir.DBConnection.ConnectionError','__exception__' => true,severity => error},[{'Elixir.Ec
  102. 2024-01-17 11:55:38
  103. 2024-01-17 11:55:38 Crash dump is being written to: erl_crash.dump...Segmentation fault
  104.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!