Hubs Cloud Personal Server failed - will not restart #6336
Unanswered
wolobotd
asked this question in
Hubs Cloud Questions
Replies: 1 comment
-
As an FYI - new 1.1.7 install does work. ... and doing a stack update seems to have wiped out whatever broke. For anyone else seeing this error (for the next two months ;-) ) try the stack update. Just worrisome that it broke for no apparent reason in the first place. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This afternoon, the server started giving 502 errors. Would allow access to already logged in accounts to admin and spoke, but could not enter any room. Rebooted, getting same errors, and now NO access to the server at all (offline).
Following errors in system logs related to reticulum:
oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/bio.service,task=beam.smp,pid=13456,uid=1001
Oct 17 19:15:46 nifty-balrog kernel: [7529905.541458] Out of memory: Killed process 13456 (beam.smp) total-vm:5263712kB, anon-rss:3074028kB, file-rss:0kB, shmem-rss:0kB, UID:1001 pgtables:6540kB oom_score_adj:0
reticulum.default@production-1(O): {"Kernel pid terminated",application_controller,"{application_terminated,ret,shutdown}"}
reticulum.default@production-1(O): Kernel pid terminated (application_controller) ({application_terminated,ret,shutdown})
reticulum.default@production-1(O):
reticulum.default@production-1(O): Crash dump is being written to: erl_crash.dump...
bio-launch(SV): Child for service 'reticulum.default@production-1' with PID 7692 exited with code exit status: 1
reticulum.default@production-1(SR): Health checking has been stopped
22:21:09.666 [error] GenServer #PID<0.3433.0> terminating
reticulum.default@production-1(O): ** (BadMapError) expected a map, got: nil
Beta Was this translation helpful? Give feedback.
All reactions