Skip to main content

During cleanup, in some cases, jobs for a few users get stuck in the running state and do not progress. The jobs neither fail with an error nor move to the completed phase, remaining in the running state for days. Is there any additional setting related to this issue or a timeout for a user's cleanup process?

hi @Burak Kosker 

please confirm cvmailcleanup.log for user which is currnelty stuck if you see below traces
or 
please confrim the current quota settings for the user mailbox in stuck state

Exception: nMailbox has exceeded maximum mailbox size., Cannot save changes made to an item to store.]
Exception: nThe message exceeds the maximum supported size., Cannot save changes made to an item to store.]

Yes, we sometimes receive this message, but our question is how we can skip that process because our customers do not want to constantly monitor the jobs. If there is a quota problem, they want to skip that user and automatically continue the job.


Hi @Burak Kosker 
Thank you for confirmation.
The cleanup job currently checks mailbox size to ensure it does not exceed the maximum allowed quota.

The cleanup process skips mailboxes that are full before initiating cleanup, accompanied by the following message:

" Skip/Failure Reason: :Mailbox is over quota. No space to save stubbing changes.]"

If the cleanup process stalls due to quota issues, consider manually freeing up space or expanding the quota for the affected mailboxes, then resubmit the job.

An internal  modification request (CMR) has been raised for this issue handling, which occurs when a mailbox reaches its quota during the cleanup process, leading to multiple reattempts.

This problem will be addressed in the upcoming Feature Release , which is currently in development. The added functionality ensures that if a message fails with an 'over quota' error, the mailbox is marked as failed.

 


Reply