Okay, so its most likely to do with the instance failing to import a custom library which is not present on your cloud instance.
A good place to check this is on the server logs located at /var/log/squirro/plumber/plumber.log
You should see an error thrown there.
You can check this by SSHing into your instance:
$ ssh username@your_host.squirro.cloud
then to check the log files:
[user@host] $ less /var/log/squirro/plumber/plumber.log
or you may be able to catch it as it happens by executing squirro_tail_errors
and attempting to upload again.
[user@host] $ squirro_tail_errors
Another option is to check which modules are already installed on the server python environment by logging onto the remote server as shown above, then running:
[user@host] $ squirro_activate
and then listing the packages with
[(virtualenv38) user@host] $ pip list | column
This should give you a list of all the packaged you have on available. You can verify if you are importing any packaged not listed there.
If this is the case, you can install the packages in the squirro environment by sqitiching your user to root
and activating squirro again, then:
[(virtualenv38) root@host ]# pip install <package-name>
Otherwise if you could paste the errors you see related to the pipelet here or DM me them, I can look into it further.
Hope this helps,
Aaron