Open soccer193 opened 3 years ago
That looks like systemd stopped responding.
Can you give more information about the system this is running on? Hardware? VM Hypervisor type?
Hi SuperQ,
It's a DigitalOcean droplet running Ubuntu 20.04. I've been running my application workload pretty close to the memory capacity of the machine (4GB total), so that may complicate the analysis.
Running sudo journalctl -u systemd*
returned nothing related to the event.
$ systemctl --version
systemd 245 (245.4-4ubuntu3.2)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid
Host operating system: output of
uname -a
node_exporter version: output of
node_exporter --version
node_exporter command line flags
Are you running node_exporter in Docker?
No
What did you do that produced an error?
Left the node_exporter running for four days.
What did you expect to see?
Continued operation, no errors or crashes.
What did you see instead?
Then the system appeared to hang. A jump in the count of go_goroutines was reported by this node_exporter before the hang.
Closer:
The system unhung at 11:41 when the process was reaped by oom-killer.