PKP-PLN plugin - deposit status

Was hoping someone would be able to provide some assistance with the PKP PLN plugin i’m using on a 2.4.8 journal.

I activated the PKP-PLN plugin at the end of last week (1st July). We have one issue published for our sole publication. Upon activating the plugin, the status showed as Local Status: transferred, Processing status: Sent to LOCKSS, LOCKSS Status: Unknown, Complete: No.

After a week, the status is still showing the same:

As you can see the check column is showing today’s date.

Does anyone know when I might expect the process to finish?

Many thanks

Hello @ah226

That sounds normal. We only recently got all of the LOCKSS Boxes on to our PLN, so it’s taken a while for all the content to synchronize.

If you send me the name or URL of the journal I can double check for you.

Hi - I’m posting this as a reply as I also have a query about status, which is currently showing ‘Unknown’ for ‘Local Status’ and ‘Processing Status’, but ‘Yes’ for ‘Complete’

Does mean the archiving has been completed?
Our journal is
Theron Schmidt, Editor

Hello @PerfPhil

Neither of your two deposits have been harvested. Your server responds to our systems with an HTTP 404 (Not Found), so we cannot download the files. What’s interesting to me is the error message that’s produced: Fatal error: Call to undefined function mime_content_type() in on line 66

Here’s an example, so you can see it in action:

Can you tell me a little more about your setup? mime_content_type() is a pretty standard function for PHP, so I’m a little surprised that it’s missing.

Thanks for the follow-up - very helpful. We’re on a shared host. I added extension=“” to my php.ini and the link now works. I reset the deposits and they are currently processing - would you be able to let me know if the harvest works?

The harvest still isn’t working. It’s strange really. The link works when I open it in a browser, but not when I try to access from the command line.

$ curl -I
HTTP/1.1 404 Not Found

Although, if I change the user agent string to one used by Google Chrome, it works.

$ curl -I -A “Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36”
HTTP/1.1 200 OK
Content-Length: 14873125

So it looks like your server is blocking some web browsers and user agents it doesn’t know about or that don’t have user agent strings.

Our system downloads content with the user agent string “PkpPlnBot 1.0;” so for us to download your content, you’ll need to whitelist it somehow.

Or at least it should have been doing that. It turns out that our system wasn’t reporting the user agent string to OJS correctly. That’s fixed and now your content is getting harvested!

Thanks for following up with this!

Hi @mjoyce,

Thanks for looking further. As an independent journal, we’re so grateful to PKP for this platform and the service, as it allows us to be independent of traditional publishers and universities.

But looks like it’s still not quite there… some of the statuses changed, but the Processing Status has been on ‘Validated’ for a while and the LOCKSS status has not updated:

Would you be able to have a look or let me know if there’s something I should do?

Hi @PerfPhil

It can take a few days for deposits to complete processing and report back success. I checked on your deposits, and our LOCKSS network has reached agreement on them. Your status page will probably update in the next 24 hours to show it.


Thank you, @mjoyce - the status has indeed now updated: LOCKSS Agreement is now ‘Agreement’ and Complete is ‘Yes’. Thanks again for your time and your support.

Hello, @mjoyce

I have next message in scheduledTaskLog today:
[2017-09-07 13:58:13] [Notice] Task process started.
[2017-09-07 13:58:13] [Notice] Depositor processing for Journal of Biomedical Photonics & Engineering.
[2017-09-07 13:58:13] [Notice] Getting service document.
[2017-09-07 13:58:14] [Notice] Processing deposit status updates.
[2017-09-07 13:58:16] [Notice] Deposit 12 has unknown processing state status-error
[2017-09-07 13:58:16] [Notice] Deposit 12 has unknown LOCKSS state status-error
—///deposits 13-21//—
[2017-09-07 13:58:22] [Notice] Deposit 22 has unknown processing state status-error
[2017-09-07 13:58:22] [Notice] Deposit 22 has unknown LOCKSS state status-error
[2017-09-07 13:58:22] [Notice] Processing updated content.
[2017-09-07 13:58:22] [Notice] Processing new content.
[2017-09-07 13:58:22] [Notice] Packaging content for deposit.
[2017-09-07 13:58:22] [Notice] Sending deposits to the PLN.
[2017-09-07 13:58:22] [Notice] Task process stopped.

And Processing status survived as “Validate”.
Why this could happen?

In some cases 10 days or more is reasonable.

Our private LOCKSS network has been made aware of your deposit files and should have them synchronized soon.

Thanks, we will wait. Also we have error with usageStats, how can it danger?

…ojs2 has produced an error\n Message: WARNING: in_array() expects parameter 2 to be array, null given\n In file: /www/home/jbpe/htdocs/plugins/generic/usageStats/\n At line: 190\n Stacktrace: \n File: (unknown) line (unknown)\n Function: PKPApplication->errorHandler(2, “in_array() expects parameter 2 to be array, null given”…

I don’t know anything about the usageStats plugin. It would make sense to start a new thread for that.

Your deposits have been processed and preserved in our PLN.


We have the same problem as above for our journal REMVT
our LOCKSS plugin has been activated a few month ago but I still have a "unknown status everywhere.
We have a lot of data to transfer (4 issues/year since 1947)
How can I solve this ?

Thank you


Hello @denisbastia. Your journal has made about 250 deposits, which our systems are not able to download. The download URLs are responding with HTTP errors.

Often when we see this it is because the server doesn’t have the PHP fileinfo extension installed. There’s no way to be sure though, without looking at the server error logs.

Hello @mjoyce .

I’m working with @denisbastia.

We have enbable the PHP fileinfo extension on our serveur but we still have the same problem.
Here you can find some interresing log on our server

grep “PKP using urllib2” access_log - - [06/Mar/2018:12:31:10 +0100] “GET /index/oai?verb=Identify HTTP/1.1” 200 15474 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:11 +0100] “GET /index.php/index/oai?verb=Identify HTTP/1.1” 200 1923 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:17 +0100] “GET /index.php/index/oai?verb=identify HTTP/1.1” 200 517 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:17 +0100] “GET /ojs/index/oai?verb=Identify HTTP/1.1” 404 211 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:18 +0100] “GET /ojs/index.php/index/oai?verb=Identify HTTP/1.1” 404 221 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:18 +0100] “GET /ojs?page=oai&verb=Identify HTTP/1.1” 404 201 “-” “PKP using urllib2” - - [06/Mar/2018:12:31:18 +0100] “GET /ojs/index.php?page=oai&verb=Identify HTTP/1.1” 404 211 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:34 +0100] “GET /index/oai?verb=Identify HTTP/1.1” 200 15474 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:35 +0100] “GET /index.php/index/oai?verb=Identify HTTP/1.1” 200 1923 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:41 +0100] “GET /index.php/index/oai?verb=identify HTTP/1.1” 200 517 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:42 +0100] “GET /ojs/index/oai?verb=Identify HTTP/1.1” 404 211 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:42 +0100] “GET /ojs/index.php/index/oai?verb=Identify HTTP/1.1” 404 221 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:42 +0100] “GET /ojs?page=oai&verb=Identify HTTP/1.1” 404 201 “-” “PKP using urllib2” - - [13/Mar/2018:11:17:43 +0100] “GET /ojs/index.php?page=oai&verb=Identify HTTP/1.1” 404 211 “-” “PKP using urllib2”

Do you have any idea of what is going on ?
As you can see in the log is reponding.
But we can observe that
grep PkpPlnBot access_log - - [05/Mar/2018:09:00:09 +0100] “HEAD /index.php/REMVT/pln/deposits/D35231F8-545F-412A-9568-D9D464A823CF HTTP/1.1” 500 - “-” “PkpPlnBot 1.0;

Is giving an error 500 .
I havce the same problem if i do curl -l
which give in the log - - [13/Mar/2018:17:33:47 +0100] “GET /index.php/REMVT/pln/deposits/D35231F8-545F-412A-9568-D9D464A823CF HTTP/1.1” 500 - “-” “curl/7.29.0”
Thank you for your help.
Best regards Thomas

Hello @tdolley.

Those log entries are for the PKP indexer, and are unrelated to the LOCKSS preservation system that we use. There should be some entries related to this URL:

Thank you @mjoyce

So to summarize the problem
grep PkpPlnBot access_log - - [05/Mar/2018:09:00:09 +0100] “HEAD /index.php/REMVT/pln/deposits/D35231F8-545F-412A-9568-D9D464A823CF HTTP/1.1” 500 - “-” “PkpPlnBot 1.0;

Our server is issuing an error 500 and we have to understand why.
I will increase server log to understand the problem and i will get you back in a few days

Best regards

That’s the access_log entry. Do you also have the error_log entry for that request? It should have a bit more detail.