Resolved Why plesk dont remove the cron asociated to the subscription when you delete that subscription?

[sistemas@chequemotiva]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

Plesk Obsidian 18.0.73.3

Hi:

I see that when i delete a subscription via plesk, in /var/spool/cron/crontabs/ dont delete the file of the username of the subscription, and in the /var/log/syslog i have the following error:

Nov 11 15:26:10 giftXX cron[414]: (us_tarjetasXX) ORPHAN (no passwd entry)
Nov 11 15:30:11 giftXX cron[414]: (us_tarjetasXX) ORPHAN (no passwd entry)
Nov 11 15:32:09 giftXX cron[414]: (us_tarjetasXX) ORPHAN (no passwd entry)
Nov 11 15:35:10 giftXX cron[414]: (us_tarjetasXX) ORPHAN (no passwd entry)
Nov 11 15:36:10 giftXX cron[414]: (us_tarjetasXX) ORPHAN (no passwd entry)

I delete the file mencionated and restar service cron and the error desapear.

Why plesk dont delete this file that was asociated to the subscription?

Best regards!

 

[Maarten]

Hi,

Thanks for post. This seems like a bug to me. I've tested it myself, and it does not delete the cronjob that belongs to the subscription.

@Sebahat.hadzhi, is this a known bug, or should I report it?

 

[Sebahat.hadzhi]

@Maarten No, I don't think we have such bug registered, but I am also unable to replicate the behavior by adding a scheduled task to a subscription and then deleting the subscription. If you don't mind, please do open a bug report with the steps you performed to reproduce the issue. Thank you in advance.

 

[sistemas@chequemotiva]

hi @Sebahat.hadzhi

I think that is a bug, because when you create a new subscription, the name of Username, that create plesk in the System user credentials, create a file in /var/spool/cron/crontabs/, but, if you delete that subscription, plesk dont remove the file asociated to that susbcription, and in the log of syslog, ypu can chek that error: ORPHAN (no passwd entry)

Thanks!

 

[Sebahat.hadzhi]

Thank you for the clarification. I misunderstood that the cron remains rather than the system user. I was able to replicate the behavior now. I will double-check with our team and follow-up with more details.

 

[Sebahat.hadzhi]

Hi, @sistemas@chequemotiva . We have released an update today which fixes the issue with the remaining user. Thank you for bringing our attention to it. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.75:

Fixed the issue where the system user/subscription owner remained in the crontab file after the subscription was deleted. (PPPM-15225)

Please let us know if you face any further issues.

 

[klowet]

Does the 18.0.75 update fix this problem also for users deleted in the past? Or is this a fix for users that are deleted in the future?
If not, how can we manually remove the cron jobs for already deleted users?

 

[sistemas@chequemotiva]

Hi:

I check that when i delete a subscription in plesk version 18.0.75, delete de user asociated that suscription ok.

If you have users that are delete in the pass, yo can check in this log:

cat /var/log/syslog | grep 'ORPHAN (no passwd entry)'

The cron jobs is in that directory of ubuntu:

ll /var/spool/cron/crontabs/

And then you can delete o mv the file that dont have user asociated to a subscription, and in the log of cron dont appear whit error.

Bye!