PKP PN Plugin does not work

I cannot succeed in archiving.
The plugin is up to date.
The term was accepted
But 2 weeks ago it displays the following information: Network Status: The PKP PLN can accept deposits from this journal.

PKP PN Plugin version

Hello @lcbrito02,

Can you let us know what version of the plugin you’re using as well? I’ll see about seeing if one of our staff can look at this when they are available, however, in the meantime, if you wanted to have a look at some of the troubleshooting suggestions on the Github page: GitHub - pkp/pln - that might help as well.

Best regards,

PKP Team

Plugin PKP PN versĂŁo

Hi @rcgillis,

I have a similar problem with OJS, PKP PN v2.0.4.2

Network Status: The PKP PLN can accept deposits from this journal.

I have taken all the advice on github into account.
The delivery process has been “in progress” for two weeks and has been stuck ever since.
Is there anything I can do or should I wait a few more weeks?


Did you find a solution? Was it just a matter of waiting? Or did you have to increase the memory limit in php.ini? I’m facing a similar problem, it’s “in progress” for several days.

I still haven’t been able to resolve it.
The plugin is constantly like this, as shown in the image

Captura de Tela 2022-04-08 às 22.52.38

Licenses are enabled

Captura de Tela 2022-04-08 às 22.52.01

Captura de Tela 2022-04-08 às 22.52.08

I’ve updated the terms of use several times.

Captura de Tela 2022-04-08 às 22.52.52

[Issue with PKP PN Plugin - #6 by jnugent](https://Issue with PKP PN Plugin)

I couldn’t solve the error that stops the task as shown in the log

I tried to orient myself through this forum, but still no solution…

Hi @lcbrito02,

I’ll try to investigate what’s happening in your case, I could find some records for your journal in the PKP|PN, but all of them refer to old/invalid URLs (e.g.


Hi @lcbrito02,

I just saw that you’ve attached a log file, and according to the message “Um executável tar deve estar disponível.”, looks like your plugin isn’t installed properly, it’s missing a required package.

In case you couldn’t grab the plugin through the plugin gallery, please ensure the composer packages have been installed.


Hi @jonasraoni
Could you check some of my journals?
I’ll add two to make it faster.
The first one (RESPYN) was a migration from 2.x and stopped doing it with the upgrade to

And the new one (AITIAS) a clean installation of (now with 3.3.08) and it shows the error: Unknown LOCKSS state inProgress
There is nothing relevant in the log file.


Hi @dagosalas!

I found a similar issue here: PKP PN Plugin error Unknown LOCKSS state inProgress eventhough journal issues appear on the list of journal list spreadsheet. I assigned myself to check it and I’ll follow up there in order to keep the focus.


1 Like

The plugin was installed from the gallery itself and so far we know what this error you are referring to was.

I uninstalled the plugin, deleted it and redid the entire installation process, let’s see what happens for a few days.

@lcbrito02 did it work? If yes, I’ll mark this one as closed.


As per your guidance, I uninstalled, deleted and again re-installed the version PKP|PN 2.0.4-2 below, but so far nothing has changed.


Was the error “Um executável tar deve estar disponível.” fixed?

If yes, could you please share your logs (I left an instruction below, if you already know where it is, feel free to skip it)?

The PLN plugin works through a scheduled task, and its activity is logged in the directory ${files_dir}/scheduledTaskLogs (the location of the files_dir is configured in the file / each time it runs. The PLN log file begins with the name PKPPLNDepositorTask and ends with a date stamp. If you don’t have these files, it’s an indication that the plugin may not be running as it should.

In order to extract a helpful error message, it would be great if you could:

  1. Execute the task manually using the command below:
    php tools/runScheduledTasks.php plugins/generic/pln/xml/scheduledTasks.xml

The task is scheduled to run once a day, in case it has already been executed, it won’t execute again in the same day. Then you’ll need to set its last_run date back a few days in the scheduled_tasks database table.

  1. Share the latest log generated for the task (the one which starts with “PKPPLNDepositorTask” and ends with the current date)
  2. Share relevant errors from your server’s error log (the errors which happened in the time frame of the task execution)