#archlinux32-devops | Logs for 2025-01-04
Back
[09:54:25] <buildmaster> any/ruby-timecop is broken (says eurobuild6-1): https://archlinux32.org
[10:02:55] <buildmaster> any/pacman-mirrorlist is broken (says eurobuild6-1): https://archlinux32.org
[10:11:52] <buildmaster> any/fluidd is broken (says eurobuild6-6): https://archlinux32.org
[10:16:21] <buildmaster> i486/kubernetes are broken (says eurobuild6-7-i486): https://archlinux32.org
[10:19:20] <buildmaster> i486/gitlab-runner is broken (says eurobuild6-8-i486): https://archlinux32.org
[10:23:31] <buildmaster> i486/python-levenshtein is broken (says eurobuild6-7-i486): https://archlinux32.org
[10:31:14] <buildmaster> i486/trivy is broken (says eurobuild6-7-i486): https://archlinux32.org
[10:31:21] <buildmaster> any/hunspell-es are broken (says eurobuild6-6): https://archlinux32.org
[10:31:56] <buildmaster> i486/python-peewee is broken (says eurobuild6-8-i486): https://archlinux32.org
[10:37:46] -!- titus_livius has joined #archlinux32-devops
[10:38:34] -!- trotz has joined #archlinux32-devops
[10:38:35] <trotz> 2024/12/20 10:47 WARN buildmaster OS updates 9 updates, 0 ignored
[10:39:38] -!- buildmaster has joined #archlinux32-devops
[13:15:45] <trotz> 2025/01/04 14:15 CRIT buildmaster Bug Tracker HTTP CRITICAL - Invalid HTTP response received from host on port 80: cURL returned 7 - Failed to connect to bugs.archlinux32.org port 80 after 1 ms: Could not connect to server
[13:15:46] <trotz> 2025/01/04 14:15 CRIT buildmaster Buildmaster Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to buildmaster.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:16:45] <trotz> 2025/01/04 14:16 CRIT buildmaster Forum HTTP CRITICAL - Invalid HTTP response received from host on port 80: cURL returned 7 - Failed to connect to bbs.archlinux32.org port 80 after 0 ms: Could not connect to server
[13:16:46] <trotz> 2025/01/04 14:16 CRIT buildmaster Forum Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to bbs.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:17:46] <trotz> 2025/01/04 14:17 CRIT buildmaster Bug Tracker Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to bugs.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:17:46] <trotz> 2025/01/04 14:16 CRIT buildmaster Forum Certificate HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to bbs.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:17:46] <trotz> 2025/01/04 14:17 CRIT buildmaster HTTP connect to address 127.0.0.1 and port 80: Connection refused
[13:18:46] <trotz> 2025/01/04 14:17 CRIT buildmaster Bug Tracker Certificate HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to bugs.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:23:45] <trotz> 2025/01/04 14:23 CRIT buildmaster Buildmaster Certificate HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to buildmaster.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:23:45] <trotz> 2025/01/04 14:23 CRIT buildmaster Git HTTP CRITICAL - Invalid HTTP response received from host on port 80: cURL returned 7 - Failed to connect to git.archlinux32.org port 80 after 1 ms: Could not connect to server
[13:23:45] <trotz> 2025/01/04 14:23 CRIT buildmaster Git Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to git.archlinux32.org port 443 after 0 ms: Could not connect to server
[13:27:46] <trotz> 2025/01/04 14:27 OK buildmaster Bug Tracker Secure HTTP OK: HTTP/1.1 200 OK - 169409 bytes in 0.077 second response time
[13:27:46] <trotz> 2025/01/04 14:27 OK buildmaster HTTP HTTP OK: HTTP/1.1 200 OK - 665 bytes in 0.001 second response time
[13:28:45] <trotz> 2025/01/04 14:27 OK buildmaster Bug Tracker Certificate OK - Certificate 'alpha.archlinux32.org' will expire on Thu 13 Mar 2025 10:22:17 AM GMT +0000.
[13:33:46] <trotz> 2025/01/04 14:33 OK buildmaster Buildmaster Certificate OK - Certificate 'alpha.archlinux32.org' will expire on Thu 13 Mar 2025 10:22:17 AM GMT +0000.
[13:33:46] <trotz> 2025/01/04 14:33 OK buildmaster Git HTTP OK: HTTP/1.1 200 OK - 11329 bytes in 0.013 second response time
[13:33:46] <trotz> 2025/01/04 14:33 OK buildmaster Git Secure HTTP OK: HTTP/1.1 200 OK - 11101 bytes in 0.011 second response time
[13:35:46] <trotz> 2025/01/04 14:35 OK buildmaster Bug Tracker HTTP OK: HTTP/1.1 200 OK - 169638 bytes in 0.058 second response time
[13:35:46] <trotz> 2025/01/04 14:35 OK buildmaster Buildmaster Secure HTTP OK: HTTP/2 200 - 2893 bytes in 0.182 second response time
[13:36:46] <trotz> 2025/01/04 14:36 OK buildmaster Forum HTTP OK: HTTP/1.1 200 OK - 17002 bytes in 0.023 second response time
[13:36:46] <trotz> 2025/01/04 14:36 OK buildmaster Forum Secure HTTP OK: HTTP/1.1 200 OK - 16774 bytes in 0.018 second response time
[13:37:46] <trotz> 2025/01/04 14:36 OK buildmaster Forum Certificate OK - Certificate 'alpha.archlinux32.org' will expire on Thu 13 Mar 2025 10:22:17 AM GMT +0000.
[17:29:00] <trotz> 2025/01/04 18:28 WARN buildmaster Current Load LOAD WARNING - total load average: 10.61, 7.36, 3.86
[17:34:01] <trotz> 2025/01/04 18:33 OK buildmaster Current Load LOAD OK - total load average: 0.81, 3.31, 3.09
[20:50:53] * buildmaster goes insane.