Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Runs missed

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Runs missed


Chronological Thread 
  • From: Kate Adams <>
  • To: "Garnizov, Ivan (RRZE)" <>
  • Cc:
  • Subject: Re: [perfsonar-user] Runs missed
  • Date: Fri, 12 Oct 2018 10:06:21 -0500
  • Ironport-phdr: 9a23:CIE4NheSJFBJ+sJWyBYW2EdwlGMj4u6mDksu8pMizoh2WeGdxcS9ZR7h7PlgxGXEQZ/co6odzbaO7Oa4ASQp2tWoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7Ovr6GpLIj8Swyuu+54Dfbx9HiTahY75+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYeRWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZTAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v9LlgRgP2hygbNj456GDXhdJ2jKJHuxKquhhzz5fJbI2JKPZye6XQds4YS2VcRMZcTyNOAo2+YIUPAeQPPvtWoZfhqFYVtxSyGROhCfnzxjNUhHL727Ax3eQ7EQHB2QwtB9cAv27IrNrrKawfTf26w7PNzTXYcvhb3jT955LUch8/uvyMUqhwftTLxkkzDwPFik+fqY3jPzOOzOgNtXaU7/Z5WO+plmUppQZxoj21ycctjInEnoEVxUrC9SVj3ok1I8e0SEhlbt64CJdQuTuVN5ZsTsw/XW5lvjsxxL4euZOjYiQHyYgryhzaZvyJcIWH+Q7vWeOeLDp7hX9od7eyiwiu/UWlz+DxVMe53VZMoyFYiNfDrGoN2AbW6sWfSvty4EOh2TGX2gDW8O5EIEQ0mbPCK54i37I8j5USvEbNEyL2gkn2g6iWdkIr+uis9evreKnpppiZN4NsiwH+NLohmtCnDOgmMwUCQ2qW9OGy1LDg5kL1XLBHg/I1n6TYv53XINoXqrK8DgJQ0Isu5RayAy+j0NsCnHkHKFxFeAiAj4jsI1zOI+r3DeuhjFm3nzdr3e7JMaf9ApXVKnjMirbhfbBm60JGzgo808xf64pOCr4dOPLzRlPxtNvAAx8hLQO02ejnCM561oMYQ22PGLaVML7JsVCW/OIiOO2MZI4OuDbhMPgp+eTijX4/mV8BY6apx50XZ26kHvh4OUmWf2fjgspSWVsN60ARRfbsiU+FT3obRmi7Wep83AsJJcPsRdPCWImrxrOIxiG6DJpITm5PFxaAHCG7WZ+DXqIvYT6fauZtmzkfHeyiQpMs/R60uQbm075uL+zPvCsVqcSwh5BO++TPmERqpnRPBMOH3jTIFjkskw==
pscheduler task --debug trace --dest ps-ksu-bw.personar.kanren.net

Results in a run being missed, as returned on the command line.  The log files have this to say:

Oct 12 09:33:46 speedy journal: task DEBUG    Posted https://localhost/pscheduler/tasks/611e97bc-21d9-4508-863d-41a26b16737d
Oct 12 09:33:46 speedy journal: task DEBUG    Submission diagnostics:
Oct 12 09:33:46 speedy journal: task DEBUG      Hints:
Oct 12 09:33:46 speedy journal: task DEBUG        requester: ::1
Oct 12 09:33:46 speedy journal: task DEBUG        server: ::1
Oct 12 09:33:46 speedy journal: task DEBUG      Identified as everybody, local-interfaces
Oct 12 09:33:46 speedy journal: task DEBUG      Classified as default, friendlies
Oct 12 09:33:46 speedy journal: task DEBUG      Application: Hosts we trust to do everything
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Limit 'always' passed
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Want all, 1/1 passed, 0/1 failed: PASS
Oct 12 09:33:46 speedy journal: task DEBUG        Application PASSES
Oct 12 09:33:46 speedy journal: task DEBUG      Application: Defaults applied to non-friendly hosts
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Limit 'innocuous-tests' passed
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Limit 'throughput-default-tcp' failed: Test is not 'throughput'
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Limit 'throughput-default-udp' failed: Test is not 'throughput'
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Limit 'idleex-default' failed: Test is not 'idleex'
Oct 12 09:33:46 speedy journal: task DEBUG        Group 1: Want any, 1/4 passed, 3/4 failed: PASS
Oct 12 09:33:46 speedy journal: task DEBUG        Application PASSES
Oct 12 09:33:46 speedy journal: task DEBUG      Proposal meets limits
Oct 12 09:33:46 speedy journal: task DEBUG    Fetching https://localhost/pscheduler/tasks/611e97bc-21d9-4508-863d-41a26b16737d/runs/first
...skipping...
Oct 12 09:35:46 speedy journal: task DEBUG    Handing off: pscheduler watch --format text/plain --debug https://localhost/pscheduler/tasks/611e97bc-21d9-4508-863d-41a26b16737d
Oct 12 09:35:47 speedy journal: watch DEBUG    Fetching https://localhost/pscheduler/tasks/611e97bc-21d9-4508-863d-41a26b16737d




On Fri, Oct 12, 2018 at 5:46 AM Garnizov, Ivan <> wrote:

Hello Kate,

 

These are 2 different cases on the pscheduler operation.

Failed to schedule means: It did not find a free slot in the schedule on the localhost. Presumably this host is engaged with other tasks as well.

A missed run means it was scheduled, but then there had been a leap of time or something kept busy pscheduler, which led to the moment when the test should have been started is missed.

 

The logs you are looking in for events are incorrect. There is only one place for logs from pscheduler operation: /var/log/pscheduler/pscheduler.log

 

The above explanations about the possible failures in operation of pscheduler though should not apply for trace tasks.

 

Please provide the whole command and related events from the pscheduler log.

 

 

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

Jubiläumsjahr 2018 - IT in Bewegung

Das RRZE - der IT-Dienstleister der FAU

www.50-jahre.rrze.fau.de

 

Von: [mailto:] Im Auftrag von Kate Adams
Gesendet: Donnerstag, 11. Oktober 2018 21:22
An:
Betreff: [perfsonar-user] Runs missed

 

Hello All,

 

In troubleshooting the maddash, I ran a traceroute manually.  The first time, the run failed to schedule.  The second time, it was missed.

 

Task URL:

Running with tool 'traceroute'

Fetching first run...

 

Next scheduled run:

Starts 2018-10-11T10:43:24-05:00 (~0 seconds)

Ends   2018-10-11T10:43:32-05:00 (~0 seconds)

Waiting for result...

Run did not complete: Missed

No further runs scheduled.

 

There was no information in these log files about that run.  Where are the errors/reasons it didn't run logged?  

psconfig-pscheduler-agent-transactions.log

psconfig-pscheduler-agent.log

psconfig-pscheduler-agent-tasks.log

 

--

Kate Adams ()

Cyberinfrastructure Technologist

Great Plains Network



--
Kate Adams ()
Cyberinfrastructure Technologist
Great Plains Network

Archive powered by MHonArc 2.6.19.

Top of Page