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.

Sign up for GitHub

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

Jump to bottom

Nightscout won't stop crashing #4566

Closed
Propelld opened this issue Apr 28, 2019 · 17 comments
Closed

Nightscout won't stop crashing #4566

Propelld opened this issue Apr 28, 2019 · 17 comments

Comments

@Propelld
Copy link

Propelld commented Apr 28, 2019 •
edited
Loading

Hi there, I have reached out to the Facebook group as well as searched the history. I have also asked in Gitter to no avail. My nightscout site is in a constant crashing state, the logs all report 'H10'. I am using Heroku. I have been successfully using OpenAps for nearly 2 weeks when it started crashing yesterday. I am running the latest version. So far I have tried:

  1. restarting dynos
  2. redeploying site in an earlier state
  3. making a new app (all of which have also crashed)
  4. changing membership plan in Heroku
  5. checking for latest updates
  6. cleaning up Mongo DB

I am at a loss. I can't seem to figure it out and I can't loop as my rig uses NS data :/

Any help would be greatly appreciated!
@sulkaharo
Copy link
Member

In Heroku, restart the dynos and immediately open the log view and don’t close the view until the error triggers. This should produce a so called stack trace that shows where the error occurs. Then post that log snapshot here.

Alternatively if you have Papertrail installed, you should be able to click on the Heroku add-on to view old logs and scroll back until you see this information.

@Propelld
Copy link
Author

2019-04-29T02:52:38.841084+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2019-04-28T02:52+00:00&find[carbs][$exists]=true" host=nat1d.herokuapp.com request_id=156b2af0-c3b2-48c2-be8a-e8148743d26e fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:52:55.594451+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/treatments.json?find[enteredBy]=/openaps:\/\//&count=1?60e93d8f3a75b7c6b7fdd658cb998867683e9b0f" host=nat1d.herokuapp.com request_id=31e0bc4c-f3f0-404e-930a-9d4e827e63bd fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:53:18.951865+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/api/v1/treatments.json" host=nat1d.herokuapp.com request_id=88cd2796-3317-41c2-851f-2467c6b2ed2a fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:06.865434+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/entries.json?find[date][$gte]=1556420045803&count=1000" host=nat1d.herokuapp.com request_id=b8086e60-48f9-42ad-b833-21780446ab0a fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:12.867213+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/entries.json?find[date][$gte]=1556502851183&count=1000" host=nat1d.herokuapp.com request_id=5735ef73-7c1a-45f8-b182-2bc773d43c35 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:26.751731+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/devicestatus.json?count=100" host=nat1d.herokuapp.com request_id=13946e29-1095-4f34-aed7-fadd3c7cd3cf fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:27.572838+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2019-04-28T02:54+00:00&find[eventType]=Temporary+Target" host=nat1d.herokuapp.com request_id=4e4d7788-1cac-4c55-a476-8cd4c6f4054c fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:39.317609+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/treatments.json?find[created_at][$gte]=2019-04-28T02:54+00:00&find[carbs][$exists]=true" host=nat1d.herokuapp.com request_id=6d1a1d73-8e49-4985-bae1-9bfc2c5e4f11 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:54:55.612609+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/treatments.json?find[enteredBy]=/openaps:\/\//&count=1?60e93d8f3a75b7c6b7fdd658cb998867683e9b0f" host=nat1d.herokuapp.com request_id=af326b79-7ef6-4eec-a9b0-12d53c5823eb fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T02:55:36.389535+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/api/v1/treatments.json" host=nat1d.herokuapp.com request_id=b185ab2d-c94c-4c43-9455-f2b01e9b8281 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T14:27:58.756917+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/appcache/nightscout-mlzvi46h52gpdv75.appcache" host=nat1d.herokuapp.com request_id=ccd021f1-7c2e-40a7-810e-f8d07da71082 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T14:27:59.045366+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/audio/alarm.mp3" host=nat1d.herokuapp.com request_id=7557c946-37a1-49ab-9161-db77f25b94d7 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T14:27:59.270008+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/audio/alarm2.mp3" host=nat1d.herokuapp.com request_id=cc0ab0a8-b4f3-42df-9523-5546b8719a04 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https
2019-04-29T14:27:59.282600+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api/v1/status.json?t=1556548137746" host=nat1d.herokuapp.com request_id=cb441879-f428-42da-a842-d1ac61b466b9 fwd="70.50.37.59" dyno= connect= service= status=503 bytes= protocol=https

@sulkaharo
Copy link
Member

That log has been produced after the crash already happened. Please follow my instructions exactly and restart the Dynos ideally just seconds before viewing the log. You should see a bunch of startup messages from Nightscout, followed by a long message about the application crashing

@Propelld
Copy link
Author

Propelld commented Apr 29, 2019 via email

@Propelld
Copy link
Author

Propelld commented Apr 29, 2019 via email

@Propelld
Copy link
Author

Propelld commented Apr 29, 2019 via email

@unsoluble
Copy link
Contributor

We're getting there... that set of logs is great, includes a bunch of times when you restarted the dynos, so we can see that part. But it doesn't include the app crashing, which is the part we need to diagnose. Can you try again, going from a restart all the way through to when the app has crashed?

@Propelld
Copy link
Author

Propelld commented Apr 29, 2019 via email

@unsoluble
Copy link
Contributor

unsoluble commented Apr 29, 2019 •
edited
Loading

If you'd like to temporarily add me as a collaborator (Heroku dashboard > Access > Add collaborator), I can pop in and take a look at the logs.

@Propelld
Copy link
Author

Propelld commented Apr 29, 2019 via email

@unsoluble
Copy link
Contributor

So one thing that may be complicating things at this point: You can only run one app on a free Heroku account — with two apps running, your free dyno hours will run out, and then neither app will run at all. I suspect that this might have happened here? Can you check your billing page to see if you have any free dyno hours left?

@Propelld
Copy link
Author

Propelld commented Apr 30, 2019 via email

@unsoluble
Copy link
Contributor

Instead of deleting it, put it in “maintenance mode”, from its settings page. That’ll make it inactive, but easily restored. And yeah, keep an eye on the other one for now I guess.

@Propelld
Copy link
Author

Propelld commented Apr 30, 2019 via email

@Propelld
Copy link
Author

Propelld commented Apr 30, 2019 via email

@unsoluble
Copy link
Contributor

This appears to be caused by OpenAPS uploading a null value into a db field. There seem to be a couple esoteric fixes that can be tried on the OpenAPS end (see here), but I've also ticketed this here because we shouldn't be crashing on this.

@Propelld
Copy link
Author

Propelld commented Apr 30, 2019 via email

@dustin-lennon dustin-lennon mentioned this issue Dec 6, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@unsoluble @sulkaharo @TwistaTim @Propelld