reclaim free space from mailboxes

klausade

It would definitely help a lot if you told us what the error-message you got was…

Hello,

i got this message during softdelete

root@PRD-MAIL01:~# kopano-admin --purge-softdelete 30
Softdelete purge failed
Using the -v option (possibly multiple times) may give more hints.
root@PRD-MAIL01:~#

Not really explicit :)

klausade

Run it again with the -v option, like the error-message says, you might get more information then.

root@PRD-MAIL01:~# kopano-admin --purge-softdelete 30 -v
Softdelete purge failed
Using the -v option (possibly multiple times) may give more hints.
root@PRD-MAIL01:~# kopano-admin -v --purge-softdelete 30
Softdelete purge failed
Using the -v option (possibly multiple times) may give more hints.
root@PRD-MAIL01:~#

unfortunaletly, this option does not give us any more info as it is not working …or i do not know how to use it …

apio-sys

I you are really close to having your disk full (what does df -h say?) I would suggest making some space before trying to run any heavy transactions on the database such as purge-softdelete. Are your attachments stored as files? Can you move them to another partition with enough space?

This is what i did, i extended my disk with more free space, but in the meantime i cleaned-up some mailbaoxesand asked to my users to clean theirs own maiboxes … but free space is not released …

@rworobel and yes my attachement are stored as files on disk :(

fbartels

Hello @rworobel ,

maybe you want to tell us a bit more about the versions and distributions you are using.

@rworobel said in reclaim free space from mailboxes:

root@PRD-MAIL01:~# kopano-admin --purge-softdelete 30
Softdelete purge failed

This could be because of insufficient mysql tuning. you can find some directions in https://kb.kopano.io/display/WIKI/Tuning.

I tried to follow this tuning and server was not able to restart …(mysql crashed)

I’m running
Linux PRD-MAIL01 4.1.0-ucs222-amd64 #1 SMP Debian 4.1.6-1.222.201701250821 (2017-01-25) x86_64 GNU/Linux

provided by UCS…

fbartels

@rworobel yes, but which Kopano?

What kind of error did you get for MySQL?

Myssql service won’t start … simply …and my kopano version is the following

root@PRD-MAIL01:~# kopano-admin --version
Product version: 8,1,1,10
File version: 10
root@PRD-MAIL01:~#

fbartels

@rworobel said in reclaim free space from mailboxes:

Myssql service won’t start … simply

you should be able to locate the error when looking at /var/log/mysql/error.log.

@rworobel said in reclaim free space from mailboxes:

kopano-admin --version
Product version: 8,1,1,10

Ok, that also explains why the soft delete did not run internally. this version had a bug that was later fixed in https://jira.kopano.io/browse/KC-638, which was released with Kopano 8.3.3 https://kopano.com/kopano-core-archiver-8-3-3-final-now-available/

Ok, so i absolutely must update my system asap, by the way … do you know if these updates will stop kopano services ?(no mail during updates) … and how long they will take ?

fbartels

Hi @rworobel ,

yes services will be stopped during package upgrade.

Ok do you have any upgrade/update documentation of these systems ? i’m a newbie in kopano world and the server was not installed by me… so i’m lost with people claiming :(…in any case thx a lot for you help.

fbartels

HI @rworobel ,

if you have a subscription upgrading is as simple as adding our repositories to your sources.list and the doing an apt-get update && apt-get upgrade.

If you don’t have a subscription you could follow the steos in https://documentation.kopano.io/kopanocore_administrator_manual/upgrading.html. Most importantly 4.1, 4.2 and 4.5 (since you’re on Ubuntu).

Ok, as i’m using univention operating system, the procedure stills to be the same ? or should i do something else/more ?

fbartels

Hi @rworobel ,

if you have a subscription you could follow https://wiki.z-hub.io/display/K4U/Updating+Kopano+packages+directly+from+the+Kopano+download+server (page offline at the moment because of server troubles, should be online rather soonish).

The only thing to have in mind here is that if you manually update on ucs 4.1, you could run into issues when during upgrade to ucs 4.2.

ok, the documentation webpage is back from hell :) … but should i first upgrade my UCS to 4.1 before ? of just appling this procedure is enough ?