In OJS version 3.4.0.4, the processing of access logs is typically handled automatically by the Acron plugin. However, I’ve been experiencing issues where the logs are not being processed as expected. Since the 27th of last month, access logs have been accumulating, but I haven’t been able to find any error messages in the system logs.
For this reason, I would like to manually trigger the processing. Doing so would allow me to monitor the process in real time and hopefully identify what is causing the issue.
Has anyone here successfully executed the access log processing manually? If so, could you share the proper approach — whether it involves configuring scheduledTasks.xml, running a specific CLI command, or another workaround?
Any insights or guidance would be greatly appreciated.
Regards,
Tarcisio Pereira
Hi @Tarcisio_Pereira,
Is the job_runner setting configured in your config.inc.php file? (See config.TEMPLATE.inc.php for an example of that section and related configuration.)
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher
In our production environment, the system is running with the Acron plugin enabled and the configuration set to job_runner = Off. The processing of the access log files is triggered as expected, but the task is consistently interrupted without leaving any clear trace in the logs — or at least none that I have been able to identify.
What I would like to do is manually trigger this processing so that I can monitor it in real time and hopefully capture more detailed output regarding where the interruption occurs.
I have also checked the scheduled task log: it records that the task has started, but there is no further entry that would explain why it stops.
Do you know if there is a way to manually trigger this process, perhaps via CLI or another method, in order to better diagnose the issue?
Regards,
Tarcisio Pereira
You mentioned OJS 3.4.0-4 . There is fix for statistics processing that is available with OJS 3.4.0-9.
Hi @Prooijen ,
this is wrong. We are talking about OJS 3.4 - there is no such directory as lib/pkp/plugins/generic/usageStats/
@Tarcisio_Pereira
I use the following process.
Move the usage_events_{date}.log file from {files}/usageStats/dispatch/. back to {back}/usageStats/usageEventLogs/.
In the database, delete the row that contains class name “APP\tasks\UsageStatsLoader”:
delete from scheduled_tasks where class_name like "APP\tasks\UsageStatsLoader";
Quit the database.
Restart the jobs:
php lib/pkp/tools/jobs.php restart
Restart your supervisor process according to your system setup. See also
https://docs.pkp.sfu.ca/admin-guide/en/deploy-jobs
The job should then start and a new entry will be created in the scheduled_tasks table.
1 Like