| 19 Aug 2021 |
 nix-community-bot | [firing] inodes_full_in_12h: nix-community-build02 device disk/by-uuid/29a6b37b-fafb-46a1-b856-1e1c20dc053b on / is running out of inodes in approx. 12 hours
| 22:43:30 |
| 20 Aug 2021 |
| nix-community-bot | [firing] inodes_full_in_12h: nix-community-build02 device disk/by-uuid/29a6b37b-fafb-46a1-b856-1e1c20dc053b on / is running out of inodes in approx. 12 hours
[firing] systemd_service_failed: nix-community-build02 failed to (re)start service nixpkgs-update-repology.service.
| 01:58:30 |
| nix-community-bot | [resolved] inodes_full_in_12h: nix-community-build02 device disk/by-uuid/29a6b37b-fafb-46a1-b856-1e1c20dc053b on / is running out of inodes in approx. 12 hours
[firing] systemd_service_failed: nix-community-build02 failed to (re)start service nixpkgs-update-repology.service.
| 03:38:30 |
| nix-community-bot | [firing] systemd_service_failed: nix-community-build02 failed to (re)start service nixpkgs-update-repology.service.
| 07:43:30 |
 Mic92 | ryantm: ^ | 08:11:53 |
| nix-community-bot | [firing] systemd_service_failed: nix-community-build02 failed to (re)start service nixpkgs-update-repology.service.
| 11:48:30 |
| nix-community-bot | [resolved] systemd_service_failed: nix-community-build02 failed to (re)start service nixpkgs-update-repology.service.
| 13:58:30 |
| Mic92 | I "solved" it by restaring | 16:19:10 |
 ryantm | Thanks. I guess it is going to keep posting until we restart it. I should look into why it crashed. | 16:41:46 |
| ryantm |
nixpkgs-update: /var/cache/nixpkgs-update/repology/nixpkgs-review/rev-0a6d0e1540834c5848a0416eed7a06da76460291/report.md: openFile: does not exist (No such file or directory)
| 16:42:46 |
| ryantm | It failed to grab the report from nixpkgs-review of the "tcltls 1.7.21 -> 1.7.22" update. | 16:43:59 |
| nix-community-bot | [firing] inodes_full_in_12h: nix-community-build02 device disk/by-uuid/29a6b37b-fafb-46a1-b856-1e1c20dc053b on / is running out of inodes in approx. 12 hours
| 17:06:30 |
| Mic92 | The linear prediction is not quite accurate here. | 18:43:00 |
| Mic92 | I will increase the prediction window | 18:44:28 |
| nix-community-bot | [firing] inodes_full_in_4h: nix-community-build02 device disk/by-uuid/29a6b37b-fafb-46a1-b856-1e1c20dc053b on / is running out of inodes in approx. 4 hours
| 20:04:28 |
| ryantm | So.. is the inode problem because I used f2fs for the filesystem? | 21:08:44 |
| Mic92 | no. I just have not found the best parameters on how to predict a disk getting full. | 21:47:56 |
| Mic92 | I will just remove it... | 22:02:12 |
| Mic92 | it was not very helpful so far | 22:02:19 |
| 21 Aug 2021 |
| nix-community-bot | [firing] systemd_service_failed: nix-community-build02 failed to (re)start service nix-gc.service.
| 03:24:12 |
| nix-community-bot | [firing] systemd_service_failed: nix-community-build02 failed to (re)start service nix-gc.service.
| 07:29:12 |
| nix-community-bot | [resolved] systemd_service_failed: nix-community-build02 failed to (re)start service nix-gc.service.
| 07:54:12 |
| nix-community-bot | [firing] uptime: nix-community-build02 has been up for more than 30 days.
| 08:42:12 |
| Mic92 | I will update & reboot build02 | 09:08:37 |
| nix-community-bot | [resolved] uptime: nix-community-build02 has been up for more than 30 days.
| 09:17:12 |
| nix-community-bot | [firing] telegraf_down: build02.nix-community.org:9273: telegraf telegraf exporter from is down.
| 09:22:12 |
| Mic92 | Rebooting this machine always takes ages. | 09:25:43 |
| Mic92 | I wonder where it hangs. | 09:25:47 |
| Mic92 | I consiert switching to kexec the next time | 09:27:17 |
| Mic92 | *consider | 09:27:23 |
