Greetings friends, the Zimbra Community has that magic that makes you keep writing every day, commenting in forums, or contributing to GitHub with Scripts. As many of you know, I created a Script called ZimbraEasyInstall some time ago that helped us to deploy a Zimbra instance on Ubuntu in a very simple way. The other day I received an update to this code (thanks to Luis Perez) and now it also supports CentOS/RHEL, so today I want to show you how easy it is to install Zimbra Collaboration 8.7. x, in CentOS/RHEL in a completely automated way, here we go.
Hello, everyone, I've been working with the VMware Content Library for quite some time, I've blogged about it here in Spanish. So, I've decided to create my own Zimbra Content Library, one of the first in the entire world, so you can sync it and deploy Zimbra in a really easy way.
Zimbra TemplatesFor the very first version of this project, I've used the latest Zimbra Collaboration 8.7.11 GA, and for the OS I've chosen Ubuntu 16.04 LTS, here are more details about this template:
- vCPU: 4
- vRAM: 8GB
- vDISK1: 50GB / partition and SWAP
- vDISK2: 100GB /opt partition
- SCSI Controller: VMware Paravirtual
- Networking: VMXNET3 - IP 192.168.1.150
- Template compatible with VMware 5.5 and above
- It does include the Open VMware Tools
- OS Credentials:
- User: oper
- Password: Zimbra2017
- Zimbra Credentials:
- User: admin
- Password: Zimbra2017
How to connect to the Zimbra Content LibraryWe can manage our VMware Content Library directly from the vSphere Web Client Flash, or even the new HTML Client, available starting vSphere 6.5 U1 or with the fling as I've explained multiple times on this Spanish blog post. The first step is to select a name for this Content Library and the vCenter Server:
Hello everyone, for the last couple of days I've been receiving notifications from my monitoring systems about disk issues on one of my Zimbra Servers. The system is an old one I had with Zimbra Collaboration 8.6, and from there it has been upgraded to 8.7, 8.7.1 and 8.7.6 and finally to 8.7.10.
Finding the disk issueI've started with the basics, what directory or file was eating my disk space without my knowledge? To do that, I've used the commands df and du, both always handy: Checking that my disk was 100% full
df -h Filesystem Size Used Avail Use% Mounted on udev 2.0G 4.0K 2.0G 1% /dev tmpfs 396M 356K 395M 1% /run /dev/disk/by-label/DOROOT 59G 56G 4.0K 100% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 2.0G 0 2.0G 0% /run/shm none 100M 0 100M 0% /run/user