Closed JerryChenn07 closed 5 years ago
Did you forget to run the command 'logparser' on the machine (A)?
POST http://172.18.19.134:5000/1/api/liststats/ text:
{
"status": "error",
"message": "\n<html>\n <head><title>404 - No Such Resource</title></head>\n <body>\n <h1>No Such Resource</h1>\n <p>File not found.</p>\n </body>\n</html>\n",
"url": "http://ip:6800/logs/stats.json",
"auth": null,
"status_code": 404,
"when": "2019-02-12 14:37:51",
"tip": "'pip install logparser' on the current Scrapyd host and get it started via command 'logparser'"
}
I run scrapydweb and scrapyd in machine(A) ,also run scrapyd in error machine. SCRAPYD_LOGS_DIR--> set the same path. machine(A) can normally use, but error machine can't.
Is LogParser running on the error machine?
Oh...thanks, solved... I thought that only one machine start scrapydweb, other machines just start scrapyd...
Describe the bug Running (0) 'pip install logparser' on the current Scrapyd host and get it started via command 'logparser' to show crawled_pages and scraped_items.
To Reproduce Steps to reproduce the behavior:
Expected behavior Running (0) by LogParser: xxx seconds ago
Screenshots
Environment (please complete the following information):
Additional context I am sure I have pip install logparser this machine(A). In another machine, I can use it normally, and use this requirements.txt to pip in machine(A).