perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Vania Zacarias writes:

We had some perfSONAR nodes with this error:
Error loading test listing; measurement archive unreachable:
http://41.94.225.242/esmond/perfsonar/archive/

…
And we have this pscheduler logs:
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR      File "/usr/
lib/python3.6/site-packages/pscheduler/db.py", line 37, in pg_connection
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR        pg =
psycopg2.connect(dsn)
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR      File "/usr/
lib64/python3.6/site-packages/psycopg2/__init__.py", line 130, in connect
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR        conn =
_connect(dsn, connection_factory=connection_factory, **kwasync)
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR
psycopg2.OperationalError: could not connect to server: No such file or
directory
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR    #011Is the
server running locally and accepting
Mar  4 14:34:39 psmctestp journal: safe_run/archiver ERROR    #011connections
on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Both Esmond and pScheduler depend on PostgreSQL as a backend.  The error you see in the logs means the local socket used for connecting isn’t available.  That’s a sign that the PostgreSQL server is not running or was running and has failed.

--Mark