| 21 Jan 2023 |
 hexa | dumped https://gist.github.com/mweinelt/cb4460149479878316b46c116518c88f | 21:30:39 |
| hexa | so I can restart | 21:30:45 |
| hexa | ah, it already was | 21:31:06 |
| hexa | K900: did you see the error? | 21:33:36 |
| hexa |
(finished: must succeed: curl --data '{"host": "acme.test", "addresses": ["192.168.1.1"]}' http://192.168.1.3:8055/add-a, in 0.24 seconds)
client # curl: (7) Failed to connect to acme.test port 15000 after 88 ms: Couldn't connect to server
client # curl: (7) Failed to connect to acme.test port 15000 after 88 ms: Couldn't connect to server
| 21:42:52 |
| hexa | nah, looks like that completed | 21:47:17 |
| 22 Jan 2023 |
 K900 | It got oomkilled I think | 08:00:24 |
| K900 | So I just restarted it | 08:00:29 |
 m1cr0man | In reply to @hexa:lossy.network
(finished: must succeed: curl --data '{"host": "acme.test", "addresses": ["192.168.1.1"]}' http://192.168.1.3:8055/add-a, in 0.24 seconds)
client # curl: (7) Failed to connect to acme.test port 15000 after 88 ms: Couldn't connect to server
client # curl: (7) Failed to connect to acme.test port 15000 after 88 ms: Couldn't connect to server
Yeah that looks fine | 18:53:19 |
| m1cr0man | I suppose OOMkill could be the culprit actually.. this test starts like 4 vms iirc. Client/dnsserver/webserver/acme server. I don't imagine many other tests have as many VMs | 18:54:50 |
| hexa | maybe allocate more memory for the test | 19:34:30 |
| hexa | * maybe allocate more memory for the test then | 19:34:36 |
