Development server freezes regularly
My development server (run with `foreman start`) constantly freezes. This is probably a noob error since I'm just getting started with JSP.
I run my JSP app with `foreman start`, which launches the usual processes:
```
web: bin/rails server -p 3000
css: yarn build:css --watch
js: yarn build --watch
# docker: docker-compose up
worker: bundle exec sidekiq
stripe: stripe listen --forward-to localhost:3000/webhooks/stripe
guard: bundle exec guard
```
After a few clicks in my application (my hunch is that it most often follows a switch of user accounts), my application only shows the loading progress bar forever. I cannot see anything really in the logs. However, I sometimes do see this:
```
[ActionCable] [User 1] [Account 1] Could not execute command from ({"command"=>"unsubscribe", ...
```
But it is followed by more logs – including successful ones by ActionCable. I don't know, if this could be the problem.
Once the app is frozen, even the usual Ctrl-C doesn't help as it freezes my terminal tab. I always have to do a `q` followed by return to quit all processes and then restart the server.
Any idea what I'm missing?
I run my JSP app with `foreman start`, which launches the usual processes:
```
web: bin/rails server -p 3000
css: yarn build:css --watch
js: yarn build --watch
# docker: docker-compose up
worker: bundle exec sidekiq
stripe: stripe listen --forward-to localhost:3000/webhooks/stripe
guard: bundle exec guard
```
After a few clicks in my application (my hunch is that it most often follows a switch of user accounts), my application only shows the loading progress bar forever. I cannot see anything really in the logs. However, I sometimes do see this:
```
[ActionCable] [User 1] [Account 1] Could not execute command from ({"command"=>"unsubscribe", ...
```
But it is followed by more logs – including successful ones by ActionCable. I don't know, if this could be the problem.
Once the app is frozen, even the usual Ctrl-C doesn't help as it freezes my terminal tab. I always have to do a `q` followed by return to quit all processes and then restart the server.
Any idea what I'm missing?
Not an answer to your exact question, but I've found overmind to be a bit more reliable than foreman. I was encountering the same issue you describe with foreman (and never could figure out the cause), but haven't ran into it since switching.
This also seems to be the preferred process manager now: https://github.com/jumpstart-pro/jumpstart-pro/pull/87
This also seems to be the preferred process manager now: https://github.com/jumpstart-pro/jumpstart-pro/pull/87
Notifications
You’re not receiving notifications from this thread.