Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonar 4.0 pscheduler archiver does not start behind firewall w/ "pscheduler" does not exist FATAL Error

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonar 4.0 pscheduler archiver does not start behind firewall w/ "pscheduler" does not exist FATAL Error


Chronological Thread 
  • From: Andrew Lake <>
  • To: "John Tai (johntai)" <>, "" <>
  • Subject: Re: [perfsonar-user] perfsonar 4.0 pscheduler archiver does not start behind firewall w/ "pscheduler" does not exist FATAL Error
  • Date: Fri, 21 Apr 2017 05:28:08 -0700
  • Ironport-phdr: 9a23:doFXohbNvPJEUj17p1PmLYn/LSx+4OfEezUN459isYplN5qZr8izbnLW6fgltlLVR4KTs6sC0LuI9fu8EjFZqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjSwbLdzIRmsowjcucYajIt/Jq0s1hbHv3xEdvhMy2h1P1yThRH85smx/J5n7Stdvu8q+tBDX6vnYak2VKRUAzs6PW874s3rrgTDQhCU5nQASGUWkwFHDBbD4RrnQ5r+qCr6tu562CmHIc37SK0/VDq+46t3ThLjlTwKPCAl/m7JlsNwjbpboBO/qBx5347Ue5yeOP5ncq/AYd8WWW9NU8BMXCJDH4y8dZMCAeoDMuZWqIfyqFUAoxijCweyGOzi0SVHimPs0KAgyektDQPL0Qo9FNwOqnTUq9D1Ob8OXOCz0abI1yvMbv1L0jn78ofIcQ4uquyLUL1qd8re1EkuGhjbgVWLs4DlOS2a1vgUvmWd8uFuW+Wvi2s9pAFwpDii3t8shZfThoIb0VDE8iN5z5wvJdGiTk50f8KkHZ1NvC+ZL4t7Wt4uT39rtSogxLAKo5G2cDUQxJkmxBPTc+KLf5SM7x75V+ucIS10iGx7dL+xnRq+7Eytx+n6W8KpylhFtDBFncPJtn0V1xzc9MyHSvxl80evxzmC2Rrf6uVfLkAwj6bbJJkhwqAompoSt0TMADP2lV3rgKOIdUgo4Oal5/7ob7n7vJORNox5hhn7Mqs0m8y/Beo4MhIJX2ie4emzzrvj8lD5QbhRkPI2ibPVsJbEKsQHvqK5GRNa0p4/6xajCDeryMwYkmcdLFJLYxKHiI7pNEvUIPzhEPe/mEqjkC1wyvDCP73hGYnNLmPdnLv7fLZ97VJcxxQpzdBZ+Z1UFq8NLOjtVUDsqdyLRiM+ZkaWxObhQOl018teW2WPBLOQMeKY+QuK4eIpP+CNTIQUoz36bfMi4qiqxTUhlEUTZq6v1IFSdWu1BNxnJVmUe3zhno1HHGsX9EJqVOHwhkaFVzdJImupUrgU5zcnBZigAJuZAI2hnerS8j28G8h/YGxcB0/ENX7res3QUvEAeQqfOYlnnyBSBuvpcJMoyRz77Fyy8LFgNOeBv3RA7Z8=

Hi John,

Try running “yum reinstall pscheduler-server”. A couple others have reported a similar issue and that fixed it. Because of some limitations of what the packages are allowed to do during the ISO install phase there are a few setup things we have to do on first boot. We think what’s happening is they are not completing all the way if networking is not all the way up yet. We are working on building and testing a new ISO that fixes this, but running “yum reinstall pscheduler-server” should get you where you need to be.

Thanks,
Andy



On April 21, 2017 at 12:59:19 AM, John Tai (johntai) () wrote:

Hi Experts!

 

I’m a perfsonar newbie and installed the pS-Toolkit-4.0-CentOS7-FullInstall-x86_64-2017Apr17.iso on an ESXi VM behind a lab firewall and cannot get the pscheduler archiver to run.

 

/var/log/pscheduler/pscheduler.log constantly restarts with the below error “OperationalError: FATAL:  role "pscheduler" does not exist”.  More detail log below.

 

The follow updates to the CentOS7 were done to handle firewall issues:

 

1)      /etc/profile.d/proxy.sh                 !!! set http_proxy/https_proxy to allow “only” http/https traffic on ports 80/443 to go thru firewall

2)      /etc/resolv.conf                                               !!! updated for DNS servers

3)      /etc/sysconfig/network-scripts/ifcfg-eth0  !!! updated for static IP, Gateway

4)      /etc/ntp.conf                                    !!! updated to use a lab NTP server (ntp is correctly working)

 

 

Running the same ISO using a laptop VMware Player VM on a corporate network that does not have a strict firewall policy initially had similar failures, but manually running “systemctl start pscheduler-archiver” restarted the archiver successfully and everything started to work. When a perfsonar VM runs in our lab network behind the stricter FW, the above error always occurs and archiver never starts, even after issue the “systemctl restart  pscheduler-archiver” several times

 

Any help is appreciated!

 

 

Here’s the detailed pscheduler.log with “pscheduler debug on”.

I did follow the Trouble Shooting link without any luck : http://docs.perfsonar.net/troubleshooting_overview.html

 

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/scheduler ERROR    Waiting 30.75 seconds before restarting

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/runner ERROR    Restarting

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/ticker ERROR    Restarting

Apr 20 21:41:39 Perfsonar-Node journal: ticker DEBUG    Debug started

Apr 20 21:41:39 Perfsonar-Node journal: ticker DEBUG    Debug started

Apr 20 21:41:39 Perfsonar-Node journal: ticker DEBUG    QM: Started

Apr 20 21:41:39 Perfsonar-Node journal: ticker DEBUG    QM: Started

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/runner ERROR    Program threw an exception after 0:00:00.007574

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/runner 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/runner", line 909, 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.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 20 21:41:39 Perfsonar-Node journal: safe_run/runner ERROR    Waiting 30.75 seconds before restarting

Apr 20 21:41:39 Perfsonar-Node journal: safe_run/ticker ERROR    Program threw an exception after 0:00:00.011558

 

Regards,

John

 

============

John Tai, Jr.

408-853-9540

 




Archive powered by MHonArc 2.6.19.

Top of Page