Why am I receiving a "spawn ETXTBSY" error on my node.js step?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi, I keep getting “spawn ETXTBSY” error on my node.js step, not sure why. It used to work perfectly. Not sure what it means.

2

Hi , maybe some libraries you used have their version upgraded and became incompatible with Pipedream.

I would suggest you check all the libraries that you use to see if is there any new version from the last time that it worked.

3

The ETXTBSY error code is thrown when puppeteer is trying to start the Chromium binary but the binary file is under a exclusive lock - that can happen if you don’t wait for executablePath to resolve, or, if you call executablePath multiple times.

4

found this on github ^

5

Have you used Puppeteer library?

6

yes

7

Then I you can refer to Pipedream’s Puppeteer action implementation for a solution that’s working

8

i’m importing it like this:
import { puppeteer } from ‘@pipedream/browsers’;

9

Hi Matan,

Is this a deployed workflow? If so, have you tried increasing the memory to 2 gbs? Chromium requires a high usage of memory to start.

10

Also, if you could share the entire code step’s source it would greatly help us recreate your issue.