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

[Crash] Sys_error "/etc/localtime: No such file or directory" #3991

Closed
yourbuddyconner opened this issue Nov 26, 2019 · 0 comments · Fixed by #3992
Closed

[Crash] Sys_error "/etc/localtime: No such file or directory" #3991

yourbuddyconner opened this issue Nov 26, 2019 · 0 comments · Fixed by #3992

Comments

@yourbuddyconner
Copy link
Contributor

Seeing this randomly crashing containerized nodes:

2019-11-26 06:00:03 UTC [Warn] Encountered error while reading stream 94: "read failure: stream reset"
2019-11-26 06:00:03 UTC [Warn] Encountered error while reading stream 140: "read failure: stream reset"
(((pid 1) (thread_id 0)) "2019-11-26 06:00:03.362469745Z"
 "unhandled exception in Async scheduler"
 ("unhandled exception"
  ((monitor.ml.Error (Sys_error "/etc/localtime: No such file or directory")
    ("Raised by primitive operation at file \"stdlib.ml\", line 390, characters 28-54"
     "Called from file \"src/zone.ml\", line 337, characters 21-49"
     "Called from file \"src/core_zone.ml\", line 155, characters 8-75"
     "Called from file \"camlinternalLazy.ml\", line 27, characters 17-27"
     "Re-raised at file \"camlinternalLazy.ml\", line 34, characters 4-11"
     "Called from file \"src/log.ml\" (inlined), line 452, characters 34-55"
     "Called from file \"src/log.ml\", line 470, characters 20-42"
    "Called from file \"src/queue.ml\", line 339, characters 4-22"
 

@yourbuddyconner yourbuddyconner added this to Discuss in Protocol Prioritization via automation Nov 26, 2019
@yourbuddyconner yourbuddyconner changed the title [Crash] [Crash] Sys_error "/etc/localtime: No such file or directory" Nov 26, 2019
@mergify mergify bot closed this as completed in #3992 Dec 2, 2019
Protocol Prioritization automation moved this from Discuss to Done Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant