Skip to Content.
Sympa Menu

perfsonar-user - RE: [perfsonar-user] update to 4.0

Subject: perfSONAR User Q&A and Other Discussion

List archive

RE: [perfsonar-user] update to 4.0


Chronological Thread 
  • From: "Mark Maciolek" <>
  • To: "'Andrew Lake'" <>, <>
  • Cc: <>
  • Subject: RE: [perfsonar-user] update to 4.0
  • Date: Thu, 20 Apr 2017 09:59:13 -0400
  • Ironport-phdr: 9a23:E4DENhS2fV/R0G1BPD6AHWWvX9psv+yvbD5Q0YIujvd0So/mwa6zYxaN2/xhgRfzUJnB7Loc0qyN4v6mAjZLv8nJmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYdFRrlKAV6OPn+FJLMgMSrzeCy/IDYbxlViDanb75/KBS7oR/fu8UIjodvK6Q8wQbVr3VVfOhb2XlmLk+JkRbm4cew8p9j8yBOtP8k6sVNT6b0cbkmQLJBFDgpPHw768PttRnYUAuA/WAcXXkMkhpJGAfK8hf3VYrsvyTgt+p93C6aPdDqTb0xRD+v4btnRAPuhSwaMTMy7WPZhdFqjK9DoByvuRJ/zIzJbo+bN/Rxcb/Sc9QGRWdaRMldSyNBD5uiY4cTDecMO/tToYnnp1sJqBuzHQegCuT1xT9ShX/9wKo03P49HgHH2wwgG8wBsHfaoN7oM6ocVvq6zLPLzTnZaP1Zwyvy6InPchAlv/6MXql9cdfXyUkvDQ/KkEifqZH8Mj6Ty+8DvW+b7+96WuKujW4qsx9+oiO1yscqlIbJmpoZyk3C9SV52oo6O8C3SFNjbd6lFptQqz+VN5FwQsw8X2Fkpjw2xaMbtp6mZCQK1JUnyADFa/yBbYeJ4grvVP6LITd/g3Jldqq/hxGz8Uim1u3wTNW70FFPridDj9LCtWgN2gTN5sWGVvdw/0Ks1DmS2wzP9u1JJE45mKnBJJI9x7M8iJUevVnGEyLzm0j6kLeaelsl9+S06unqZ7rrqoKAO4NojwzzPKcjldajDek9LAQDUHWX9OG52bDg/kD0RqhBgOcsnanDqp/aINwWpq6nDA9R1YYu8w2wDzO839sEnnkHN05Fdwidj4TzIFHOOur0Deq5g1Ssijtk2e3JPqD5DpXMKHjMjqvhcK5j50Nd1AY+zNVS6p1JBr0dPP7+X0H8ud/CARMlNgG43enqBMh4244bWm+DHreVMKbIvl+J4uIvLfOMZIgQuDvlLPYq/eTujXwjlVEaZ6amwZoXaHe8Hvt4IEWUemfsgtEBEWsQoAUxUfHqhEWYUTFPf3ayQ7485jYjBYK+E4jDXI6tgKeG3Ce9BJJWfHlKCk2XEXj2bYWJQPMMaCOJIs99iTwIS6KtS44n1RGyqgD60bxnIfTI+iEGr57sysV65/CA3S01oHY7JsKRyWySB0V9nW5HDXdi1aZzsGRw0RGF3LQux7QMH9hP5v5TVAorHZPHiep3F4ahdBjGe4LDbV+8QZ2DCDowSdY8wJVGN2N0AdbkqxnI3i2uDrw9irqLQpE47/SPjDDKO89hxiOeh+EahF48T54XOA==

Hi,

 

Nothing comes back, just get my prompt again.

 

Mark

 

 

From: [mailto:] On Behalf Of Andrew Lake
Sent: Thursday, April 20, 2017 9:55 AM
To: Maciolek, Mark <>;
Cc:
Subject: RE: [perfsonar-user] update to 4.0

 

Hi Mark,

 

Looks like you database is fine, so a reinstall is not needed. I get JSON back from "https://perf-rcc.unh.edu/pscheduler/tests” which it would not if that were the case. 

 

Could you do a “sudo pscheduler validate-limits” and send us the output?

 

Thanks,

Andy

 

 

On April 20, 2017 at 9:30:03 AM, Maciolek, Mark () wrote:

Hi,

 

Even the auto update of pschedular reports the same error of Failed to load limit file.

 

Apr 20 03:34:50 Updated: pscheduler-server-1.0.0.1-1.el6.noarch

[root@perf-rcc mlm]# tail /var/log/pscheduler/

archiver.out    pscheduler.log  runner.out      scheduler.out   ticker.out

[root@perf-rcc mlm]# tail /var/log/pscheduler/pscheduler.log

Apr 20 03:34:50 perf-rcc runner INFO     Started

Apr 20 03:34:50 perf-rcc archiver INFO     Started

Apr 20 03:34:50 perf-rcc scheduler INFO     Started

Apr 20 03:34:54 perf-rcc runner INFO     Exiting on signal 15

Apr 20 03:34:57 perf-rcc archiver INFO     Exiting on signal 15

Apr 20 03:35:03 perf-rcc runner INFO     Started

Apr 20 03:35:03 perf-rcc archiver INFO     Started

Apr 20 03:35:03 perf-rcc scheduler INFO     Started

Apr 20 03:35:17 perf-rcc pscheduler-api INFO     Started

Apr 20 03:35:17 perf-rcc pscheduler-api CRITICAL Failed to load limit file /etc/pscheduler/limits.conf:

 

Mark

 

--Mark Maciolek

Network Administrator

Morse Hall Rm 338

http://www.unh.edu/research/support-units/research-computing-center

 

From: Brian Tierney [mailto:]
Sent: Wednesday, April 19, 2017 2:22 PM
To: Maciolek, Mark <>
Cc: Andrew Lake <>;
Subject: Re: [perfsonar-user] update to 4.0

 

 

That is odd.

 

Can you try this, and see if that fixes it:

 

yum reinstall pscheduler-server



On Wednesday, April 19, 2017, Maciolek, Mark <> wrote:

Hi,

 

2017/04/19 13:07:38 (9225) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Limit processor is not initialized: Limit processor is not initialized.  See system logs.

2017/04/19 13:07:38 (9225) WARN> perfsonar_meshconfig_agent:430 main:: - Problem adding test, continuing with rest of config: 500 INTERNAL SERVER ERROR: Error while tasking 132.177.100.142: Unable to post task to 132.177.100.142: Unable to complete request: Limit processor is not initialized: Limit processor is not initialized.  See system logs.

 

 

pscheduler-api CRITICAL Failed to load limit file /etc/pscheduler/limits.conf

 

The limits.conf file is there and it’s the same size as the file on my second perfsonar box where the tests are running.

6150 Apr 18 04:40 limits.conf

 

https://perf-rcc.unh.edu/toolkit/

 

Funny thing my other perfsonar box updated yesterday and its tests are working

 

Mark

 

--Mark Maciolek

Network Administrator

Morse Hall Rm 338

http://www.unh.edu/research/support-units/research-computing-center

 

 

Hi,

 

What is in /var/log/pscheduler/pscheduler.log and /var/log/perfsonar/meshconfig-agent.log? Also,does the host have a public address so I can look at the web frontend?

 

Thanks,

Andy

 

 

 

On April 19, 2017 at 11:57:59 AM, Mark Maciolek () wrote:

Hi,

I let the system auto update to version 4 yesterday. I rebooted the server
yesterday. Since the reboot the tests have not run.

This is from the logs:

perf-rcc bwctld[13065]: FILE=sapi.c, LINE=391, BWLControlAccept(): Unable to
read ClientGreeting message

Do I have to remake all the tests?

Mark



--
Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net




Archive powered by MHonArc 2.6.19.

Top of Page