-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jobs silently fail #6
Comments
I don't know if this is your problem with the zip file being empty, but there is a function mcl_check_setup() in sites/all/modules/mcl/mcl.module that should check that the zip extension is loaded, but as written it does nothing. I had to do this to install the missing zip extension: And for me the logs are saved to |
ah, right. The files, csv, and logs folder in that directory all empty. I think i have permissions set ok? ( i just did chmod -R 777 for the mcl user under files/mcl...) attemping to re-upload the file and rerun gives me this error:
same errors attempting to create a new job and upload. I think that it fails to put the file where it wants it. Manually moving the file there doesnt help... |
I have these notes from when I was first debugging, I don't know if this is much different from what you are trying, but maybe you can try the same and re-run at the command line and see more information?: Use this command to re-run a job so that I can see the output and error messages
And I also had this later note: Fix this stupid stupid line 325 in |
Hi @dsenalik , sorry I missed your response and spaced. Running the job manually via drush does succeed (see below). Confirmed via SQL. Thank you!
|
So to summarize this issue: running However, rerunning the job via |
Hello,
I'm attempting to use your loader. I have created a simple db upload job from the db template file:
I create a job using the UI and run it using
drush mcl-run
. It runs with no feedback:The job status page is updated to failed (see below).
Downloading the log file returns a zip file that is 0 bytes and cannot be unzipped:
to be clear: the db was not loaded:
Any thoughts on how to proceed?
Thank you
Bradford
The text was updated successfully, but these errors were encountered: