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 15:03:12 -0400
  • Ironport-phdr: 9a23:KYC3GBH72o0qRXBvvVgFyZ1GYnF86YWxBRYc798ds5kLTJ7yoMmwAkXT6L1XgUPTWs2DsrQf2rSQ6PqrADdaqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjSwbLdzIRmsowjdqMYajZZsJ6ov1xDEvmZGd+NKyG1yOFmdhQz85sC+/J5i9yRfpfcs/NNeXKv5Yqo1U6VWACwpPG4p6sLrswLDTRaU6XsHTmoWiBtIDBPb4xz8Q5z8rzH1tut52CmdIM32UbU5Uims4qt3VBPljjoMOjgk+2/Vl8NwlrpWrhK/qRxxwYHafY+bOvlxcazBet0aWXFMUdxNWyxOGo6wcZcDAugHMO1Fr4f9vVwOrR6mCAWiA+3g0CVIhnzr1qM9yesuDQDG3AskH90Qs3TYosj+OaAVX++v1qnIzi/PYfRM1jjh6YjIdRQhru+PXb9rbMrRz0kvGxnbgVqNtIzoJjWY3fkDvWic6upvT+Ovi2g/pg5vuTij3MEshZfVho4N11DE8yV5zJwrKtKlVU53ed+kEJ1Mty6ELYt2RN0tQ312tCog1LIJpIO7cDAWyJQm2RHfcfqHfJaI4x77TOaROzB4hHVreLKngBay8E6gyvHmWsao11ZKqyxImcTPuHAVzxHf9MmKRud880qk1juDyhzf5v1BLE06lqfUMYItz7sumpccrEjOGyr7lUbqgKOOaEkp+/Sk5uXib7jpu5OQK5N4hwTwP6ktgMOzHeE1PhYBUmSG/Omx0b7u8E7/Tb5XlPM5iLPZv4rfJckDpq62HQtV0oE75hmkCzepysgXnXocLFJZYh2HlZLlO0rUIPziEPe/hVSsnC11yP/bI73tGpTNLn7dn7f9Zbtx9U9RxBYywN1a6J9YF60NLO72V0L/t9HXFAM1Pgmqz+voFdlw04YTVGGTDqOBNaPdq16I5uYhI+mWY48VvS7wJf8/6P70jn81g1gTcrO10psWb3C4GuppI0aCbHrxhNcBEX0GsRQjQ+z3kFGCSyJcZ26uX6Ig4TE2EJqmApnZRoCjm7yB2yG7EYdMZmxfF1CMCmnnd5+fVvcIaSKSOdNhkicaWbS7So8h0w2uuxHgy7phMOXU5jMUuYj929do+u2A3S01oHY7JsKRyWySB0V9nW5HDXdi1aZzsGRw0RGF3LQux7QMH9hP5v5TVAorHZPHiep3F4ahdBjGe4LDbV+8QZ2DCDowSdY8wJVGN2N0AdbkqxnI3i2uDrw9irqLQpE47/SPjDDKO89hxiOeh+EahF48T54XOA==

Andy,

 

Be renaming the /etc/pscheduler/limits.conf file, I can do throughput tests now.

 

I am tempted to wipe clean and install CentOS 7, maybe next week.

 

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