Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] pScheduler Cannot Connect to DB

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] pScheduler Cannot Connect to DB


Chronological Thread 
  • From: Mark Feit <>
  • To: "Smith, Cody A." <>, perfsonar-user <>
  • Subject: Re: [perfsonar-user] pScheduler Cannot Connect to DB
  • Date: Thu, 22 Jun 2017 19:29:44 +0000
  • Accept-language: en-US
  • Authentication-results: oar.net; dkim=none (message not signed) header.d=none;oar.net; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:Jqkf3RLj6qhRCZuzuNmcpTZWNBhigK39O0sv0rFitYgfKfjxwZ3uMQTl6Ol3ixeRBMOAuq0C2rCd6vu9EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT6/bL9oKBi6swrdutQYjIZiN6081gbHrnxUdupM2GhmP0iTnxHy5sex+J5s7SFdsO8/+sBDTKv3Yb02QaRXAzo6PW814tbrtQTYQguU+nQcSGQWnQFWDAXD8Rr3Q43+sir+tup6xSmaIcj7Rq06VDi+86tmTgLjhTwZPDAl7m7Yls1wjLpaoB2/oRx/35XUa5yROPZnY6/RYc8WSW9HU81MVSJOH5m8YpMPAeQfIOhYs4fzqVgPrRSiCgahH/ngxiNNhnLswaE2z+YsHAfb1wIgBdIOt3HUoc3yOqgIS+C1z7TDwzXdYPNXxTf29Y/FchUvof6SXLJwbdHcyUgpFwPZkFqQs4rlMC2J1ugTqWSU8fdvVf+2hmMhtgp/oSCvy98yhobTmo4Z11XJ+ThkzIooINC4RkF2bcK4HJZVtSyVKYR7T8AnTmxtpio21rILtYamcCQWy5kr3QDTZv+df4SW7R/uUPydLSpliH54fr+0mgy8/lK6yuLmU8m5yFZKoTRBktnLrn0DzwDe5M+bRvZz50usxy+B2x3K5uFDOk87i7DXK5k8wr4sjZUTtlnDHinrl0nslK+WbEIk+vS25Ov7frXmp5icN4luhgH5L6Quhsi/AeM/MggNRWSU5eO81Lj78U34RrVFkOE2n7HHvJ/AOcgXu6u0DxJI3oo+7hu/ATir3MgEkXQCLl9KZh2KgovsNlzLPvz0Efiyj0ypkDhxxvDGOrPhAo/KLnjGiLrheLh95FBdyAov1t1f5pRUCq0fL/LpXE/+qsDYAgEjPwOq3unnFc1x1pkCVmKXHq+ZLKTSvEeQ5u0xOemMapQVuDH7K/c//f7ilGI5mUQDcqmzxpYXbHG4Hu96I0WCf3bgmNYBEWEWvgUgVuzqjkONUSJNa3qoQa0z+yw7W8qaCtKJfYWsnLzFlAy8EoweTyYMQgSHFmztdpmEc/AFcmSUL9M31nQcWKKvUIgn3AvrqRT30fIzNufO9DYfs5v5kcVu6vf7lBcu+CZyAtjHlWyBUjcnsHkPQmoT1bp86WJwy0vLha12jv1EPd1V+/5TVAomb9jRw/EsWIO6YR7IYtrcEAXued6hGzxkC4tpm9I=
  • Spamdiagnosticoutput: 1:0

Smith, Cody A. writes:

 

Recently, our MaDDash server has ran into a bit of a snag, We’re getting an internal server error ( 500 ) and all signs point to not being able to connect to the pScheduler DB .

…

To me, it seems like the application can’t connect to the DB because the authentication for the scheduler is failing. Any idea how to remedy this, or is this a red herring?

 

The database and the programs that use it are part of the pscheduler-server package, which generates a new random password to be used during the connection process on installation and during upgrades.  If something happens that causes an upgrade to fail mid-stream, it’s possible that the file that stores the password and what the database thinks it should be can get out of sync.  Because of a quirk in the way RPM works, there isn’t a way to cleanly roll the entire system back to its prior state where everything matched.

 

A “yum -y reinstall pscheduler-server” should make things right again and won’t destroy any data.

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page