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.
OJS 3.3.0.8
PKP PN Plugin version 2.0.4.2
URL: https://periodicos.ifma.edu.br/actatecnologica
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,
Roger
PKP Team
Plugin PKP PN versĂŁo 2.0.4.2
Hi @rcgillis,
I have a similar problem with OJS 3.3.0.7, 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?
Regards
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.
Thanks,
-Felipe.
I still haven’t been able to resolve it.
The plugin is constantly like this, as shown in the image
Licenses are enabled
I’ve updated the terms of use several times.
[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
https://drive.google.com/file/d/1k_q8tkBJig9NiaxUQT31BHnlAo9LAQAP/view?usp=sharing
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. https://ojs-reitoria.ifma.edu.br/actatecnologica).
Best,
Jonas
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.
Best,
Jonas
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 3.3.0.8
And the new one (AITIAS) a clean installation of 3.3.0.6 (now with 3.3.08) and it shows the error: Unknown LOCKSS state inProgress
https://aitias.uanl.mx
There is nothing relevant in the log file.
Thanks!!
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.
Best,
Jonas
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.
Best,
Jonas
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.
Hi!
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 /config.inc.php) 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:
php tools/runScheduledTasks.php plugins/generic/pln/xml/scheduledTasks.xmlThe 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_rundate back a few days in thescheduled_tasksdatabase table.
Best,
Jonas