-
|
I am currently utilizing changedetection and Playwright Chrome as Docker containers on a Synology NAS920 running a Linux-based OS. The deployment is managed via docker-compose. The setup works intermittently. To validate its functionality, I've set up a watch that fetches the current time every 5 minutes from a webpage using Playwright Chrome. However, this watch occasionally fails, returning the error message: I've set Within Playwright Chrome, the following log entries are particularly noticeable:
Change detection error: I'm seeking guidance on how to troubleshoot and resolve this intermittent issue. Any assistance or insights would be greatly appreciated. Complete Playwright Chrome log of a failed session.
My docker-compose: |
Beta Was this translation helpful? Give feedback.
Answered by
42Craft
Jan 7, 2024
Replies: 8 comments 7 replies
-
|
thanks for the nice debug info - " Target page, context or browser has been closed" i would say, turn all "wait seconds" down to 3, and see if it helps, keeping it open for more than 20 seconds can cause this error also the browsers might be overloaded and taking too long to respond (slow hardware?) |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I have tuned down the prefetch waiting time to 3, but it didn't make a difference. I have compared 2 runs with each other. One failed and one succeeded run. On the failed run I got this error: Complete log - succeeded run Complete log - failed run |
Beta Was this translation helpful? Give feedback.
-
|
In an effort to address the intermittent failures, I made adjustments to the settings assuming it could be related to CPU performance. The changes implemented were: Additionally, in response to the 'vulcan' error mentioned earlier and the occurrence of However, despite these modifications, the issue persists. During the moments of failure, a different error is logged: |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I too am experiencing a similar issue to vcntt. At this time I couldn't figure out where or how vcntt got their debug logs. I will see if I can find similar information for my setup and attach it. I was trying to find a solution for my errors when I came across this discussion and thought it would be helpful to share that I have a similar setup and am experiencing what appears to be similar issues. |
Beta Was this translation helpful? Give feedback.
-
|
It seems that I'm not the only one. I can also do your reproduction steps and share my log. For reference, Opened this thread few weeks ago: |
Beta Was this translation helpful? Give feedback.
-
You can add The logs can be found by selecting a container in the Synology Container Manager and then right-click, details and go to the tab logs. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Good news! I managed to resolve the issue by migrating to version 2.0 of While addressing the deprecated Environment Variables, I found only success in activating Any guidance or suggestions on additional optimizations or improvements would be greatly appreciated. Currently, I am utilizing the following configuration: |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I will try this and report back too. |
Beta Was this translation helpful? Give feedback.
-
|
if this broke for anyone else after the recent browserless/chrome update to 2.2.0, the fix for me was to change image to the following... image: ghcr.io/browserless/chromium:latest apparently browserless changed the name of the old image to chromium and created a new chrome image that actually uses chrome. Not sure how to configure the new one |
Beta Was this translation helpful? Give feedback.
Answer selected by
42Craft
-
|
Can confirm, not seeing the error since 10 hours ago. And as a plus, memory
leak of browserlwss seems to have been fixed in v2 as well. From 1gb to
0.2gb currently
…On Mon, Jan 8, 2024, 12:46 AM Vincent ***@***.***> wrote:
I have fixed the issue by using version 2.0 of browserless/chrome. Note
that version 2.0 is hosted at a new image registry.
I use this at the moment:
version: '3.2'
services:
changedetection:
container_name: changedetection
image: ghcr.io/dgtlmoon/changedetection.io:latest
hostname: changedetection
volumes:
- /volume2/docker/containers/changedetection:/datastore
ports:
- 1891:5000
restart: unless-stopped
environment:
- TZ= *REDACTED*
- PUID=*REDACTED* # you must find out your PUID through SSH, type in terminal: id $user
- PGID=*REDACTED*
- PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000/?stealth=1&--disable-web-security=true&blockAds=true
- BASE_URL=192.168.1.14:1891
depends_on:
playwright-chrome:
condition: service_started
# https://www.browserless.io/docs/docker
playwright-chrome:
hostname: playwright-chrome
container_name: playwright-chrome
#image: browserless/chrome:latest
image: ghcr.io/browserless/chrome:latest
restart: unless-stopped
expose:
- 3000
environment:
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1024
- SCREEN_DEPTH=16
- ENABLE_DEBUGGER=false
#- PREBOOT_CHROME=true <-- deprecated in v2.0
#- CONNECTION_TIMEOUT=120000 <-- deprecated in v2.0. Use TIMEOUTinstead
- TIMEOUT=60000 #60 seconds
- CONCURRENT=10 # Replaces from CONCURRENT_SESSIONS
#- CHROME_REFRESH_TIME= 3600000 <-- deprecated in v2.0
#- DEFAULT_BLOCK_ADS=true <-- deprecated in v2.0, i've added this to the playwright driver url
#- DEFAULT_IGNORE_HTTPS_ERRORS=true <-- deprecated in v2.0
—
Reply to this email directly, view it on GitHub
<#2076 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGD6KTSWQTLVX2UP6G2UGLYNLGO7AVCNFSM6AAAAABBLFHQWCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMZYGU2TS>
.
You are receiving this because you commented.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
0.2gb instead of 1gb |
Beta Was this translation helpful? Give feedback.
-
|
#1973 the PR to upgrade browserless is in progress for a while now, some failures in testing were discovered but i havent looked any deeper - if someone would have some time to help there, could be nice! |
Beta Was this translation helpful? Give feedback.
0 replies
-
I tried adding this, but it was giving me an error on I would say half of my watches are giving me the Target page, context or browser has been closed. Ram usage of playwright-chrome is 822MB for me right now and staying pretty constant. I will wait for another update to changedetection.io and try that then. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I have managed to fix this issue by using version 2 of playwright chrome. Please refer to the discussion above. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your help! The following configuration works for me: version: "3.9"
services:
changedetection:
container_name: ChangeDetection
image: ghcr.io/dgtlmoon/changedetection.io:latest
hostname: changedetection
mem_limit: 4g
cpu_shares: 768
security_opt:
- no-new-privileges:true
restart: on-failure:5
ports:
- 5054:5000
volumes:
- /volume1/docker/changedetection:/datastore:rw
environment:
- PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000/?stealth=1&--disable-web-security=true&blockAds=true
depends_on:
playwright-chrome:
condition: service_started
playwright-chrome:
hostname: playwright-chrome
container_name: playwright-chrome
image: ghcr.io/browserless/chromium:latest
restart: on-failure:5
environment:
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1024
- SCREEN_DEPTH=16
- ENABLE_DEBUGGER=false
- TIMEOUT=60000 #60 seconds
- CONCURRENT=10 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good news! I managed to resolve the issue by migrating to version 2.0 of
browserless/chrome. Please note that this version is now hosted at a new image registry.While addressing the deprecated Environment Variables, I found only success in activating
blockAdsby incorporating it into thePLAYWRIGHT_DRIVER_URL. However, I'm uncertain about further optimizations required for the setup. Perhaps @dgtlmoon could provide additional insights on this matter?Any guidance or suggestions on additional optimizations or improvements would be greatly appreciated.
Currently, I am utilizing the following configuration: