| 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: Mon, 11 Jan 2021 17:04:39 +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=BIC0wJY5603IYpP/ms4kAOMg77wnmR59fXDTdXA4Bcw=; b=nHKgZ2JjvoAfl2/7IVrzwuMX8RXo/J9oipBVaXPnY5EodFBp3xkl1rzM0UUE/sQoVXGRc/Pa4NgLeXULuMSPr4+8M7lYBxopdfN6H0cGQf2+YHSpruX3gyTK4G8bxRCs9zLAjl1HOIegDKwB3jR+bYPpsOm5MYFtm0Vm9JLHp0DtMFYCwDzACbONYhYBMWdv/h5NEsC7QycE/hgXj9u81TpdKiQlwO1ltyL3ZmxVBKYPUpM7OYbLyK4ml0MPsCY+RrTd8yUHJd8rFw4PGDRAbaL03k6AYOuZ2rQ/YWI2BXfz9pdtmXA6iX9DdOj1MgHdx2DwcniMn4kOr2R2RkfkEA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iGere2BtRIxwSKgPpIsy7vUZWITO05njGSGoHLGp6AKzWJARGEheVCHbciQ25jgBh4Dxc9j8BQZqWXezoOXMWtqEOCMgkL7XAUA3nfa4UifJm+igrW6ixyx7Py/QCkIoljoXSMnCDBl9FSaNTXRbqpmatDiM/bzxMU8wuJHF9nAB7eQP5p4w+cmQFjjmDlosn5MMYBAjrqN5DuNKZqUk9l2B06Y0NtF3yH2zXOeR+tonu8ytX/How3G94nefi5q8eDp8g8Hr1M7GFK7KBo69AK3CDEroQrmPqc8M7zVwu1pyIfctyc6WnepgMeFcO4dsOb6WTG8DvhNj1WYX20mRuw==
- 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=BIC0wJY5603IYpP/ms4kAOMg77wnmR59fXDTdXA4Bcw=; b=G0ffVv5Msxp2pacZ3kipAbVF6ZJLkYrN1RuL8UVWGuDMffRtxAzcp96rEbECEmV3phu/9tglH3f6Iid/BFXxdAQm/xdyiE8DxbvZ6psykbp/9ftUBENwLxaAx9t+N4R5pSp0m6ndSko9MsAff+KBKLfDVdZZaMz4qbwzRnpNLtw=
- Thread-index: AdblQklRsLq5hdxcR76wLIkNuRSNQQCv70mAAAbz5bAABdyYAAABii8w
- Thread-topic: [chrony-users] chronyd.service doesn't have Restart=on-failure?
Please see my other post to Miroslav for more detail.
Normally the local clock would be a reasonable backup, but AWS instances have terrible internal timekeeping. Within a day this box lost >2 hours(!) of time.
--Jamie
Jamie Gruener | Director of IT & Security, Biospatial, Inc. | 919-624-9760 | jamie.gruener@xxxxxxxxxxxxx
-----Original Message-----
From: Bill Unruh <unruh@xxxxxxxxxxxxxx>
Sent: Monday, January 11, 2021 11:18 AM
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.
.....
>
> But I think the lines:
>> Restart=on-failure
>> RestartSec=30s
> Should be added in the [Service] section. If chronyd fails for any reason, given how important time is, I can't think why it wouldn't try to restart..
>
Well, if, due to some bug in chrony or bad configuration, chrony dies, then it is liable to die again and again and again. Having a program do that is not a good idea. Rather the sysadmin needs to fix things. Remember that the local clock is still running, so that time is not a complete disaster.
If you really wanted to you could have a cron job run every minute, and if chrony is not running, then restart it (and send the sysadmin an email saying it had happened).
--
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.