perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan" <>]

Hello Phil,

 

It would be great, if you are able to share the output of a run with a failure to archive.

curl –k https://<pscheduler-run-address>

 

I presume there is more clarification in there, than the mere 'false' statement.

 

You could also start some diagnostics for the pscheduler-archiver by running: pscheduler debug on archiver

and seek for the extended logging in /var/log/pscheduler/pscheduler.log

 

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

 

 

-----Ursprüngliche Nachricht-----
Von: [mailto:] Im Auftrag von Phil Reese
Gesendet: Mittwoch, 23. Oktober 2019 21:01
An:
Betreff: Re: [perfsonar-user] Modest sized grid has agent failure to archive once or twice a day

 

Hi,

 

I'm still having this annoying problem.  Any thoughts or suggestions for log files to look into?

 

Hosts seem to run for about 2 days and then fail with this error, corrected by restarting pscheduler-archiver.  (though sometime more often then 2 days)  With 17 agents, this error happens at least once a day.

 

I guess the good news is that the data seems to remain intact on the MaDDash page, once the agent's pscheduler-archiver is restarted.

 

Thanks,

Phil

 

 

 

On 10/18/19 11:28 AM, Phil Reese wrote:

> The problem is that at seemingly random times a host will stop

> reporting data to the MaDDash esmond database, from all tests. This

> shows as an orange line of boxes on each of the MaDDash grids.

> 

> The guaranteed fix is to log into the host and 'systemctl restart

> pscheduler-archiver', this has ALWAYS solved the problem.

>