CLI exiting with error code 133 on AWS Lambda

Any updates on this yet? It has soon been 2 months

Best regards
Magnus

Hi Magnus,

I apologize for the delay from our side. Our devops team is in the process of setting up an environment that will allow us to use Lambda within the company. They are reviewing the process now and once it is ready we will attempt to reproduce this exact issue. Unfortunately this has been out of our hands, but we hope to have it ready soon.

Thank you again for your patience,

Artem

Just checking in again. Soon to be 3 months.

Again, please - please reach out if you need any help!

We're blocked due to this not working...

Best regards
Magnus

Hi Magnus,

We have gotten access to AWS Lambda and have been able to reproduce the same issue in our own environments. Thank you for your detailed instructions on how to reproduce this issue, it really helped speed up the process. My first impression is that this may be caused by the interaction of node with the way in which Lambda runs its processes. However I do not have a solution to propose to you at this time. We will continue to look into this to try and help you alleviate this blocker.

Thank you and I hope to have more details for you soon,

Artem

Hi Artem

Thanks for the response, happy to hear that you are able to reproduce the issue!

My initial problem was actually running it through PHP, node was just easier to set up for reproducing the problem.

Looking forward to hearing more!

A possible problem is that Lambda runs in READONLY mode for all directories except for /tmp directory. Meaning if any script attempts to create new files etc. it won't be able to unless it is in the /tmp directory.

This could be a problem for config files etc.

Any updates?

Bump

Hi @magnusboye,

I'm sorry that you're running into this for so long without a solution.

When signing in to a new account, the CLI stores the account configuration in a configuration file. By default that's stored in ~/.op/config. Could you try overwriting the configuration directory using the --config flag to a directory in /tmp that is writable?

If this doesn't solve it, yes, let's jump on a call together and get it sorted out. I want to help you get up and running with this.

Cheers,
Simon

Hi @1P_Simon

Thanks for the response!

I did retry setting it all up again and actually got it running. Not sure if it is due to AWS making changes in Lambda or just updating to the newest version of the CLI

The issue can be closed now :-)