Skip to content
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

Data stops updating #12

Closed
rosskukulinski opened this issue Jan 26, 2015 · 2 comments
Closed

Data stops updating #12

rosskukulinski opened this issue Jan 26, 2015 · 2 comments
Labels

Comments

@rosskukulinski
Copy link
Member

Using fleetctl, I see a unit is stopped/failed, but in CoreGI it's being reported as RUNNING.

REST API for CoreGI also reports RUNNING, so it must be a backend issue.

@rosskukulinski
Copy link
Member Author

Seems stopping/starting the service again resolved the issue. Will keep an eye on this.

@rosskukulinski rosskukulinski changed the title Stopped units not displaying correctly? Data stops updating Feb 18, 2015
@rosskukulinski
Copy link
Member Author

This is still an issue, which is why we're adding improved logging in #14.

Potentially https://github.com/ncb000gt/node-cron/issues/141 is causing problems as this problem has only recently come up (in the last month or so).

New logs should allow us to see exactly what the issue. Possible solutions include:

  • We can/should pin to node-cron@1.0.5
  • We should take advantage of the TTL value in memory-store to flush expired data

rosskukulinski added a commit that referenced this issue Feb 23, 2015
rosskukulinski pushed a commit that referenced this issue Feb 24, 2015
Pin node-cron version re: #12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant