Answer the question
In order to leave comments, you need to log in
The cron function does not work, the logs are calm ...?
Hello, Community, the scheduler starts the task (100% starts), but it works out partially, then nothing, no logs, no errors. I remove one malicious function (writing to the database), everything works fine. What is characteristic: on the local machine everything is super good, on the host - that's ... Where to dig?? If the timeout works, he (Lara) would report in the logs. I don’t even know how to check where the Ficus was placed. Thanks in advance for your replies.
$schedule->call(function () {
// if (Sinc::getFilexml()) {
$filename=Sinc::getXMLname();
//Store::loadStore($filename);
//sleep(4);
//Auto::loadGroup($filename);
//sleep(4);
Item::loadItems($filename);
$malo='БЛА БЛА'.date("d.m.Y");
Mail::send('emails.update', ['malo'=>$malo] , function($message)
{
$message->to('****@gmail.com', 'С сайта')->subject('Слова...');
});
//}
})->everyFiveMinutes();
Answer the question
In order to leave comments, you need to log in
Look at the logs and the level of error_reporting. Logs need to be looked not only for laravel, but also for php error_log.
It will not be superfluous to write output for cron tasks to the log using php sript.php >> log/path.log
In general, I twisted it through the browser, increasing the chunk back, which led to such an error several times, although Lara wrote it to the log, well, maybe it's her. If you fantasize, then the feeling that the muscle did not have time.
1390 prepared statement contains too many placeholders
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question