-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Crawler stops between 95 and 98%. #1356
Comments
Can you paste the complete stack trace? |
|
You have an empty |
After the update comes a new error.
|
... |
Where should the MySQL server be going? ... the page is running ... the crawler rotates at 96%. 🎃 |
I can't help you anymore here without having a copy of the whole setup, sorry. The MySQL server shuts down, you have to debug on your own why that happens. Maybe there is some endless loop, maybe not. |
On the command line, the crawler runs without problems. |
Now I have found the link. 💡 https://brkwsky.de/blog-leser/diese-drei-tools-erleichtern-unseren-arbeitsalltag
nofollow noreferrer noopener?! |
|
I have a similar problem. Only links that contain rel="nofollow" are correctly tagged with "rel-nofollow" in the table "tl_crawl_queue". With rel="nofollow noopener" it doesn't work. |
Indeed. Fixed in terminal42/escargot@f01decb and released as 0.5.3. Update your dependencies so you get the latest |
Great... thanks for the fast fix! |
I fixed the problem @LIVID-Media was mentioning. I cannot fix your problem until I have proper instructions on how I can reproduce the issue. |
i can share my screen? @Toflar |
I couldn't spot any issues. The crawler finishes correctly and crawls through all the data. |
Ok, that's a good idea. |
PR is here: #1396 |
Tadaaaa, now it works and the crawler was lightning fast. ❤️ |
…see #1396) Description ----------- It was confusing and it does not provide any added value. Also, it just slows down CLI rendering. Also see contao/contao#1356. Commits ------- 74a2e108 Do not show the current URI in progress bar title on crawl command
@Toflar Can it be, that the newest version detects console-commands as GET Requests but has no URI, because we are on the console? I'm getting a similar error on all cronjob-commands, since i updated from Contao 4.9.1 to 4.9.2 with all dependencies. One example command would be: Error: As a Hotfix i added this: Is this a local problem in my page or something caused by a logic-error in the SearchIndexListener? Thanks in advance for your help |
That doesn't look like any issue of the crawler no. But it looks like the BC layer of the |
See #1637 |
Is there an update or fix for this? Everytime i update Contao, I get this error every minute (by cron) until I insert the hotfix by @rorych .
|
Affected version(s)
4.9
Description
On my website the new crawler stops between 95 and 98%.
The following error message can be found in the log files.
[2020-02-19 09:02:23] request.CRITICAL: Uncaught PHP Exception InvalidArgumentException: "Unable to parse URI: http://" at /www/htdocs/vendor/nyholm/psr7/src/Uri.php line 51 {"exception":"[object] (InvalidArgumentException(code: 0): Unable to parse URI: http:// at /www/htdocs//vendor/nyholm/psr7/src/Uri.php:51)"} []
How to reproduce
I can show you my installation.
The text was updated successfully, but these errors were encountered: