License was not automatically updated: KeyUpdate Result code: 2 Network failure

Follow

Comments

2 comments

  • Avatar
    b_p

    The expression as explained in Option 1 seems to be the easiest solution. Why isn't this single line of code included by default? As the solution is already clear, that should be part of the next microupdate!

    In addition, the article might let the reader assume that you should shift the task exactly by +/- 1 hour or +/-30 minutes (first sentence in Option 1). But since that basically brings the server to the next/previous time zone, the problem might appear again. Using a random time seems more appropriate.

    For option 2: is there a reason why you gave the time range of +/- 30 minutes? Would it hurt if the job starts much earlier/later?

  • Avatar
    Nikolay Zhmuk

    @b_p , solution in Option 1 is not a proper one, the recommended way to change execution time for Daily Maintenance is through task scheduler like cron or anacron.

    About random time for DailyMaintenance task there is a feature request https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/18978205 and I assume you have voted for this already.

    > For option 2: is there a reason why you gave the time range of +/- 30 minutes? Would it hurt if the job starts much earlier/later?
    The main requirement for the start time is to run DailyMaintenance task when the server load is minimal.

    Thank you for the input, the article has been updated.

Please sign in to leave a comment.

Have more questions? Submit a request