-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daemons::Rails::Monitoring.statuses doesn't work in production #14
Comments
Do you have only one production server and are daemons running on same machine as application? |
yes, only 1 production server |
Ok. |
daemons are in lib/daemons bundle exec lib/daemons/<your_daemon_name>_ctl status Daemons::Rails::Monitoring.default.controllers works fine in console production, but when i do <%= Daemons::Rails::Monitoring.statuses["daemons.rb"] %> in the view it return "not_exists". |
Is it behave same if you set instance variable in controller and then display in view? Also, it may be result of page caching and actually you see old version of page when daemons not yet run. So, try to add timestamp to this page - will it change on reload? It it will not help - it may be helpful if you create simplest not working version of application and send me by email or share through github. I just checked your use case and it works for me, so I need more details to find problem. |
just tried setting the instance variable in the controller but no dice. still shows not_exists when the daemons are clearly running. I'm using Rails 4.0.0 and daemons-rails (1.2.1) and ruby 2.0.0p247. oh another piece of info, I had to comment out this line in my daemon or it wouldn't start. I don't know if that has anything to do with this problem: |
@rickygu @hospital-systems Did you get this fixed? I'm having the same issue when deploying to a Digital Ocean VPS running Dokku. |
When I call Daemons::Rails::Monitoring.statuses in development, it works fine, but on my production server, it returns not_exists even though the daemons are running.
The text was updated successfully, but these errors were encountered: