perfsonar-user - [perfsonar-user] pScheduler ping localhost failed

Subject: perfSONAR User Q&A and Other Discussion

List archive

From: Tao Zhang <>
To: "" <>
Subject: [perfsonar-user] pScheduler ping localhost failed
Date: Mon, 26 Mar 2018 13:25:36 +0000
Accept-language: en-CA, en-US
Ironport-phdr: 9a23:39kO2R38lvaVO3vtsmDT+DRfVm0co7zxezQtwd8Zse0QIvad9pjvdHbS+e9qxAeQG9mDsLQc06L/iOPJYSQ4+5GPsXQPItRndiQuroEopTEmG9OPEkbhLfTnPGQQFcVGU0J5rTngaRAGUMnxaEfPrXKs8DUcBgvwNRZvJuTyB4Xek9m72/q99pHPbQhEniaxba9vJxiqsAvdsdUbj5F/Iagr0BvJpXVIe+VSxWx2IF+Yggjx6MSt8pN96ipco/0u+dJOXqX8ZKQ4UKdXDC86PGAv5c3krgfMQA2S7XYBSGoWkx5IAw/Y7BHmW5r6ryX3uvZh1CScIMb7S60/Vza/4KdxUBLmiDkJOSMl8G/ZicJwjb5Urx26qhNl34LUZZuYOOZicq7fe94RWGpPXtxWVyxEGo6ycZEAD+0cNulbr4nyvV0OrRSjDgSrGu3g0DhIimX10q06yeshFw7G0Rc8EN0UtnTbts/1NKYMXuyv0KbH1yzOYvVL0jn+8IjFag4tre2MUL5qbMbcyk0iGxnLg1ies4DpIjGY2vwQv2SH9eZsSOGihmo9pwx/vDSj3Mchh4nPi4kI0F7L7z95z5wwJdCgSE50f9qkEJxIui6GLYR2RMYiTHtpuCY+0LEJpYS0fC4Qx5Q9xh7QdeaLfJSS7R77VeaRJyl3hG59db6hmxq/8VKsxvD/W8SwylpHoCRInsPRun0PzxDT79KISvp5/kevwzaP0AXT5/laL08ukqrXMZ0uwr4qmZoVvkTOBTP5l1/wjKCMbEUk+/an5/77bbr8vpOcLZN7ihniMqQyncyyGfw4PRYUX2iV4uS807vj8lfjQLlTk/02ibfWsIrBKMQfp665GBNV0p095xqlDjem1sgYkmcdLFJDZh2Hk5blN0vQL//lEPfsy2irxX1zyurIJbrnC4+IM2POip/ge6pw8UhR1FB1wNxCrdoAErwbLun0XEbr8cHDAwURMgqozvzhBcknkI4SRDTcLLWeNfbuuFjA1OImJebEMLMcv3DPK/Ej6NblhHkwg14QO6Kgi8hEIEukF+hrdh3KKUHnhc0MRD8H

Hello Group,

We have a perfSONAR node: 198.165.161.174. We cannot do any test with this node.

I run pscheduler ping localhost on the host and I got “localhost: Request timed out”.

I checked today’s pscheduler.log file, only two lines showed up in the file:

Mar 25 06:27:46 pS-mun-stj journal: pscheduler-api INFO Started

Mar 25 06:27:47 pS-mun-stj journal: pscheduler-api INFO Limits loaded from /etc/pscheduler/limits.conf

I checked and restarted the four pscheduler services on the node, they are all up and running.

pscheduler-archiver

pscheduler-runner

pscheduler-scheduler

pscheduler-ticker

Could it be related to DNS? This node doesn’t have reverse records in our DNS server at this moment.

Any suggestions?

Tao

[perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
- Re: [perfsonar-user] pScheduler ping localhost failed, David Szydloski, 03/26/2018
  - Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
    - Re: [perfsonar-user] pScheduler ping localhost failed, Szymon Trocha, 03/26/2018
    - Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/26/2018
      - Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
        
        Re: [perfsonar-user] pScheduler ping localhost failed, Michael Johnson, 03/26/2018
        
        Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/26/2018
        
        Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/26/2018
        
        Re: [perfsonar-user] pScheduler ping localhost failed, Tao Zhang, 03/28/2018
        
        Re: [perfsonar-user] pScheduler ping localhost failed, Mark Feit, 03/28/2018