-
Notifications
You must be signed in to change notification settings - Fork 60
ActionQueue is not running #7008
Comments
first you need to understand that tine20 only fills the ActionQueue, if you want it to be processed, you have to take care of that for yourself. You need to setup a daemon executing tine20/worker.php easiest solution is not to use the ActionQueue, otherwise, read the resources that are available and get it working yourself |
That is fine - problem is that worker.php run into an issue: Parse error: syntax error, unexpected '.', expecting ')' in /var/www/mail/tine20/Tinebase/ActionQueue/Worker.php on line 36 For me it´s fine to run the action Queue once per hour for example so starting the php out of the crontab. But the worker script is not running... |
line 36 is the default config array, I guess you changed something there. git checkout 2018.02.7 also a brief look at line 36 shows everything is fine. Either the packages don't contain the code that is tagged in git or you broke that yourself. hope this helps |
OK - in which file do i have to do the config? Redis.ini??? |
'configfile' => '/etc/tine20/actionQueue.ini', there? |
The worker itself is now running and logging into the worker.log - here i got the next issue |
reading helps: |
You´re right - i missed to mention that the file is paced there and accessible - authorization is 777 (for testing purposes. I also tried a copy of the file and changed the config win ../ActionQueue/Worker.php. Nothing helps... |
did you look at your php config, safe_mode, anything exec related? |
Have not found anything curious - all other php scripts are running well, i don´t know why opening the file is failing all the time... |
is it possible to run something like "php /var/www/mail/tine20.php" (as the same user that is running the worker process)? |
the service worker.php is running, but not doing anything (just filling the logs like mentioned above). |
that is not an answer to the question, pls answer it (so probably understand it first, then answer) |
Hello paulmhh - in my note 20 days ago i mentioned, that all other scripts are running as expected. The worker.php is also running and stays active but the logs showing me that something is wrong in tine20.php. Calling the same always shows the help file (even --dry e.g. is used): Don´t be so angry with me - i just want to help making things running :-) |
the action queue worker is just working fine (well, actually... but lets keep it simple: it is working, believe me, it is) pschuele questions was: which user is executing the worker.php? Can that user also execute tine20.php? (-i or -h is fine, -d alone is pointless, but that works too, just getting the usage message is all you want to achieve here), pls also note the path to the php binary, maybe its different on your system? again, consider not using the action queue |
In my first tests i used "root" to run the worker.php with the result above. After Upgrade to 2018.02 it is still the same - worker.php is running but in the logfile i see errors above. Using www-data user (user which runns Tine Scripts usually) brings the following error: Fatal error: Uncaught exception 'Zend_Log_Exception' with message '"/var/log/tine20/worker.log" cannot be opened with mode "a"' in /var/www/mail/tine20/vendor/zendframework/zendframework1/library/Zend/Log/Writer/Stream.php:81 |
ls -l /var/log/tine20/worker.log wenn du dir die Fehlermeldungen durchliest, steht da ja alles drin... '"/var/log/tine20/worker.log" cannot be opened with mode "a"' |
wahrscheinlich gehört das file root, weil du es im ersten anlauf als root hast laufen lassen |
This is with reference to #6956
My Installation (2018.02.7) is running well but ActionQueue is not getting processed at all.
It´s switched on in the settings to use REDIS but no Meetingacceptence, etc. is send out by the system.
Can you please help me getting Action Queue running.
An upgrade is currently not possible as im still running on Ubuntu 14.04 and an OS upgrade is not possible yet bit in 10 weeks.
Thanks for your help and best regards
Landei
The text was updated successfully, but these errors were encountered: