Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Experience from reinstall to Centos 7/PS 4.0

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Experience from reinstall to Centos 7/PS 4.0


Chronological Thread 
  • From: Sean Crosby <>
  • To: <>
  • Subject: [perfsonar-user] Experience from reinstall to Centos 7/PS 4.0
  • Date: Wed, 19 Apr 2017 17:18:55 +1000
  • Ironport-phdr: 9a23:lzleTRGKXBIAVBbPfdcEM51GYnF86YWxBRYc798ds5kLTJ78rsmwAkXT6L1XgUPTWs2DsrQf2rSQ6fGrADZcqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjSwbLdzIRmsswncssYajZZ8Jqs+1xDEvmZGd+NKyG1yOFmdhQz85sC+/J5i9yRfpfcs/NNeXKv5Yqo1U6VWACwpPG4p6sLrswLDTRaU6XsHTmoWiBtIDBPb4xz8Q5z8rzH1tut52CmdIM32UbU5Uims4qt3VBPljjoMOjgk+2/Vl8NwlrpWrhKvqRJ83oDafoCVO+Zlc6zHYd8XX3BMUtpNWyFDBI63cosBD/AGPeZdt4TzukUBogG4BQKxGu7v0DhIhmTt0qw6zu8sFhrG0xA6H9IJq3Tbt9X0ObwPUeCzzanIyCvMb/dN1jvn9ofHbw0hreuWUrJtaMfcz1QkGQDdjliItIDoPC+Z2v4Qv2WY6+dsT/yjhm09pw1vvjSiyN8gh4vGi44P11zI6yV0zJw2KNGmUkJ2YcOoHZ1NvC+ALYR2WNktQ2RwtSY61LIGvZm7cTAQx5Q63hLfcPmHc5SQ4h76SemePzN4hHN7eL2hnRaz8VGsxvPgWsS6ylpKqytFktzSuX8RzRPT8dSHRuFh8Uem3DaDzwHT6udaLkAojafXNp0szqIqmpYOsknOGjX6lFv1gaOMaEko5ual5/ziYrr8p5+cM4F0ihv5MqQrgsG/Gvg3MhIJX2iA4uu91Kbu/VD/QLVLi/05jK3Zv4vAKcsFu6G5HhVZ3Zw+6xqnFTepzMwYnWUbLFJCYB+Hl5bmO0vAIPDjCve/hU6jkC1yy/DbJb3uHI/NI2PHkLfgZrZ991VcxBQpwdBe4ZJUFq8OIOj1WkDvqNzUEAU1PBKpzOb6W51B0dZKQW+VDLSeNqrI9EKT6/gHIu+QaZUTtSqnbfUp+qi9o2U+nAomcKCvlbANb2uyD7wyOE6DZmHmk/8cF2YPsw40CuHmlRuLTGgAND6JQ6sg62RjW8qdBoDZS9X1jQ==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Hi all,

Today I reinstalled both of my perfSonar boxes to Centos 7/PS 4.0 using the full CD (not netinstall). Everything worked out of the box, except for the creation of the pscheduler user and database.

After install and reboot, I had to do this:

# sudo -u postgres bash
$ createuser pscheduler
$ psql -f /usr/share/pscheduler/database-build-super.sql
$ psql -f /usr/share/pscheduler/database-build.sql

Otherwise I got these errors in the journal

Apr 19 15:03:47 ps-latency journal: safe_run/ticker ERROR    Exception: OperationalError: FATAL:  role "pscheduler" does not exist#012#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/pscheduler/saferun.py", line 41, in safe_run#012    function()#012  File "/usr/libexec/pscheduler/daemons/ticker", line 156, in <lambda>#012    pscheduler.safe_run(lambda: main_program())#012  File "/usr/libexec/pscheduler/daemons/ticker", line 123, in main_program#012    db = pscheduler.pg_connection(dsn)#012  File "/usr/lib/python2.7/site-packages/pscheduler/db.py", line 35, in pg_connection#012    pg = psycopg2.connect(dsn)#012  File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line 164, in connect#012    conn = _connect(dsn, connection_factory=connection_factory, async=async)#012OperationalError: FATAL:  role "pscheduler" does not exist
Apr 19 15:03:47 ps-latency journal: safe_run/ticker ERROR    Waiting 8.25 seconds before restarting
Apr 19 15:03:56 ps-latency journal: safe_run/scheduler ERROR    Restarting
Apr 19 15:03:56 ps-latency journal: safe_run/runner ERROR    Restarting
Apr 19 15:03:56 ps-latency journal: safe_run/scheduler ERROR    Program threw an exception after 0:00:00.003040
Apr 19 15:03:56 ps-latency journal: safe_run/runner ERROR    Program threw an exception after 0:00:00.003030
Apr 19 15:03:56 ps-latency journal: safe_run/scheduler ERROR    Exception: OperationalError: FATAL:  database "pscheduler" does not exist#012#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/pscheduler/saferun.py", line 41, in safe_run#012    function()#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 660, in <lambda>#012    pscheduler.safe_run(lambda: main_program())#012  File "/usr/libexec/pscheduler/daemons/scheduler", line 527, in main_program#012    pg = pscheduler.pg_connection(dsn)#012  File "/usr/lib/python2.7/site-packages/pscheduler/db.py", line 35, in pg_connection#012    pg = psycopg2.connect(dsn)#012  File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line 164, in connect#012    conn = _connect(dsn, connection_factory=connection_factory, async=async)#012OperationalError: FATAL:  database "pscheduler" does not exist
Apr 19 15:03:56 ps-latency journal: safe_run/scheduler ERROR    Waiting 8.5 seconds before restarting

Not sure if it is just the full CD that has this error, and it has been fixed in the netinstall, but it happened on both of my boxes.

Cheers,
Sean

--
Sean Crosby
Research Computing
ARC Centre of Excellence for Particle Physics at the Terascale
School of Physics | University of Melbourne VIC 3010 Australia



Archive powered by MHonArc 2.6.19.

Top of Page