• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Forwarded to devs Scheduled task format changes when a subscription is suspended and reactivated

macadia

Basic Pleskian
Username:

TITLE

Scheduled task format changes when a subscription is suspended and reactivated

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.73_build1800251009.17 os_RedHat el9
AlmaLinux 9.6 (Sage Margay)

PROBLEM DESCRIPTION

When a subscription is suspended, all scheduled tasks created under it are deactivated. That's correct, but when the subscription is reactivated, although the scheduled tasks that were active are reactivated, they lose their original formatting and associated comments.

STEPS TO REPRODUCE

Create a cron using execute PHP script with argument

Example:
httpdocs/cms/crontabs/cron_php.php argument_value
Notify users of available replacement products for created requests // this is a comment
*/15 9-21 * * *

Suspend the subscription
Reactivate the subscription again
Check the scheduled tasks page
Edit 1 scheduled tak

ACTUAL RESULT

(/opt/plesk/php/8.4/bin/php -f 'httpdocs/cms/crontabs/cron_php.php' -- 'argument_value') */15 9-21 * * *

KDJdE3g.jpg


EXPECTED RESULT

KDJf07e.md.jpg


ANY ADDITIONAL INFORMATION

For users who aren't as advanced as me, it's important to maintain the cronjob format exactly as it was created, and keeping the comments is even more important.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Hello, @macadia . Thank you for the report. I was able to replicate the described behaviors after the subscription suspension and forwarded them to our team for further review.
 
Thank you for your patience. The disappearance of the description was registered as bug identified with ID PPPM-15196. The prepending of the PHP binary location with PPPM-15210. Regarding the latter, our team determined that this only occurs if the scheduled task is modified while the subscription is suspended. Thus, it is recommended to avoid doing so until the bug is fixed. At this point, I cannot provide an ETA on when the fixes will be introduced. You can monitor the changelog here.

On a side note, according to one of the screenshots the configuration appears to be "Run as command" - when PHP scripts are being used, it is best to stick to the "Run as PHP script" option:

 
Hi, my PHP cronjobs were created as PHP Script but they automatically have converted to Run as command where the subscription was activated again... That it why I opened this report. I don't understand your side note... The screenshots are ok. The first is THE ACTUAL RESULT -crons converted by Plesk- and the second THE EXPECTED RESULT -cron reconfigured by me-.

And I add information, where this happens, if you run the contab manually it won't work... So I have to modify all my crons manually to restore them.
 
I think you misunderstood my post... The crons change from PHP Script to Run as Command where you deactivate and reactivate a subscription... That's the problem, not the comment lost (what happens too).
 
Thank you for the update and clarification. My point is, that if you do not interact with the scheduled tasks while the subscription is in suspended state, the issue should not occur. Nevertheless, this is just a workaround suggestion until our team introduce an official fix for the issues. They already determined the root cause of the issue thanks to your report and, hopefully, the fix will be introduced soon. Thank you once again for bringing our attention to the issue.
 
Back
Top