Sometimes getting :noproc error

Once in a while I get a :noproc error:

** (stop) exited in:{:via, Registry, {:trip_generation_server, "804194805327673"}}, :send_to_processing, 5000)
    ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
    (elixir 1.14.2) lib/gen_server.ex:1027:
    (vehicle_processing 0.1.0) lib/vehicle_processing/processor.ex:1243: VehicleProcessing.Processor.run_trip_generation_server/3
    (stdlib 4.2) gen_server.erl:1161: :gen_server.try_terminate/3
    (stdlib 4.2) gen_server.erl:1351: :gen_server.terminate/10
    (stdlib 4.2) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
Last message: :check_end_of_processing
State: %VehicleProcessing.Processor.State{vehicle: nil, unique_identifier: "804194805327673", data_start_at: nil, data_stop_at: nil, last_active_at: ~U[2023-10-30 10:30:47.181818Z], parking_notification_sent: false, driver_id: %{ibutton: nil, log: nil, permission: nil}, gps_based_properties: %{distance: nil, speed: nil, time: nil}, sent_vehicle_start_trigger?: false, at_least_one_non_heartbeat_message?: true, messages: [], timer: #Reference<0.3285835207.3288072193.194993>, geofences: [], previous_trip_point: nil, gps_reference: nil, previous_state_of_charge: nil, notifications_sent: %{battery_level_low: nil, battery_range_low: nil, battery_state_of_charge_low: nil}, gps_send: 1}

I start the TripGenerationServer dynamically:

  defp run_trip_generation_server(state, f, tries) do
    if tries > 0 do
      case Registry.lookup(:trip_generation_server, state.unique_identifier) do
        [] ->
          case TripGenerationServerSupervisor.start_child(state.unique_identifier) do
            {:ok, _pid} ->

            e ->
                "Can not start TripGenerationServer #{state.unique_identifier}: #{inspect(e)}"

              run_trip_generation_server(state, f, tries - 1)

        [{_pid, _nil}] ->
      Logger.error("Can not startTripGenerationServer #{state.unique_identifier}")


And I get the :noproc error when

   [{_pid, _nil}] ->
defmodule VehicleProcessing.TripGenerationServerSupervisor do
  @moduledoc false

  use DynamicSupervisor
  require Logger
  alias VehicleProcessing.TripGenerationServer

  def start_link(_) do"start #{__MODULE__}")
    DynamicSupervisor.start_link(__MODULE__, [], name: __MODULE__)

  def start_child(unique_identifier) do
    child_spec = %{
      id: TripGenerationServer,
      start: {TripGenerationServer, :start, [unique_identifier]},
      # the child process is restarted only if it terminates abnormally,
      # i.e., with an exit reason other than :normal, :shutdown, or {:shutdown, term}
      restart: :transient,
      shutdown: :brutal_kill,
      type: :worker,
      modules: [TripGenerationServer]

    DynamicSupervisor.start_child(__MODULE__, child_spec)

  @impl true
  def init([]) do
    DynamicSupervisor.init(strategy: :one_for_one)

How is this possible?
It also happens sometimes in a test, and when I run the test again, the error does not appear; or it appears in another test, totally random.

At least in test env it’s possible the process is exiting before the test completes?

That also sometimes happens, but in this case I get {:ok, pid} but still the :noprocess error.

I did not show this in my question, but in my init/1 function of the TripGenerationServer a query to the DB was called:

  def init(imei) do
       imei: imei,
       from_ts: nil,
       to_ts: nil,
       should_send_to_processing: should_send_to_processing?(imei),
         Application.get_env(:vehicle_processing, :trip_split_interval_in_seconds) || 300,
       ts: now_ts()
     }, {:continue, :initial_state}}

is a call to the DB.
I removed that, and not seen the error again in my tests.

So is it possible that we get {:ok, pid} back already before the init/1 function is complete?

Oh, don’t do that. I am not sure that’s your problem but always do these with handle_continue!

Also a piece from handle_call docs:

Returning {:reply, reply, new_state, {:continue, continue_arg}} is similar to {:reply, reply, new_state} except that handle_continue/2 will be invoked immediately after with continue_arg as the first argument and state as the second one.

1 Like

One thought: TripGenerationServerSupervisor.start_child will return the child PID as soon as the process is started, but a call using a via tuple won’t succeed until the child process has registered (presumably using code in TripGenerationServer)

The error you’re seeing could happen if the callback passed to run_trip_generation_server “wins the race” and tries to make a call too early.

1 Like