| Issue Number | 4580 |
|---|---|
| Summary | PDQ Distribution Partner List |
| Created | 2019-02-25 16:46:46 |
| Issue Type | Bug |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-04-28 18:46:08 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.240733 |
Our monthly PDQ partner list is listing at least one of the partners
with an incorrect "Last Access" date.
The partner "University of Bonn" is regularly downloading the PDQ data
but is listed on the report without a "Last Access" date.
The user-ID is ubonngq
The process for creating the PDQ Partner List includes the column for the "Last Accessed" date. This date gets extracted from a file called cumulative.log. The log contains entries for the user ID univbonn. This is the username for the University of Bonn before the switch to the SSH-key access. The user had the user ID changed to ubonngq but there are no entries for this current user ID in the cumulative.log file.
~bkline, do you remember which process is creating this log file which is the basis of the Last Accessed date?
Never mind, ~bkline, I found it.
Our monthly PDQ partner list is listing at least one of the partners with an incorrect "Last Access" date.
After going over the code and inspecting the log files it appears that the statement above is wrong. There are multiple entries each month indicating that Gustav Quade (ubonngq) has a process running which is trying to connect to our SFTP server but there is never a successful connection established, according to the log files. A successful connection would be indicated by the text
session opened for local user
but this entry never appears for ubonngq. When I tried to view the data on the website for this PDQ partner I was unable to find our PDQ information. The University of Bonn redesigned their website and Mr. Quade has retired. It is likely that a process is still running at their site trying to connect to our server and never succeeding.
We should try to contact this PDQ partner to confirm that they aren't updating our data anymore but I don't believe there is anything we can do at our end and since the report is correct there is nothing to change.
FYI: The last successful connection using the old user ID (univbonn) was 2016-09-12.
Elapsed: 0:00:00.001384