Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSONAR Tests During Specific Time Frame (pSConfig)

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSONAR Tests During Specific Time Frame (pSConfig)


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Travis Cook <>, "" <>
  • Subject: Re: [perfsonar-user] perfSONAR Tests During Specific Time Frame (pSConfig)
  • Date: Mon, 29 Nov 2021 19:10:37 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=kmt5OTYtwVokSMtPbHSOd1rnmusyB3C2ngUVrj7KycQ=; b=lyQu0/SxEuSvq8yO4j7+u1uAhBVI+g8WN+pRVl7Or3Nw1MUWtak4b+BITKtXaZCzlddmIIzn+O4aPwVNkCsrSjKNXAP0Kse+OrxQW97sBXZGWqij1BXbu5t8fO7brCyu8TYXNYRR6tBKHGTh2CB2mqXuiebVg0ANqSc+m4PBKlEvEBH/4XQ0rXxRKF709Li8QD0I+4jDch0bxa21OnjdqYcDAzAmkX7Vtto6UcMr8W7LWPNCXYQXQ5dfF5FfMFvLzYk8rwUeETHsgAmjFhvzDP3t5BLL+s7nbI2cgIO5Ygit0wlrmCyYxAFwjJXK/iXmya6YZ2pzc/DqgpJulVH1cA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MKY96Kzs4IDxrA/lIAXc1Kr+PAsQAZC9zud0+BcyXAq/7S1TnuxW8g5Cb+Q4hLif8pMqUANrhlB00hwlHMjPEAALX9Ijgp8XCmBMumzbZcTDa6+v57zcNqjyJl/IV2UItL/gyBaeAdyQSmbWgLqEFfRSq4x4nmhE5qNVnQw9O3ZTJcye+CYsUkuAAWzenBznu3h++QzenX4mC25bQKXYi3+iRFjhBnz3oInM0HdLMf3HAdM23PWHMo67PGAg+KtIwjiZ9t2vOpvnWFiBehc+yoOqHtq5Yu9w8da1TkWvHLUNvwySWTuceVG4dVBbw+3sfChldT44skHCfA5fpxm4NQ==

Travis Cook writes:


Awhile back, our organization installed Cron onto the perfSONAR machines prior
to knowing about the "--repeat-cron" function. While the scheduled testing
issue that caused my initial message has been resolved (using Crontab and
pScheduler to run tests instead of using pSConfig and agents), the "--repeat-
cron" function still doesn't work despite the normal Cron function working
properly.

 

The feature has been in pScheduler since 4.3.0 and it does work.  From the command line, this should run RTTs against the local host at the top of the next three minutes:

 

pscheduler task --repeat-cron '* * * * *' --max-runs 3 rtt --dest 127.0.0.1

 

Support for repeat-cron in pSConfig and PWA got overlooked.  I have tickets open against both to get it added to the 5.0 release.  (I think I may have covered that, but there was much turkey and stuffing between then and now.)

 

Could the installed Cron package have affected the performance of
the "--repeat-cron" function and is causing the internal error?

 

There’s no connection between them.  The scheduler doesn’t actually use cron; it has (separate) code that understands the cron specifications and figures out when the next run should be.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page