Production deployment with gunicorn - notifications not working #3661
Replies: 3 comments
-
|
I see the problem -- the notification stream specifically checks if the cherrypy server is running and stops if it isn't. I'll have a fix shortly. |
Beta Was this translation helpful? Give feedback.
-
|
I have it enabled. I see the requests going to GET /notification/stream, they get 200 response (quickly). with for girder container notifications are picked up immediately. It's clearly a matter how I run it, not Girder's fault at all. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have the Server Notification Stream enabled in the system configuration / advanced settings? If so, then I don't know why it isn't working. If not, then the large_image plugin has an optional polling fallback that really should be moved into core. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I switched to gunicorn for production deployments (and v4-integration branch). Everything seemed to work smoothly until I noticed that notifications are not working properly. It looks like GET /notification/stream is closed almost instantly with 200, instead of keeping the connection alive. I tried
geventas gunicorn worker but that didn't help. Do you have any hints how to make it work? What am I missing?Beta Was this translation helpful? Give feedback.
All reactions