[01:30] *** ivan has quit IRC (Leaving) [01:31] *** ivan has joined #warrior [01:32] *** Fusl sets mode: +o ivan [07:40] *** h3ndr1k has joined #warrior [09:07] *** drcd has joined #warrior [10:08] *** Dj-Wawa has quit IRC (Quit: Connection closed for inactivity) [13:56] *** second is now known as sec^nd [15:25] *** nyany has joined #warrior [16:18] My warrior seems to have gotten stuck [16:19] It was running the Newsgrabber project quite happily, but it seems to have stalled with 2.3GB Egress and 121.1GB Ingress [16:19] https://usercontent.irccloud-cdn.com/file/nNkZvL9C/image.png [16:19] This is what it looks like when I access the web frontend [16:21] oh nice. it's a disk error. [16:21] never mind. [16:28] *** Dimtree has quit IRC () [16:58] Okay, so new problem. I'm running the Newsgrabber project via warrior-dockerfile. It seems to pull down a bunch of data and then all of a sudden stop responding [16:58] `docker stats` does show that the container is actively doing things, but the frontend won't respond [16:59] There's nothing useful in `docker logs bc6c673842dc` either [17:01] Is it possibly the dedup that's causing the hang? [17:11] what's the last thing in the logs? [17:13] literally "starting warrior" [17:18] anything happening in webui? [17:18] right now yeah, just rsync uploads [17:46] *** Dimtree has joined #warrior [17:59] well that sounds fine then [19:02] *** Dj-Wawa has joined #warrior [19:13] Kaz: should note that after everything finished uploading and started the new download jobs after about 20-30 seconds the front end stopped responding again [19:52] *** Odd0002 has quit IRC (Write error: Broken pipe) [19:54] *** Odd0002 has joined #warrior [20:18] *** t3 has joined #warrior [21:43] *** af10b3e5e has quit IRC (Ping timeout: 615 seconds) [21:47] *** d5f4a3622 has joined #warrior