-
Notifications
You must be signed in to change notification settings - Fork 49
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
dhermanns/rpi-nightscout:latest keeps restarting #10
Comments
Hi! Looks like you have killed your docker Installation. You should try to
get that up and running again. If you should have problems afterwards, you
could decide to reset your containers by doing a
docker-compose stop
docker-compose rm
docker-compose up -d
But you should keep in mind that you will loose your data by doing so. But
you could be sure that everything will come up as you are used to
afterwards ;-)
Cu,
Dirk
Parallello <notifications@github.com> schrieb am Mi. 26. Dez. 2018 um 19:03:
… *(Hi there. First of all a shoutout to the developer for giving so many
people around the world a chance to have this low-cost solution to an
otherwise complicated problem. Big thumbs up !)*
I have an RPi 3 that has been hosting a nightscout instance for a friend
of mine since last August.
I noticed the webpage was down this afternoon. The
"dhermanns/rpi-nightscout:latest"-container is stuck in a restart loop.
I see this in the logfile:
`Setting up new connection to MongoDB
the server/replset/mongos options are deprecated, all their options are
supported at the top level of the options object
[poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,keepAliveInitialDelay,checkServerIdentity,validateOptions,appname,auth]
GIT HEAD 9f7de63
Successfully established a connected to MongoDB
Mongo Storage system ready
/home/node/app/node_modules/mongodb/lib/mongo_client.js:433
throw err
^
SyntaxError: Error parsing
/home/node/app/node_modules/jsonwebtoken/package.json: Unexpected token �
in JSON at position 1042
at JSON.parse ()
at readPackage (module.js:116:52)
at tryPackage (module.js:126:13)
at Function.Module._findPath (module.js:208:20)
at Function.Module._resolveFilename (module.js:525:25)
at Function.Module._load (module.js:476:23)
at Module.require (module.js:568:17)
at require (internal/module.js:11:18)
at Object. (/home/node/app/lib/authorization/index.js:4:11)
at Module._compile (module.js:624:30)`
I will admit I tried an apt-get update && upgrade right before the
troubles started. This spits out:
The following packages have unmet dependencies: docker-ce-cli : Breaks:
docker-ce (< 5:18.09) but 18.06.1~ce~3-0~raspbian is installed
Thanks for taking the time to look into this !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ADDwlb0EcnbLzvl5XuW97vJf3p_P65EYks5u87nggaJpZM4Zh-CW>
.
|
Right. I see. Is it possible to 'extract' the API-tokens for the different devices that have been allowed access to the website and reuse them on the new installation ? Are they saved in the /var/lib/docker/overlay2/... somewhere ? |
I never tried. Maybe someone else has experience with that?
Parallello <notifications@github.com> schrieb am Sa. 29. Dez. 2018 um 12:56:
… Right. I see.
Is it possible to 'extract' the API-tokens for the different devices that
have been allowed access to the website and reuse them on the new
installation ? Are they saved in the /var/lib/docker/overlay2/... somewhere
?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADDwlbwtPNebRp89qCLYqj9B_Df3hMJTks5u91hTgaJpZM4Zh-CW>
.
|
Hi, is it possible to upgrade nightscout from 10.3 to 13.0.1 using your way? |
Should be
|
Should be? But it is still on 0.10.3.1, when i try to reinstall like in your desciption? |
If you modify the Dockerfile it should wird with later versions, too. If you have a look here: If got it running using nightscout 0.12.4. If I'll find some time, I will update to the latest version... Did you try to use 0.12.4 instead of latest? I will have to link latest to 0.12.4. Looks like it points to an older version right now. |
Tried to update to 0.12.4, what worked for me, but is it possible that there is a forwarding directly to https ? This is not working for me :/ Pulled 0.12.4 but opening then the website didnt work because of https |
No - not from the docker file. All that's done here is: |
(Hi there. First of all a shoutout to the developer for giving so many people around the world a chance to have this low-cost solution to an otherwise complicated problem. Big thumbs up !)
I have an RPi 3 that has been hosting a nightscout instance for a friend of mine since last August.
I noticed the webpage was down this afternoon. The "dhermanns/rpi-nightscout:latest"-container is stuck in a restart loop.
I see this in the logfile:
I will admit I tried an apt-get update && upgrade right before the troubles started. This spits out:
The following packages have unmet dependencies: docker-ce-cli : Breaks: docker-ce (< 5:18.09) but 18.06.1~ce~3-0~raspbian is installed
Thanks for taking the time to look into this !
The text was updated successfully, but these errors were encountered: