perfsonar-user - [perfsonar-user] pScheduler Cannot Connect to DB
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: "Smith, Cody A." <>
- To: perfsonar-user <>
- Subject: [perfsonar-user] pScheduler Cannot Connect to DB
- Date: Thu, 22 Jun 2017 16:28:10 +0000
- Accept-language: en-US
- Authentication-results: spf=pass (sender IP is 128.146.163.17) smtp.mailfrom=oar.net; internet2.edu; dkim=none (message not signed) header.d=none;internet2.edu; dmarc=bestguesspass action=none header.from=oar.net;
- Ironport-phdr: 9a23:xDqnUBIqAGRs6XA52dmcpTZWNBhigK39O0sv0rFitYgfL/XxwZ3uMQTl6Ol3ixeRBMOAuq0C2rCd4vCocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbQhFgDiwbal2IRmoogncssobipZ+J6gszRfEvmFGcPlMy2NyIlKTkRf85sOu85Nm7i9dpfEv+dNeXKvjZ6g3QqBWAzogM2Au+c3krgLDQheV5nsdSWoZjBxFCBXY4R7gX5fxtiz6tvdh2CSfIMb7Q6w4VSik4qx2ThLjlSUJOCMj8GzPisJ+kr9VoA6vqRJ8wo7bfI6aOeFkfq/BeNMXX3ZNUtpTWiFHH4iyb5EPD+0EPetAoYXzul4OrRqiBQmsHO/k1yFFhnjr0qw6zu8sDRvK0AI9FN8JrHvUq871NKITUeCpzKnF1jLDYOlM2Tvn7ojHbAwhrOiKULltf8TRzkwvGBnEjlWWsYHlOCma1v4Xv2id8eVgSfqji2knqw1ovjig2NsjionTioIS0FDE+iN0y5s2K92gUEN3f8SrHIdNuyyfKod6X94uTmRmuCs11rEKpZu2fCYUx5koxhPSbvmKfoqW7h79TOqdPDN1iXZ/dL6ihBu+61asx+L4W8Wu0VtGtiRFncfPu3wR0hHe78aHR/R980qv3DuC2AHe5f9KLE0xl6fXN4MuzqI1m5cSvknMAjT5lUPrh6GMbEok4PKn6+H/b7XmuJCcM4h0hxnmPKkyncKzHfo0PhETUmad5+iwzbrj8lbnT7lQif02j7XZv4vdJcQGoK62HhVZ0p456xa4EzepzsgXnWUGLFJCfhKLlY/pO0zSIPD8Cve/hFesnC13yPDBO73tGpTNLn7dn7f9Zbtx9VRTxBYuwd1a+p5YF6wNLff9WkL+qNDUEho0MwKqzOvoCdhw04YTVGCRDqOHKK/StEWH5uMrI+mCfo8VvzP9JuA56P7pln85nF4dfbWp3ZYMb3C3BO5mL1+fYXXyntcNCX0KsRYmTOz2lF2CViZeZ26sUKIm6DE7E4WmDYHZSYC3mbCBwTy7EYNMZm1dDlCMEGzod5mfW/sSci6SI8lhkiAaWri7TY8uyw2uuBHgx7V5M+XU535QiZW2zNVv6fbUkxgosCFvAt7Vh3mAVW9vmWUBXXorx61liU171lqZ16Vk2bpVGcEFtN1TVQJvf6XZzvB6T5jZXQ7QNv7PAh7ySdK9BDAtTvo2ysVIZUthTYbxxivf1janVudG34eAA4Y5p/rR
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
|
Hey, all.
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 .
Sigh.
A quick glance at the logs gives us this:
Jun 22 12:21:49 clmbs-ps1 safe_run/runner ERROR Exception: OperationalError: FATAL: password authentication failed for user "pscheduler"#012#012Traceback (most recent call last):#012 File "/usr/lib/python2.6/site-packages/pschedule
r/saferun.py", line 41, in safe_run#012 function()#012 File "/usr/libexec/pscheduler/daemons/runner", line 907, in <lambda>#012 pscheduler.safe_run(lambda: main_program())#012 File "/usr/libexec/pscheduler/daemons/runner", line
719, in main_program#012 db = pscheduler.pg_connection(dsn)#012 File "/usr/lib/python2.6/site-packages/pscheduler/db.py", line 35, in pg_connection#012 pg = psycopg2.connect(dsn)#012 File "/usr/lib64/python2.6/site-packages/psyc
opg2/__init__.py", line 164, in connect#012 conn = _connect(dsn, connection_factory=connection_factory, async=async)#012OperationalError: FATAL: password authentication failed for user “pscheduler"
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?
Thanks in advance!
Best,
Cody Smith
|
- [perfsonar-user] pScheduler Cannot Connect to DB, Smith, Cody A., 06/22/2017
- <Possible follow-up(s)>
- Re: [perfsonar-user] pScheduler Cannot Connect to DB, Mark Feit, 06/22/2017
- Re: [perfsonar-user] pScheduler Cannot Connect to DB, Smith, Cody A., 06/28/2017
Archive powered by MHonArc 2.6.19.