From: UNH-IOL Open Source Team Monitoring <os-team@iol.unh.edu> To: <ci@dpdk.org> Subject: [PROBLEM] https on dpdk-dashboard.iol.unh.edu is CRITICAL! Date: Tue, 07 Dec 2021 18:34:25 +0000 Message-ID: <61afa932.1c69fb81.d4b08.8069SMTPIN_ADDED_MISSING@mx.google.com> (raw) ***** Service Monitoring on aed1b7bcbb73 ***** https on dpdk-dashboard.iol.unh.edu is CRITICAL! Info: CRITICAL - Socket timeout after 10 seconds When: 2021-12-07 18:34:25 +0000 Service: https Host: dpdk-dashboard.iol.unh.edu IPv4: 132.177.123.104 IPv6: 2606:4100:3880:1234::104 http://os-monitor.iol.unh.edu/monitoring/service/show?host=dpdk-dashboard.iol.unh.edu&service=https
next reply other threads:[~2021-12-07 18:34 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-07 18:34 UNH-IOL Open Source Team Monitoring [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-19 8:31 UNH-IOL Open Source Team Monitoring 2022-05-16 16:41 UNH-IOL Open Source Team Monitoring 2022-05-12 8:06 UNH-IOL Open Source Team Monitoring 2022-05-05 12:26 UNH-IOL Open Source Team Monitoring 2022-05-04 14:06 UNH-IOL Open Source Team Monitoring 2022-05-02 0:41 UNH-IOL Open Source Team Monitoring 2022-05-01 5:16 UNH-IOL Open Source Team Monitoring 2022-04-29 21:11 UNH-IOL Open Source Team Monitoring 2022-03-25 15:22 UNH-IOL Open Source Team Monitoring 2022-03-24 15:27 UNH-IOL Open Source Team Monitoring 2022-02-13 2:22 UNH-IOL Open Source Team Monitoring 2022-02-02 23:27 UNH-IOL Open Source Team Monitoring 2022-01-26 17:49 UNH-IOL Open Source Team Monitoring 2022-01-21 13:49 UNH-IOL Open Source Team Monitoring 2022-01-03 19:39 UNH-IOL Open Source Team Monitoring 2021-12-20 10:14 UNH-IOL Open Source Team Monitoring 2021-12-18 7:15 UNH-IOL Open Source Team Monitoring 2021-12-18 5:49 UNH-IOL Open Source Team Monitoring 2021-12-09 7:27 UNH-IOL Open Source Team Monitoring 2021-12-09 4:36 UNH-IOL Open Source Team Monitoring 2021-12-04 8:19 UNH-IOL Open Source Team Monitoring 2021-11-23 2:48 UNH-IOL Open Source Team Monitoring
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=61afa932.1c69fb81.d4b08.8069SMTPIN_ADDED_MISSING@mx.google.com \ --to=os-team@iol.unh.edu \ --cc=ci@dpdk.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK CI discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \ ci@dpdk.org public-inbox-index ci Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.ci AGPL code for this site: git clone https://public-inbox.org/public-inbox.git