---
owner: gmikcon
status: active
last_reviewed: 2026-10-07
review_interval: 90d
confidence: high
source_of_truth: ssh-host-verified
---

# Nextcloud VM

Nextcloud file cloud VM, upstream for `cloud.gnexus.space`.

## Identity

- Inventory id: `nextcloud`.
- VM id: `nextcloud` (libvirt domain on hypervisor `hp-proliant-dl380-g6`, bserv `192.168.1.130`).
- LAN address: `192.168.1.152`.
- Resources: 24 vCPU, 32 GiB RAM.
- Disk: qcow2 `/mnt/main/vm_main/nextcloud`.
- Autostart: enabled. Note: libvirt autostart only fires on host/libvirt start — it does NOT recover a VM killed by the OOM killer.

## Roles

- Nextcloud instance behind `cloud.gnexus.space` (TLS terminates on `internal-proxy-vps`, upstream `http://192.168.1.152`).

## Incident 2026-10-06 (OOM crash)

- 2026-10-06 07:53:20 UTC: global OOM on hypervisor bserv — 117 GiB RAM exhausted and 8 GiB swap full. Kernel OOM killer killed the nextcloud qemu process (pid 3965, ~28 GiB RSS, largest allocation on the host).
- 2026-10-06 07:54:06 UTC: VM shut down, `reason=crashed` (libvirt log).
- Down ~31h12m; `cloud.gnexus.space` returned 502 from the internal proxy during the outage. Started manually by the owner 2026-10-07 15:06 UTC; service verified 200 after start.
- Standing risk: hypervisor memory stays tight (90/117 GiB used, swap 8/8 GiB full at check 2026-10-07); the nextcloud VM is the largest single memory allocation (32 GiB) and the most likely OOM victim again.

No raw credentials are documented here.
