Git Product home page Git Product logo

Comments (4)

willoughby avatar willoughby commented on May 26, 2024

I was able to resolve my issue. New to the ecosystem but had to add the following to my Application:

worker(Bolt.Sips, [ Application.get_env(:bolt_sips, Bolt)])

from bolt_sips.

florinpatrascu avatar florinpatrascu commented on May 26, 2024

That’s the correct solution! :)

from bolt_sips.

florinpatrascu avatar florinpatrascu commented on May 26, 2024

the latest version 0.4.11, has its README updated with an example clarifying this aspect. Thank you @willoughby, for suggesting it!

from bolt_sips.

gamebox avatar gamebox commented on May 26, 2024

I am still seeing a similar issue. Running Phoenix 1.3.4 with OTP 20 and Elixir 1.7. Starting a new phoenix project(no brunch, no ecto) adding only the things needed per the README, and I get this:

** (Mix) Could not start application phx_issues: PhxIssues.Application.start(:normal, []) returned an error: shutdown: failed to start child: PhxIssuesWeb.Endpoint
    ** (EXIT) shutdown: failed to start child: Phoenix.Endpoint.Handler
        ** (EXIT) shutdown: failed to start child: {:ranch_listener_sup, PhxIssuesWeb.Endpoint.HTTP}
            ** (EXIT) exited in: :gen_server.call(:ranch_server, {:set_new_listener_opts, PhxIssuesWeb.Endpoint.HTTP, 16384, [env: [dispatch: [{:_, [], [{["phoenix", "live_reload", "socket", "longpoll"], [], Plug.Adapters.Cowboy.Handler, {Phoenix.Transports.LongPoll, {PhxIssuesWeb.Endpoint, Phoenix.LiveReloader.Socket, :longpoll}}}, {["phoenix", "live_reload", "socket", "websocket"], [], Phoenix.Endpoint.CowboyWebSocket, {Phoenix.Transports.WebSocket, {PhxIssuesWeb.Endpoint, Phoenix.LiveReloader.Socket, :websocket}}}, {["socket", "websocket"], [], Phoenix.Endpoint.CowboyWebSocket, {Phoenix.Transports.WebSocket, {PhxIssuesWeb.Endpoint, PhxIssuesWeb.UserSocket, :websocket}}}, {:_, [], Plug.Adapters.Cowboy.Handler, {PhxIssuesWeb.Endpoint, []}}]}]], onresponse: #Function<1.129103586/4 in Plug.Adapters.Cowboy.add_on_response/3>]})
                ** (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

I have a more mature app that I've added bolt_sips to receive a similar, but not identical error.

from bolt_sips.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.