perfSONAR User Q&A and Other Discussion

[Kathy Benninger <>]

I'm testing CentOS6->7 upgrade with backup and restore of measurement data according to the instructions at:

https://docs.perfsonar.net/install_migrate_centos7.html

I ran into the postgresql 8.4/9.5 error on backup, which resolved with removal of the 8.4 rpms, and the following error when I did the restore:

[root@rumba tmp]# /usr/lib/perfsonar/scripts/ps-migrate-restore.sh --data rumba-ps-backup_30Mar18.tgz
WARN: Looks like non-root user accounts were created prior to running this script. Skipping user account restoration to avoid conflicts
Restoring perfsonar configuration...[SUCCESS]
Restoring bwctl-server configuration...[SUCCESS]
Restoring owamp-server configuration...[SUCCESS]
Restoring NTP configuration...[SUCCESS]
Restoring cassandra data for esmond...[SUCCESS]
Restoring postgresql data for esmond...[SUCCESS]

WARNING

You are about to obliterate the contents of the pScheduler
configuration and database on this host.  Please confirm this by
typing today's date in YYYY-MM-DD format at the prompt below.

Confirm (YYYY-MM-DD): 2018-03-30

Restoring pScheduler from backup:
  Unpacking backup... Done.
  Restoring configuration... Done.
  Restoring database...

Database restore failed:
ERROR:  syntax error at or near "%"
LINE 1: DROP DATABASE IF EXISTS %{_pscheduler_database_name}_save;
                                ^

Restoring prior database... FAILED.ERROR:  syntax error at or near "%"
LINE 1: DROP DATABASE IF EXISTS %{_pscheduler_database_name};
                                ^

WARNING:  Because of errors, pScheduler may be in an inoperable state.
Unable to restore pScheduler configuration

At first there were no "Test Results" displayed on the pSTK home page. After about 30 minutes or so, there are now test results and it looks like the backup/restore worked, but the message "Database restore failed" doesn't leave me with warm-fuzzies about the overall restore. Also, new test results since I took the server down for the upgrade aren't being graphed, though according to pscheduler there are tests scheduled (see below).

Can I rely on the backup/restore in spite of the error message?
Is there something that needs to be done or restarted to get the graphing working for current tests?

Thanks for any advice!
Kathy Benninger
Pittsburgh Supercomputing Center

pscheduler schedule -----------------------------------------------------------------

[benninge@rumba tmp]$ pscheduler schedule
2018-03-30T17:47:08Z - 2018-03-31T17:47:08Z  (Running)
latencybg --data-ports 8760-9960 --dest rumba.psc.edu --packet-padding 0 --flip --source ps.ncsa.xsede.org --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool
  'powstream')
https://localhost/pscheduler/tasks/b507387c-1093-446f-a8cb-af3b7cfab3f8/runs/e3f235e1-08ac-4664-8b4f-b61bafeee47f


2018-03-30T17:47:15Z - 2018-03-31T17:47:15Z  (Running)
latencybg --data-ports 8760-9960 --dest rumba.psc.edu --packet-padding 0 --flip --source ps.psc.xsede.org --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool
  'powstream')
https://localhost/pscheduler/tasks/052cffec-b796-40cb-ac4c-4a93cb3528d8/runs/4e7fa990-b835-4560-8108-d9fb88f04d14


2018-03-30T17:47:15Z - 2018-03-31T17:47:15Z  (On Deck)
latencybg --data-ports 8760-9960 --dest ps.ncsa.xsede.org --packet-padding 0 --source rumba.psc.edu --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool
  'powstream')
https://localhost/pscheduler/tasks/28c0a6d9-d1cb-453a-a5e1-d2a1f9d6c52f/runs/16ee04c3-c68f-4133-93e1-31c1600683c6


2018-03-30T17:47:22Z - 2018-03-31T17:47:22Z  (Running)
latencybg --data-ports 8760-9960 --dest rumba.psc.edu --packet-padding 0 --flip --source ps-test.psc.edu --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool
  'powstream')
https://localhost/pscheduler/tasks/c6169096-494d-46ed-9edd-5b02fd1f8ed9/runs/b5e9d879-2ba9-4c0f-811c-3c7920766028


2018-03-30T17:47:22Z - 2018-03-31T17:47:22Z  (On Deck)
latencybg --data-ports 8760-9960 --dest ps.psc.xsede.org --packet-padding 0 --source rumba.psc.edu --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool
  'powstream')
https://localhost/pscheduler/tasks/1558ec2d-6f9d-4ab2-949c-dfbafb6a5f4c/runs/f0bde1cb-ac5f-41a2-abc8-4210a1d673fc


2018-03-30T17:47:33Z - 2018-03-31T17:47:33Z  (Running)
latencybg --data-ports 8760-9960 --dest ps-test.psc.edu --packet-padding 0 --source rumba.psc.edu --packet-interval 0.1 --duration PT86400S --packet-count 300 (Run with tool 'powstream')
https://localhost/pscheduler/tasks/4bf0a8f6-2bee-40f6-9461-41004447d6e8/runs/a2136c8e-6a5e-4613-9999-4cbae36679a0


2018-03-30T19:09:19Z - 2018-03-30T19:09:35Z  (Running)
rtt --count 10 --dest ps.ncsa.xsede.org --interval PT1S --source rumba.psc.edu --length 1000 (Run with tool 'ping')
https://localhost/pscheduler/tasks/9e212cc5-7d88-4ba2-b19c-8f376adf7016/runs/b18513f8-d37b-4d33-aced-1c172d414d50


2018-03-30T19:09:21Z - 2018-03-30T19:09:29Z  (On Deck)
trace --dest ps.psc.xsede.org --length 40 --source rumba.psc.edu --hops 64 (Run with tool 'traceroute')
https://localhost/pscheduler/tasks/842e2418-899c-4075-85f3-04d8822fb74b/runs/eb881fa3-fcef-482b-bd52-1b315eb2aa63


2018-03-30T19:11:32Z - 2018-03-30T19:12:11Z  (Pending)
throughput --duration PT30S --source rumba.psc.edu --dest ps.ncsa.xsede.org --parallel 1 (Run with tool 'iperf3')
https://localhost/pscheduler/tasks/074a70a4-4a8c-4b56-9916-f66a4cb5cdab/runs/28316e7b-e808-4c2f-9ce4-2b155b051e74


2018-03-30T19:11:51Z - 2018-03-30T19:11:59Z  (Pending)
trace --dest ps-test.psc.edu --length 40 --source rumba.psc.edu --hops 64 (Run with tool 'traceroute')
https://localhost/pscheduler/tasks/e84ff1a6-df53-43e1-aa44-46418f852b14/runs/6f2f1790-f74b-4987-a486-57b5a3a83917


2018-03-30T19:14:01Z - 2018-03-30T19:14:17Z  (Pending)
rtt --count 10 --dest ps-test.psc.edu --interval PT1S --source rumba.psc.edu --length 1000 (Run with tool 'ping')
https://localhost/pscheduler/tasks/8b979f3b-f127-4274-bd4c-166bb6d5a84e/runs/89b7015e-ae8f-4ae8-8337-7e0221add898

etc.................