Attempting to bulk import blew up Cheerverto

[SubnetMask]

I was attempting to import 684 images ranging from about 7MB to 10MB in size into a new album via the web UI, and that conked out at around 10% every time. I attempted importing in batches but something seemed off, so I deleted the album and looked into bulk importing... I created a user directory in /var/www/importing/parse-users for my username, and a folder inside that for the album, uploaded all of the files into that folder using filezilla, then via ssh ran 'sudo -u www-data php /var/www/html/app/bin/cli -C bulk-importer', which resulted in the following:

sudo: /etc/sudo.conf is owned by uid 33, should be 0
sudo: /etc/sudo.conf is owned by uid 33, should be 0
sudo: /etc/sudoers is owned by uid 33, should be 0
sudo: error initializing audit plugin sudoers_audit

I then ran a 'chown -R www-data:www-data /var/www/html/importing/', followed by '/var/www/html/app/bin/cli -C bulk-importer' and the response was:

1770596234 - [Thread #0] Import process started (job ID 1)
1770596234 - [Thread #0] ================================================================================
1770596234 - [Thread #0] Nothing parsed in /var/www/html/importing/no-parse
1770596234 - [Thread #0] DB status changed to completed
1770596234 - [Thread #0] DB status should be changed to "working" to keep this job alive
1770596234 - [Thread #0] About to remove /var/www/html/importing/no-parse directory contents (recursively)...
1770596234 - [Thread #0] The directory is already empty, no need to iterate its contents
1770596234 - [Thread #0] Directory /var/www/html/importing/no-parse contents removed
1770596234 - [Thread #0] Chunked process ended
1770596234 - [Thread #0] ================================================================================
* Processing job id #2
1770596234 - [Thread #0] Import process started (job ID 2)
1770596234 - [Thread #0] ================================================================================
1770596234 - [Thread #0] Nothing parsed in /var/www/html/importing/parse-users
1770596234 - [Thread #0] DB status changed to completed
1770596234 - [Thread #0] DB status should be changed to "working" to keep this job alive
1770596234 - [Thread #0] About to remove /var/www/html/importing/parse-users directory contents (recursively)...
1770596234 - [Thread #0] The directory is already empty, no need to iterate its contents
1770596234 - [Thread #0] Directory /var/www/html/importing/parse-users contents removed
1770596234 - [Thread #0] Chunked process ended
1770596234 - [Thread #0] ================================================================================
* Processing job id #3
1770596234 - [Thread #0] Import process started (job ID 3)
1770596234 - [Thread #0] ================================================================================
1770596234 - [Thread #0] Nothing parsed in /var/www/html/importing/parse-albums
1770596234 - [Thread #0] DB status changed to completed
1770596234 - [Thread #0] DB status should be changed to "working" to keep this job alive
1770596234 - [Thread #0] About to remove /var/www/html/importing/parse-albums directory contents (recursively)...
1770596234 - [Thread #0] The directory is already empty, no need to iterate its contents
1770596234 - [Thread #0] Directory /var/www/html/importing/parse-albums contents removed
1770596234 - [Thread #0] Chunked process ended
1770596234 - [Thread #0] ================================================================================
~They took our jobs!~

At that point, it immediately blew up. The OS is responding, but the web UI pretty much immediately went to 'Something went wrong' and is stuck there.

Any suggestions? If I need to rebuild from scratch, it's not the end of the world because I only had one small album at this point, but the fact that trying to import images like this literally blew it up is... concerning...

Importing images in small quantities has never been an issue, but when I take pictures of my daughters hockey games there are typically a LOT of images (and image sequence is IMPORTANT, which is another issue...), and it seems the web UI just isn't up to the task of uploading all of those images, and the bulk import is cumbersome and apparently can roach the entire instance...

Any thoughts?

 

[Rodolfo]

That's really odd because there's no error logs, and the timestamp doesn't move at all. We do have a sample demo-importing project you can use to check for filesystem issues: https://github.com/chevereto/demo-importing

Web uploader is limited by your web browser, it is also limited by the speed of the local filesystem as it needs to hash stuff before sending the payloads. I've experienced very odd behavior when using network attached drives, mostly web browser related. For example, Chrome is champion on disk read access media files while Safari will take several seconds more (even minutes) to do the same.

 

[SubnetMask]

Any suggestions on how to get it back to a functioning state first? If I can do that, then I can take a snapshot before I try anything further, but I never expected trying to do an import to blow it up like this. I expected that at worst, the import would just fail.

Right now all I get is this:


While there wasn't much and I could get by with starting over, if there's a relatively easy way to fix it, I'd rather not.

 

[Rodolfo]

As you aren't reporting an error in the bulk importer runtime, can't assume that is bulk importer related yet.

The error you are showing happens on production context, hidding from public domain why your website failed, it is a basic security feature to avoid leaking sensitive data about your installation.

That error message contains instructions that you (as system administrator) need to follow, once you follow the guide/steps you will be able to explain and understand the current system state.

NOTE: WE DONT HAVE ANY KIND OF ACCESS TO YOUR WEBSITE OR CHEVERETO INSTALL. WE CANT TELL WHATS GOING WRONG WITHOUT YOUR COLLABORATION.