| RE: [chrony-users] chronyd.service doesn't have Restart=on-failure? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] chronyd.service doesn't have Restart=on-failure?
- From: Jamie Gruener <jamie.gruener@xxxxxxxxxxxxx>
- Date: Fri, 15 Jan 2021 13:29:47 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=biospatial.io; dmarc=pass action=none header.from=biospatial.io; dkim=pass header.d=biospatial.io; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c1+/dcPmEuWzdStp1LJrPJ2VFtMOuXslSuE/Zoeg0bk=; b=LECAqa9oMooAPcVSd7Jg4Lku2p2a769uwk/8WJcJXyQ6tmwG63W6d4K6vWN0HXI55hsotfL1pPAP4OFApwZxMvzvTzTb8niRDDDzM7HN2ZEQSWA5SJmiuA1Ke3GtTqGzsnZN4v90MOqYn3JZ/OrVcGkr/r/8MHNkHqWPOqN5SjgkLpBbyUSXaOelRPWZPHi4rIhTHKzbhwsJiEdY8MdKjcaa6+mx1Ui80kSjfSwQttYtgaA8wCjn5ylWpnMCWI3u/c/yvXVqH+xaSpaN3Gm+lPIni8YwNmtULR8Tt/T5ro7RNfrpn1FT6oTVe12zp9upGhOo1CeNpK/t6ezasEkrng==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nZvr61eDkHCJFXx6f7JjX+NjMBniY1jnSeOOOVyJG/RpR4Yr+C356uqo4dWwJ3SbfWKbgLktsnSyBJyakWtuyOk70LkaimV9zWzn0Bn9IG7pvNFPaGU4R16EwHtIjnl/mt1Sq4K0vFK9UsMHRv75WreMRWBEUZEnmCRhDneHf3GEaX8mEeAyF3sNra1HhtbUjYXrI/gbVewbTFJbqTIV3p+EgYSikEpfebyZNwKTgU4aQL67r65ej7Ste0eluOTVzPry96rgWinPVi020/n20+AyqW5zzCO6Gn13U+NmVi0ZjEc9ODhsFyVZlMnnRsW6gc4XTgcZwLwXprXMBbytGw==
- Authentication-results: chrony.tuxfamily.org; dkim=none (message not signed) header.d=none;chrony.tuxfamily.org; dmarc=none action=none header.from=biospatial.io;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=biospatial.io; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c1+/dcPmEuWzdStp1LJrPJ2VFtMOuXslSuE/Zoeg0bk=; b=EvlSX4BqYJsBLfapLsmoGQZXsD66zdWL0kN6/4PEspC+nxcZCbc2Ub1YOyq1mfw4jSrljfc6S440etEePc3YzxBGXFFImN2mpJpJ7RCM9I16Fd0bNEAG8tkq8L7SDr11fVOoPrBFY6jpkdetuPjw+BP4RLCiTzOCR/0v0XDFqFc=
- Thread-index: AdblQklRsLq5hdxcR76wLIkNuRSNQQCv70mAAAbz5bAABHqLAAABxqBgAAGdEoAAl5UCgAApsAQA
- Thread-topic: [chrony-users] chronyd.service doesn't have Restart=on-failure?
That's great, thank you. What release(s) will have this patch?
Thanks,
--jamie
Jamie Gruener | Director of IT & Security, Biospatial, Inc. | 919-624-9760 | jamie.gruener@xxxxxxxxxxxxx
-----Original Message-----
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Sent: Thursday, January 14, 2021 12:35 PM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] chronyd.service doesn't have Restart=on-failure?
CAUTION: This email originated from outside of Biospatial. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On Mon, Jan 11, 2021 at 06:15:07PM +0100, Miroslav Lichvar wrote:
> On Mon, Jan 11, 2021 at 05:01:42PM +0000, Jamie Gruener wrote:
> > I can see is that we were at 88%+ memory usage and mid 50% CPU usage during the period leading up to the failure and immediately afterwards. I do have detailed syslog data, though, and 10 minutes before chronyd died clamav also died due to an error that is related to an out of memory condition. There's some other evidence (consul logs on other boxes) indicating that other instances were having trouble reaching the problem instance. Something was up with the box, obviously.
>
> Ok, that might be a good hint. If the system was running out of
> memory, maybe chronyd was stuck waiting for its pages to load from
> disk and execute.
I have commited a fix to trigger the error only when the rate of dispatched timeouts is higher than 100 per second. That should not happen in the slow execution in low-memory conditions.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.