Skip to content
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

Page items failed #1

Open
steffenk opened this issue Nov 8, 2017 · 6 comments
Open

Page items failed #1

steffenk opened this issue Nov 8, 2017 · 6 comments

Comments

@steffenk
Copy link

steffenk commented Nov 8, 2017

Hi - just checked out master and tried it on one site. I created the configuration for pages, created the tasks and run.
Problem is that all items failed
bildschirmfoto 2017-11-08 um 11 47 20
Unfortunally there is no way in BE to see the errors, but in DB i found the entries, eg:

An error occurred. The call to the url "http://ewp.t3/index.php?id=26&L=0" returned the status code 500
Testing the url in FE gave no error at all.

@thommyhh
Copy link
Contributor

thommyhh commented Nov 8, 2017

Hi Steffen, thank you for your feedback. The will be added a backend module to view the failed items in a future version.

What does your error log about the 500 error?

@steffenk
Copy link
Author

steffenk commented Nov 8, 2017

Hi Thommy,
there is no entry in error log. I also recognized, that a second run of process ignored the failed items - i thought they will be reprocessed, so i had to empty the table first.
I now will debug the crawler.

@thommyhh
Copy link
Contributor

thommyhh commented Nov 8, 2017

Well, there should be an error log for the host ewp.t3, from the webserver and/or php. That would give more information about the actual error. I would try that first.

For debugging, try starting in FrontendRequestCrawler::processQueueItem ll. 57-59.

@thommyhh
Copy link
Contributor

thommyhh commented Nov 8, 2017

And if you have frontend debugging enabled, try deactivating it and run the queue again. The failed items are re-scheduled by running the queue task again.

@thommyhh
Copy link
Contributor

@steffenk Have you found something out here? Either way, you could try the new version 1.0.1. I made some fixes there, that could have caused some trouble.

@glucka
Copy link

glucka commented May 25, 2018

Hi, i had the same problem, the reason was: domain record did not exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants