Skip to content
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

When a file for document migration doesn't exist, the process fails - it should ignore the record and process the rest #24

Open
mparnelldmp opened this issue Jun 1, 2020 · 1 comment

Comments

@mparnelldmp
Copy link

2020-06-01T21:20:20.111Z Started Getting activityProfile documents from v1
2020-06-01T21:20:20.165Z Started Getting agentProfile documents from v1
2020-06-01T21:20:20.685Z Starting new statements batch of 1000
2020-06-01T21:20:20.942Z Reading file from /mnt/lmsfiles/tmpstor/5956ad4523a9eb2e0cbc3abc/documents/1562612719_677.bin
2020-06-01T21:20:21.181Z Finished migrating documents
2020-06-01T21:20:21.182Z Finished migrating documents
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open '/mnt/lmsfiles/tmpstor/5956ad4523a9eb2e0cbc3abc/documents/1562612719_677.bin'
Emitted 'error' event at:
    at /home/nodeuser/v1-to-v2-migrator/node_modules/fs-extra/node_modules/graceful-fs/graceful-fs.js:190:14
    at /home/nodeuser/v1-to-v2-migrator/node_modules/fs-extra/node_modules/graceful-fs/graceful-fs.js:241:16
    at FSReqWrap.args [as oncomplete] (fs.js:140:20)```
@mparnelldmp
Copy link
Author

...turns out that the script has trouble if any .bin files are missing...and for whatever reason I did have.

I nuked those records and will try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant