https://pulumi.com logo
#general
Title
# general
s

straight-insurance-27894

11/20/2019, 8:21 PM
THere are no other instances of node or pulumi running. It's a fresh reboot. All yarn files match. And I can't find anything about this on the net. Chris Duck is running the same setup and is not having this issue. Have you see this issue?
g

gentle-diamond-70147

11/20/2019, 8:22 PM
Haven’t seen that. Are you on a different node version than Chris perhaps?
l

lemon-spoon-91807

11/20/2019, 8:23 PM
We have not seen that issue. And it's definitely not good. Does it survive a reboot? does it happen on every run (presumably with a different
pulumi#####
pipe)?
s

straight-insurance-27894

11/20/2019, 8:23 PM
I believe we have checked all versions, but I will double check that one
I can reboot adn it still happens, didn't track the pipe number, lmme see....
l

lemon-spoon-91807

11/20/2019, 8:24 PM
also, do you potentially run any sort of antivirus or other disk-scanning tool?
Note: one thing you can do to workaround the issue while we investigate this is the following:
s

straight-insurance-27894

11/20/2019, 8:25 PM
YES to the antivirus/diskcheck
l

lemon-spoon-91807

11/20/2019, 8:25 PM
1. it looks like you're makin a call to getSubnet. Are you making that call directly yourself?
s

straight-insurance-27894

11/20/2019, 8:25 PM
Confirmed. The pipenames are different
l

lemon-spoon-91807

11/20/2019, 8:25 PM
i.e. right here: index.ts2630. That's what the callstack seems to indicate, but i just want to check before assuming
s

straight-insurance-27894

11/20/2019, 8:27 PM
yes, lines 31 thru 36 are const subnet = azure.network.getSubnet({ name: config.require('subnet'), virtualNetworkName: config.require('vnet'), resourceGroupName: config.require('vnet-rg'), });
l

lemon-spoon-91807

11/20/2019, 8:28 PM
how do you then use that 'const subnet' later in your program?
s

straight-insurance-27894

11/20/2019, 8:28 PM
I dont'. It's leftover code.
I can comment it out
l

lemon-spoon-91807

11/20/2019, 8:28 PM
well, that could certainly potentially help 😄
s

straight-insurance-27894

11/20/2019, 8:28 PM
this is a working stack I use to try different things
l

lemon-spoon-91807

11/20/2019, 8:30 PM
in general though, until we figure out why you're gettin the EBUSY, what we can do is switch away from "synchronous invokes", and move to "async invokes". This will mean that instead of calling just
azure.network.getSubnet({ ... })
we would isntead call
azure.network.getSubnet({...}, { async: true })
.
However, if you do this, you'll get a Promise back.
So you'd either need to do:
await azure.network.getSubnet({...}, { async: true })
s

straight-insurance-27894

11/20/2019, 8:30 PM
error: Running program 'C:\work\repos\hondofoozle' failed with an unhandled exception: Error: EBUSY: resource busy or locked, open '\\.\pipe\pulumi4203104520\invoke_req' at Object.openSync (fs.js4483) at Object.tryGetSyncInvokes (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\settings.js16329) at invokeSync (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\invoke.js9536) at Object.invoke (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\invoke.js8424) at Object.getClientConfig (C:\work\repos\hondofoozle\node_modules\@pulumi\core\getClientConfig.ts3168) at Object.<anonymous> (C\work\repos\hondofoozle\index.ts59:28) at Module._compile (internal/modules/cjs/loader.js93630) at Module.m._compile (C\work\repos\hondofoozle\node modules\ts node\src\index.ts439:23) at Module._extensions..js (internal/modules/cjs/loader.js94710) at Object.require.extensions.<computed> [as .ts] (C\work\repos\hondofoozle\node modules\ts node\src\index.ts44
l

lemon-spoon-91807

11/20/2019, 8:30 PM
Or you'd need to do:
pulumi.output(azure.network.getSubnet({...}, { async: true });
these code changes will sidestep the issue above completely.
s

straight-insurance-27894

11/20/2019, 8:31 PM
ok
l

lemon-spoon-91807

11/20/2019, 8:32 PM
my guess though is that this might be related to antivirus. it might be seeing us open a connectoin between our processes and it might be scanning it.
that's a guess on my part though.
Note: this general space is one we know we have some issue around. We have an issue tracking resolving it all entirely in the near term.
s

straight-insurance-27894

11/20/2019, 8:33 PM
ok
l

lemon-spoon-91807

11/20/2019, 8:33 PM
LMK if you need any more info or help here.
s

straight-insurance-27894

11/20/2019, 8:33 PM
so run these failed commands azynchronously?
for now?
l

lemon-spoon-91807

11/20/2019, 8:33 PM
if you do need them, yes.
s

straight-insurance-27894

11/20/2019, 8:34 PM
k, will try.
thanks for the rapid response
l

lemon-spoon-91807

11/20/2019, 8:35 PM
if antivirus is the cause, let us know.
we may have to code ourselves up to be a little more resilient to this possibility