Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Idle error after update

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Idle error after update


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Raul Lopes <>, "" <>
  • Subject: Re: [perfsonar-user] Idle error after update
  • Date: Fri, 28 Apr 2023 17:00:00 +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=ISeNW7aAXIGqrwb4VvzDPTB78zIfcc/S5d2qgzoF2wo=; b=aE/X3u/zF9QGor/EbzwGrZqabsZol013EY/1XFgews9/J8meqYlxZjPt/cw/oonX2wdTdzBR4/1P7l5DM1svYYl7wSBp6UOWw8m6vr2IA6itllKK133spLIHdJdsXHT2fkUJ3kmripQdSvmySQUFL2OM+0fdvhjVgcEUIH4lvZdCHGs2D9UiZ0KYmSD1a4o3d/h3LWZCo3igrek57m0jjmKoYuwDiQW3J6h87OAf97qUQTvaPPHCQ+dnFAX1dGF3AcdOmQ4zAq3R6gQGrMIwfZHK4NKSp5/okFRwoM9NC3zsQ+2TgnMiI32xRf89fskqn+Yj8kVWPSWnTTUb932wkA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=M/xjodAx92Ufk1WyrnLelwQTHjcYMFKJmqH8x70V+Ivk++w7B9qcufP1syBKJUsQUKVnkWPFRoYJ+uguJrS45foMcgrtiw3Yn9GGor0oRB2I0SeHZOW9aZmaA9Q01iptGhYkh69FeF9Pjw/+I4sDaDWWSnMEeimPIdvRsFeYynYFdE1DOPCk8Y0GtaC3IBZTMJGG7B/5B30LB4+HrN7H6Ri5KgJGomNQvtKmmwLP/DcGuMlUjRabkbvK1JI/q1hprGJt2BjqxqFfRBn/ugkRMYn0pIkNQucpjMcn/C5/yxvd1XLd1mFM0NnxEJGYKtm4KROXXXtsfa2XYILJnXMSUQ==
  • Msip_labels:

Raul Lopes writes:

 

I posted this 

   Measuring MTU... Unsafe or unknown: MTU along path drops from 9000 to 1500

because the troubleshooting is reporting first Unsafe or Unknow. Then, it reports correctly that the MTU drops from 9000 to 1500.

 

That drop is correct and doesn't cause any problem at all. Both hosts are healthy and transfers between them are fine, but 

the troubleshooting result seems contradictory.  

 

Under the hood of that is a run of tracepath, which can sometimes take a long time to run.  We set 30 seconds as a time limit for that, and the unsafe/unknown message is what gets produced when that is exceeded.  I’ve written another ticket on clarifying that:  https://github.com/perfsonar/pscheduler/issues/1332

 

The part of the Idle test, I posted because I couldn't understand and I was wondering if it could denote a configuration problem.

 

It shouldn’t.  The four services that make up pScheduler are either up and functioning or they aren’t.  Is there anything interesting in /var/log/pscheduler/pscheduler.log?

 

--Mark


Archive powered by MHonArc 2.6.24.

Top of Page