Crontab wiped on upgrade

1

Hello,

We did the upgrade to the new Bluecherry version yesterday (v3.1.1). Doing so, we’ve noticed that the script entirely wiped the crontab for the root user and force it to have its own two line and nothing else in it.
Would it be possible to add a small statement in there to check if something is there and readd it? Or simply check for both lines individually and not add them if they are already there?

Thank you

1 Like
2

I agree that it’s a pain, every time Bluecherry update I have to go back and rewrite my crontab.
some logic to the crontab writing wouldn’t hurt or even I believe the certbot could be handled by a systemd service instead, but it indeed need fixing.

3

Set to be fixed in 3.1.6

1 Like