Closed Mikeparmenter11 closed 2 years ago
the situation is: you calibrate in xdrip calibration is passed to aaps(nsclient) aaps upload calibration to NS NS crash
correct?
could you provide logs from aaps from that time?
Thanks for looking, Yes xdrip with OOP2 as data source feeds to AAPS / NS / NSCLIENT. Finger pricks entered in xdrip crash NS and NSCLIENT. I can deliberately crash it later to get more logs but not now as she's at school. It has become rather an issue safety wise as its making it tricky to keep the xdrip / libre calibrated. H
Sent from Yahoo Mail on Android
On Fri, 29 Apr 2022 at 10:06, Milos @.***> wrote:
the sutiation is: you calibrate in xdrip calibration is passed to aaps(nsclient) aaps upload calibration to NS NS crash
correct?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Please find attached logs from straight after the crash. KR Hannah
Sent from Yahoo Mail on Android
On Fri, 29 Apr 2022 at 11:20, Milos @.***> wrote:
could you provide logs from aaps from that time?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
i see no logs
I can confirm. My NS is down after I entered a bloody measurement. I'll see if I can grab some logs.
no logs?
Have not been able to reproduce it up to now.
Apologies for my inexperience, I was reading your messages as emails, replying and attaching the logs to the emails, not realising they weren't getting to you / onto github.
Sent from Yahoo Mail on Android
On Fri, 29 Apr 2022 at 10:06, Milos @.***> wrote:
the sutiation is: you calibrate in xdrip calibration is passed to aaps(nsclient) aaps upload calibration to NS NS crash
correct?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
hopefully i found the reason. you may test dev branch
Hello, first time I've raised an issue.
When BG calibrations are entered in XDrip, it causes NSClient to crash. This makes it very difficult to manage our 8 yr old T1 daughter remotely via NSClient, eg. when she is at school.
Sometimes the situation can be recovered by restarting dyno's in Heroku, but it can take several restarts and perhaps 10 minutes for NSClient to operate correctly.
This problem started after updating to AAPS v3.0.0.1
I have attached a screenshot of our NSClient logs, and Heroku logs.
Our rig set up is as follows:
It would be great if this issue could be resolved. Thank you for all your hard work, I don't know what we would have done without NS AAPS.
NSclient crash after calibration error log.txt