• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue artisan' 'schedule:run' Appeared in a Subscription

WebHostingAce

Silver Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update #2
I’m not using Laravel in any of my subscriptions, but I noticed that a scheduled task suddenly appeared in one of my subscriptions.

Here’s the task that appeared:

---
/opt/plesk/php/7.4/bin/php '/var/www/vhosts/domain.tld/httpdocs/pub/artisan' 'schedule:run'
Extension laravel
---

Has anyone else experienced this issue? Any insights into what might be causing this?

Thank you.
 
Hello, @WebHostingAce . Judging by the Extension laravel input, the cron jobs was added by the Laravel extension. As far as I am aware, the cron in question is added when the "Scheduled Tasks" option is enabled for the domain in the extension. Is there any possibility that you/a user previously deployed Laravel for the domain name in question and manually removed the files? If not, can you recall when you noticed this cron job appearing?
 
Hi @Sebahat.hadzhi,

Thank you for your response.

This server only has the current subscription running Magento 2. We do not use Laravel at all.

Additionally, I am the only user managing this subscription and the server—there is no other user involved.

The subscription was migrated from another server (a server change), but I’m quite sure I checked the ‘scheduled tasks’ after the migration, as the Magento 2 cron job should be set up.

I was really surprised to discover the Laravel cron job today when I attempted to manually run the Magento 2 cron.

The migration was completed on April 6th, and I only found this cron job today.

Thank you.
 
Thank you for the confirmation. I will double-check with our team if they have any suggestion on what might be leading to that behavior in these circumstances and get back to you once I have more details.
 
Back
Top