perfSONAR User Q&A and Other Discussion

["Pennington, Mike" <>]

Also saw this in the pscheduler.log:

 

Feb 13 10:37:32 perfsonar-hartford journal: runner ERROR    84864837: Failed to post run for result: Database connection pool exhausted. Unable to get connection after 60 attempts.

Feb 13 10:37:32 perfsonar-hartford journal: runner ERROR    84828777: Failed to post run for result: Database connection pool exhausted. Unable to get connection after 60 attempts.

Feb 13 10:37:33 perfsonar-hartford journal: runner ERROR    84949221: Failed to post run for result: Database connection pool exhausted. Unable to get connection after 60 attempts.

Feb 13 10:37:33 perfsonar-hartford journal: runner ERROR    84911283: Failed to post run for result: Database connection pool exhausted. Unable to get connection after 60 attempts.

Feb 13 10:37:35 perfsonar-hartford journal: runner ERROR    84850075: Failed to post run for result: Database connection pool exhausted. Unable to get connection after 60 attempts.

 

 

 

Mike Pennington CEN | Network Engineer Hartford CT | 06105-3702 p 860 622 4566 Member Conference - May 10th 2019 – Register:  https://t.co/laqXY47EZl

 

 

From: Pennington, Mike
Sent: Wednesday, February 13, 2019 10:37 AM
To:
Subject: Perfsonar node showing 100% CPU by scheduler

 

I noticed today our perfsonar-hartford node wasn’t responding to HTTP/HTTPS.  SSH was timing out as well.  I power cycled the box when I came in and was finally able to get in.  But it’s very, very sluggish.  Disk space looks good, but when I checked CPU I’m seeing this:

 

 

Any idea on where to start troubleshooting why scheduler is taking up all the CPU?

 

Thanks

 

Mike Pennington CEN | Network Engineer Hartford CT | 06105-3702 p 860 622 4566 Member Conference - May 10th 2019 – Register:  https://t.co/laqXY47EZl