Dmitrii Kuvaiskii
Dmitrii Kuvaiskii
Unfortunately, NodeJS doesn't output some meaningful message like `eventfd() failed`. This would make it more apparent to users that Gramine's insecure emulation of `eventfd` should be enabled in the manifest....
Why do you think that it doesn't work? The last few lines are like this: ``` [P1:T1:node] trace: ---- shim_fstat(17, 0x118be2210) = 0x0 [P1:T1:node] trace: ---- shim_read(17, 0x10bdb6010, 0x177f) ......
> TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined Do you know what it can refer to? Looks like something about command-line arguments? Did you try...
Well, but you're making progress :) Any error from NodeRed? The Gramine logs look fine. Where is the error?
@p-vernaeckt Your manifest has a couple problems, which *may* be the cause of your NodeRed not running properly. - `sgx.debug = true` -- this is wrong. In GSC, you're supposed...
Yes, this looks good now. Well, your workload will need more debugging and analysis then...
We need someone to reproduce and check whether this is a real bug in Gramine. I will now set the labels to Bug and P2.
Jenkins, test this please
[Original comment from issue. Original author: @dimakuv] Thanks, Anjo. This helps greatly for applications that frequently fork children during runtime. E.g., web/database applications that fork a child for every client...
[Original comment from issue. Original author: @yamahata] When recycling zombie, its state needs to be re-initialized before receiving checkpoint. i.e. bring its status into known (initial) state.\ There are several...