chattes
Hello Experts,
I am just starting to play with Supervisors and I have created the Project using mix new podder --sup
I get the Following error when I try to Invoke a Process using the Dynamic Supervisor.
This is my code.
I am using Elixir 1.7.3.
Applicaiton.ex
defmodule Podder.Application do
# See https://hexdocs.pm/elixir/Application.html
# for more information on OTP Applications
@moduledoc false
use Application
def start(_type, _args) do
# List all child processes to be supervised
children = [
# Starts a worker by calling: Podder.Worker.start_link(arg)
# {Podder.Worker, arg},
%{
id: Podder.DynamicSupervisor,
start: {Podder.DynamicSupervisor, :start_link, []}
}
]
# See https://hexdocs.pm/elixir/Supervisor.html
# for other strategies and supported options
opts = [strategy: :one_for_one, name: Podder.DynamicSupervisor]
Supervisor.start_link(children, opts)
end
end
Supervisor
defmodule Podder.DynamicSupervisor do
use DynamicSupervisor
def start_link() do
DynamicSupervisor.start_link(__MODULE__, :ok, name: __MODULE__)
end
@doc """
Server Side
"""
def init(_arg) do
DynamicSupervisor.init(strategy: :one_for_one)
end
def start_work do
{:ok, pid} = start_podcast_server
end
defp start_podcast_server do
spec = %{id: Podder, start: {Podder, :start_link, []}}
DynamicSupervisor.start_child(__MODULE__, spec)
end
end
GenServer
defmodule Podder do
use GenServer
@moduledoc """
Documentation for Podder.
"""
@doc """
Hello world.
## Examples
iex> Podder.hello()
:world
"""
def init(state) do
{:ok, state}
end
def handle_call(:fetch, _from, state) do
new_state = Map.put(state, "fetched", 1)
{:reply, new_state, new_state}
end
def handle_call(:get_state, _from, state) do
{:reply, state, state}
end
@doc """
Client Implementation
"""
def start_link(state) do
GenServer.start_link(__MODULE__, state)
end
def fetch_episodes(pid) do
GenServer.call(pid, :fetch)
end
def get_episodes(pid) do
GenServer.call(pid, :get_state)
end
end
I am trying this from iex
iex(4)> Podder.DynamicSupervisor.start_work
** (MatchError) no match of right hand side value: {:error, {:invalid_child_spec, {{Podder, :start_link, []}, :permanent, 5000, :worker, [Podder]}}}
(podder) lib/podcastsupervisor.ex:16: Podder.DynamicSupervisor.start_work/0
iex(4)>
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
saulecabrera
The error that you’re experiencing is because in
Podder.DynamicSupervisor/start_podcast_serveryou have defined the child spec as%{id: Podder, start: {Podder, :start_link, []}}, which means that when the dynamic supervisor tries to start the child, it will invokePodder.start_link/0with no arguments, but in yourPoddermodule you have no such definition, instead you havePodder.start_link/1.This can be fixed by either defining
Podder.start_link/0or by passing a param to the child spec inPodder.DynamicSupervisor/start_podcast_server(i.e.%{id: Podder, start: {Podder, :start_link, [:ok]}})chattes
Sorry that was my mistake.
But actually I am do passing the args , in the updated code as so.
But I still get the same error running in iex
saulecabrera
I tried replicating your code in a new mix project, may I ask how are you starting iex?
I tried running
iex -S mixand the application is not even able to start because the current code is registering two processes with the same name (Podder.DynamicSupervisor), one for the top level supervisor and another for the actual DynamicSupervisor:The name for the top level supervisor is normally omitted, unless you actually need it:
With those changes I was able to succesfully call
Podder.DynamicSupervisor.start_workdavid_ex
Have you tried
Typically, I think providing a child spec “by hand” is asking for trouble. If you’re interested, I’ve covered child specs and dynamic supervisors in more depth at http://davidsulc.com/blog/2018/07/10/pooltoy-a-toy-process-pool-manager-in-elixir-1-6-part-1-9/
chattes
Yeah , I think I understand now what i was doing wrong.
So basically Supervisor.start_link starts the main process along with the Child Processes in my case the Dynamic Supervisor.
I was duplicating the process name and I think that probably did not even start the child process.
Even i got the error, but was unable to wrap my head around what it is.
Its a lot clearer for me now.
Thanks for the help!