-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Timed out while waiting for the WS endpoint URL to appear in stdout! #177
Comments
After updating the memory from 512MB to 1600MB as suggested in the readme. I now get this:
|
Can you add |
This might have been fixed by 119.0.2, please check and also add |
Thanks @Sparticuz I cannot update the plugin yet as we are coming to a change freeze but I've done a dumpio:true just to see if it shows anything the next time it errors. It seems to occur in clusters and then nothing for a few days, so I am just waiting and seeing what is going on. I shall certainly try your updated plugin asap though. Many thanks for your support. |
Hi @Sparticuz, I got an error this morning but it wasn't an error that stopped it doing its job unlike before. Not sure if this extra parameter is a catch all or something and it will still continue but this is what was shown:
Another one just showed up, all seemed to convert fine but an error of:
|
Hi @Sparticuz I found a html that is created that always fails, the main issue is that it includes personal information so I can't include it here, I did do a print to pdf successfully on chrome and did notice it is 99 pages, also tried to change the timeout but it seems set to 30seconds regardless, which may be part of the reason? Not sure how I can proceed with that but I did update it to the latest version: node_modules/@sparticuz/chromium": { "node_modules/puppeteer-core": { But I still get the following and for this, it occurs every single time it is ran:
|
Just to add to above @Sparticuz it seems to be 100% related to pages, I reduced it from 99 (in chrome) to 50 (in chrome) or 61 in your plugin and it worked fine Made a quick file which has no personal information on it and hopefully you can replicate |
Sorry @Sparticuz found the issue and all it was, was lack of memory for the lambda. 30 seconds seems hard set no matter what I did but increasing the memory allocated (not just ephemeral storage) I guess ensured it could do it in less than 30 seconds |
Apologies, seem I may have closed this prematurely. I still get these even after the upgrade:
|
Hi @Sparticuz any suggestions on the above errors? Many thanks. |
Nothing specific, just try increasing memory. |
Sorry missed the last comment, those are chromium errors, take a look at your launch arguments. |
thanks @Sparticuz
I cant see what else i can change though |
@Sparticuz sorry to ping, any suggestions you can offer would be greatly appreciated as I cannot recreate this issue consistently |
Just to add more information, after adding dumpio: true I've seen I had to increase the /tmp ephemeral storage of my lambda. |
Thanks though I thought I had it already quite high but i've changed from 3000MB to 5000MB, i would have thought this would be enough? Description |
launch arguments:
|
Environment
chromium
Version: 118.0.0puppeteer-core
Version: 21.4.1Expected Behavior
No errors and runs as expected running on AWS Lambda
Current Behavior
We sometimes get this error
#TimeoutError: Timed out after 30000 ms while waiting for the WS endpoint URL to appear in stdout!
at ChromeLauncher.launch (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:149:23)
at async parseHTMLToPDF (/var/task/index.js:66:21)
at async Runtime.exports.handler (/var/task/index.js:128:21)
Steps to Reproduce
Unable to reproduce all the time, it seems to be random, this is the code it errors at, specifically on const browser.
Possible Solution
I am thinking whether it might be multiple run times at the same time. I initially had it at 30 seconds timeout for the whole lambda which ran fine on the old chromium method before upgrading to yours following a forced change from nodejs12 which meant we couldn't revert back to it and saw that this is the only repo working so I did the conversion following your npm help. I saw these timeout issues so tried increasing to 3 minutes but to no avail.
This does not seem to occur all the time and anyway of replicating the failure each and every time has not worked for me.
Your input would be greatly appreciated.
The text was updated successfully, but these errors were encountered: