Closed Eugene-Melbourne closed 6 years ago
Something is running on your local machine. We cant tell you what it is.
One option is destroy your Homestead box and re-create it, and see if the issue persists.
You are right it was a supervisor. Thank you very much.
Just for other searchers who might be frustrated:
Make sure there isn't a semi colon ending your superivsord.conf command section. The semi colon was ending up as part of the queue name and freaking everything out
Anyone else come across this, this was most likely due to having "...queue:work SQS" in the supervisord config's command... which tells laravel to use SQS connection in the config/queue.php
I recently updated to latest laravel v5.7.9, on my dev Homestead.
I'm not using queues in my project.
QUEUE_DRIVER=sync
, I have never touched file\app\Console\Kernel.php
and never configuredSQS
in.env
.But Now I'm getting file
worker.log
in my project root. It is always empty.Plus.
My Laravel.log file is getting too big for no reason. Yesterday was Sunday, I did not even switch on my Notebook (Windows 10, it may switch on by itself).
Today, I switched my computer on and find 8 Mb of a log file. First line was 8.752.288 entities of the special character
null
, then it wasthe 403 is reasonable, I don't have SQS configured, but why did it started sending something to AWS at 10 pm on Sunday, from my dev homestead?
the last record in the log was dated on [2018-10-14 22:09:27] and it did not continue triggering this stuff on Monday when I started my computer.
Please Help
*Please find full log record below:**