Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] PerfSonar 5.1.4 Install Disabling Chronyd

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] PerfSonar 5.1.4 Install Disabling Chronyd


Chronological Thread 
    < Chronological >      < Thread >
  • From: "White, Doug" <>
  • To: "" <>
  • Subject: [perfsonar-user] PerfSonar 5.1.4 Install Disabling Chronyd
  • Date: Mon, 31 Mar 2025 22:43:32 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ipac.caltech.edu; dmarc=pass action=none header.from=ipac.caltech.edu; dkim=pass header.d=ipac.caltech.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=NpTIdYWLqJffbZzKI2gqgQxQDpiFRz2NiOw5Og9JeAw=; b=FZvmsfaqjZaLfT+rUl4GEzgJukAiUW354xkHFhqCorE04ef6llS9T4+ebBh1k84qs9KdVPAtLPQ1NsOJ7/t/14gFluxCZRVJLTeSEbqkqeAMChoSaI3RKZUSuIZS79l7BYiYpUToYyuO5gOoUnMry533JJUHixkfWeh4MopTgM94zai3qeESKAUv58X4UXqrBM5k2C5VHPdWtFbLkdMNzfmIGNUfLsR2Kt+1t8Gpo5Ubz2+6MrOgPD42N20edwrtBOcLtokbZGp7YNX5dta4ZUOXuGIfR7KzIMYCO8CUxuwLqkX8LQMI7c0UO13RgEzneSFNFe3HgHkbj4h2PqMikA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=ldQV3IG67mPFKKyJkG6RzOpDtULJ2asSdzJFI6iF9zKyDLf6RXHZ2o/hZZfLuyxNr+szGHFk4Za5rv7xCWCyEJJjotMcqGS7iQU6tbpkZ/XfYsZRSktt81/w94eXxS4fadXXz6ao8ysNteivjnY3XjrVv9/WdD2NKBbwcBZNdUCzAkXyxiwnC3MUawofilknA/DNOAffTDOYF46tuGNsbZpXg/Sq7D9YH7/rqslCpyR0D7DOIGtKnskvNdGyq0583JucudGucNu0rBysQZHXdgiJOzKLe0BvVvZEP2wf2tdkGEicIL+qFm4ajNzdHTDQytwhcgwZTaEKuydDVpkQeg==
We recently upgraded all of our test nodes to Perfsonar 5.1.4. After discovering that tests between some of the nodes were failing we determined it was due to “time” not being synchronized. Further investigation determined that the PerfSonar Installation process (curl -s https://downloads.perfsonar.net/install | sh -s - toolkit) had disabled chronyd. It was enabled and running prior to the install and afterward it was still running but had been disabled. As a result, chronyd would not reload after the next reboot.

We have a simple work-around in place as we just issue a “systemctl enable chronyd” immediately following the the software installation so this is not an urgent matter. We thought we would call it to your attention however, in case this is something that can be addressed in a future release.

FYI, Doug.

Archive powered by MHonArc 2.6.24.

Top of Page