#archlinux32-devops | Logs for 2025-12-14

Back
[00:03:23] <trotz> 2025/12/14 01:02 CRIT archlinux32.org Home Certificate HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to www.archlinux32.org port 443 after 0 ms: Could not connect to server
[00:05:23] <trotz> 2025/12/14 01:04 CRIT buildmaster HTTP connect to address 127.0.0.1 and port 80: Connection refused
[00:06:24] <trotz> 2025/12/14 01:05 CRIT archlinux32.org Home HTTP CRITICAL - Invalid HTTP response received from host on port 80: cURL returned 7 - Failed to connect to www.archlinux32.org port 80 after 1 ms: Could not connect to server
[00:06:24] <trotz> 2025/12/14 01:06 CRIT archlinux32.org Home Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to www.archlinux32.org port 443 after 0 ms: Could not connect to server
[00:08:24] <trotz> 2025/12/14 01:08 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
[00:08:24] <trotz> 2025/12/14 01:07 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
[00:08:24] <trotz> 2025/12/14 01:07 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
[00:09:24] <trotz> 2025/12/14 01:08 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
[00:11:24] <trotz> 2025/12/14 01:10 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
[00:11:24] <trotz> 2025/12/14 01:10 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
[00:11:25] <trotz> 2025/12/14 01:11 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
[00:11:25] <trotz> 2025/12/14 01:10 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
[00:11:25] <trotz> 2025/12/14 01:10 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
[00:11:25] <trotz> 2025/12/14 01:10 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
[00:45:27] <trotz> 2025/12/14 01:44 CRIT buildmaster Git Certificate 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
[08:57:33] -!- titus_livius has joined #archlinux32-devops
[08:57:36] -!- trotz has joined #archlinux32-devops
[08:57:37] <trotz> 2025/12/14 01:05 CRIT archlinux32.org Home HTTP CRITICAL - Invalid HTTP response received from host on port 80: cURL returned 7 - Failed to connect to www.archlinux32.org port 80 after 1 ms: Could not connect to server
[08:57:37] <trotz> 2025/12/14 01:02 CRIT archlinux32.org Home Certificate HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to www.archlinux32.org port 443 after 0 ms: Could not connect to server
[08:57:37] <trotz> 2025/12/14 01:06 CRIT archlinux32.org Home Secure HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to www.archlinux32.org port 443 after 0 ms: Could not connect to server
[08:57:38] <trotz> 2025/12/14 01:10 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
[08:57:38] <trotz> 2025/12/14 01:08 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
[08:57:38] <trotz> 2025/12/14 01:10 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
[08:57:39] <trotz> 2025/12/14 01:08 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
[08:57:39] <trotz> 2025/12/14 01:11 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
[08:57:40] <trotz> 2025/12/14 01:10 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 1 ms: Could not connect to server
[08:57:40] <trotz> 2025/12/14 01:10 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
[08:57:41] <trotz> 2025/12/14 01:10 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
[08:57:41] <trotz> 2025/12/14 01:07 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
[08:57:42] <trotz> 2025/12/14 01:44 CRIT buildmaster Git Certificate 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
[08:57:42] <trotz> 2025/12/14 01:07 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
[08:58:36] <trotz> 2025/12/14 09:58 OK buildmaster Bug Tracker Certificate OK - Certificate 'archlinux32.org' will expire on Tue 20 Jan 2026 09:59:06 AM GMT +0000.
[08:58:36] <trotz> 2025/12/14 09:57 OK buildmaster Git HTTP OK: HTTP/1.1 200 OK - 11601 bytes in 0.857 second response time
[08:58:36] <trotz> 2025/12/14 09:57 OK buildmaster Git Secure HTTP OK: HTTP/1.1 200 OK - 11401 bytes in 0.856 second response time
[08:58:41] -!- buildmaster has joined #archlinux32-devops
[08:59:37] <trotz> 2025/12/14 09:59 OK archlinux32.org Home HTTP OK: HTTP/1.1 200 OK - 25910 bytes in 0.226 second response time
[08:59:37] <trotz> 2025/12/14 09:58 OK buildmaster Buildmaster Certificate OK - Certificate 'archlinux32.org' will expire on Tue 20 Jan 2026 09:59:06 AM GMT +0000.
[09:00:37] <trotz> 2025/12/14 10:00 OK buildmaster Bug Tracker HTTP OK: HTTP/1.1 200 OK - 166729 bytes in 0.104 second response time
[09:00:37] <trotz> 2025/12/14 10:00 OK buildmaster Bug Tracker Secure HTTP OK: HTTP/1.1 200 OK - 166527 bytes in 0.153 second response time
[09:00:37] <trotz> 2025/12/14 10:00 OK buildmaster Forum Certificate OK - Certificate 'archlinux32.org' will expire on Tue 20 Jan 2026 09:59:06 AM GMT +0000.
[09:00:37] <trotz> 2025/12/14 10:00 OK buildmaster Forum Secure HTTP OK: HTTP/1.1 200 OK - 16756 bytes in 0.022 second response time
[09:01:37] <trotz> 2025/12/14 10:01 OK archlinux32.org Home Secure HTTP OK: HTTP/1.1 200 OK - 25910 bytes in 0.210 second response time
[09:01:37] <trotz> 2025/12/14 10:01 OK buildmaster Buildmaster Secure HTTP OK: HTTP/1.1 200 OK - 2963 bytes in 0.016 second response time
[09:01:37] <trotz> 2025/12/14 10:00 OK buildmaster Forum HTTP OK: HTTP/1.1 200 OK - 16956 bytes in 0.034 second response time
[09:03:37] <trotz> 2025/12/14 10:02 OK archlinux32.org Home Certificate OK - Certificate 'archlinux32.org' will expire on Tue 20 Jan 2026 09:59:06 AM GMT +0000.
[09:19:04] -!- girls has quit [Quit: ZNC 1.10.1 - https://znc.in]
[09:19:25] -!- girls has joined #archlinux32-devops
[09:44:38] <trotz> 2025/12/14 10:44 OK buildmaster Git Certificate OK - Certificate 'archlinux32.org' will expire on Tue 20 Jan 2026 09:59:06 AM GMT +0000.
[14:51:05] -!- girls has quit [Quit: ZNC 1.10.1 - https://znc.in]
[14:52:00] -!- girls has joined #archlinux32-devops
[17:29:55] <trotz> 2025/12/14 18:29 WARN buildmaster Current Load LOAD WARNING - total load average: 12.58, 10.48, 6.13
[17:39:55] <trotz> 2025/12/14 18:39 OK buildmaster Current Load LOAD OK - total load average: 2.34, 4.78, 5.63
[18:11:48] <buildmaster> any/archlinux32-keyring is broken (says euronuc): https://archlinux32.org
[18:28:43] <buildmaster> pentium4/python-cffi is broken (says euronuc): https://archlinux32.org
[19:31:03] <buildmaster> pentium4/ffmpeg is broken (says streusel-1): https://archlinux32.org
[19:32:06] <girls> streusel-1 has expired keys, it seems
[19:40:07] <buildmaster> i686/ffmpeg is broken (says streusel-1): https://archlinux32.org