Open darenwelsh opened 6 years ago
I've had this happen a few times now and every time it happens after I run showJobs.php
to check the remaining amount. It's too few data to say with certainty that this is repeatable, but just an observation at this point.
What are the permissions of /opt/data-meza/cache?
ls -al /opt/data-meza/cache
Does /opt/data-meza/cache/oso exist? (if subsequent runs completed, then I would assume yes)
If so, what are it's current permissions+ownership?
ls -al /opt/data-meza/cache/oso
What groups are you in?
groups
I suspect that the 'oso' directory creation job was actually executed by the web request method, or cron where permissions were not a problem. You running it from the console as yourself probably do not have the right group membership or ownership of those directories to create 'oso'.
You need to sudo
that command. Meza needs to be better about requiring sudo
less...it shouldn't really be necessary in this case, but it is with the current setup.
Renamed the issue, adding to catch-all issue #910
Environment
Issue details
Because the cron job runner on dkms was not working at the time, I was manually executing
runJobs.php
to get through some find/replace jobs. After a few times of this running as expected (running until it ran out of memory and stopped), I encountered this error output. This happened after only one or two jobs ran. After taking this screenshot, I tried to runJobs again and it ran as expected.