You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2019. It is now read-only.
NOTE, winston is async, so logger.warn() followed by process.exit() will cause the process to exit before the log message is emitted. This is why we're not seeing log messages at the moment.
Verified the following in verifier.log:
...etc...
{"level":"warn","message":"code updated. closing 1 connections and shutting down."}
{"level":"info","message":"graceful shutdown complete..."}
{"level":"debug","message":"pre-seeded public key cache with key for diresworb.org"}
{"level":"info","message":"verifier server starting up"}
{"level":"debug","message":"attempting to fetching public key for diresworb.org"}
{"level":"debug","message":"public key for diresworb.org returned from cache"}
...etc...
Verified the following in keysigner.log:
...etc...
{"level":"info","message":"running on http://127.0.0.1:62600"}
{"level":"info","message":"process type is keysigner"}
{"level":"warn","message":"code updated. closing 1 connections and shutting down."}
{"level":"info","message":"graceful shutdown complete..."}
...etc...
Verified the following in browserid.log:
...etc...
{"level":"warn","message":"code updated. closing 1 connections and shutting down."}
{"level":"debug","message":"closing database connection"}
{"level":"info","message":"graceful shutdown complete..."}
{"level":"info","message":"delivering email via SMTP host: smtp.socketlabs.com"}
{"level":"info","message":"authenticating to email host as morgamic"}
{"level":"info","message":"browserid server starting up"}
{"level":"info","message":"running on http://127.0.0.1:62700"}
...etc...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
generally whenever the process goes down, we need clear output in the log so we know why.
The text was updated successfully, but these errors were encountered: