# Agent v3.67.0 refusing to start because of a new configuration error

**URL:** <https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625>\
**Category:** General\
**Created:** [March 29, 2024, 8:28pm UTC](https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625 "2024-03-29T20:28:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ian-persona](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ian-persona/32/1234_2.png) [@ian-persona](https://forum.buildkite.community/u/ian-persona)\
**Post date:** [March 29, 2024, 8:28pm UTC](https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625/1 "2024-03-29T20:28:19Z")

</div>

Testing Agent v3.67.0 and my instances are failing to start with:

`fatal: cancel-grace-period (5) must be greater than signal-grace-period-seconds (9)`

We set `cancel-grace-period` and always have but have never touched `signal-grace-period-seconds` in the config.

I don’t see any mention of a config-file `signal-grace-period-settings` setting in the documentation. The [command line option doc](https://buildkite.com/docs/agent/v3/cli-bootstrap#signal-grace-period-seconds) says it defaults to 0 if omitted and it _is_ omitted in my case.

Was there a new default of 9 seconds set for this value in v3.67.0? Intentional? Accidental?

I do not have a similar issue with v3.66.0.

---

<div class="post-metadata">

**Author:** ![ian-persona](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ian-persona/32/1234_2.png) [@ian-persona](https://forum.buildkite.community/u/ian-persona)\
**Post date:** [March 29, 2024, 8:48pm UTC](https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625/2 "2024-03-29T20:48:43Z")

</div>

Also: would you prefer these sorts of reports get posted as github issues instead of here in the forum?

---

<div class="post-metadata">

**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\
**Post date:** [March 31, 2024, 12:27am UTC](https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625/3 "2024-03-31T00:27:30Z")

</div>

Hi @ian-persona!

You are correct and we did change the default value of `signal-grace-period-seconds` to 9 seconds; you can read more about this change and why was introduced in [Extend default signal grace period to 9 seconds by triarius · Pull Request #2696 · buildkite/agent · GitHub](https://github.com/buildkite/agent/pull/2696)

You can raise an issue to the github repo to get more info and provide feedback, and the maintainers will get back to you there 🙂

---

<div class="post-metadata">

**Author:** ![ian-persona](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ian-persona/32/1234_2.png) [@ian-persona](https://forum.buildkite.community/u/ian-persona)\
**Post date:** [April 1, 2024, 4:47pm UTC](https://forum.buildkite.community/t/agent-v3-67-0-refusing-to-start-because-of-a-new-configuration-error/3625/4 "2024-04-01T16:47:28Z")

</div>

Thanks @paula – I’ll just revert to the default for `cancel-grace-period`, I think. Our change doesn’t really net us a ton of extra expediency here.