• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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