Melihat Ukuran Inbox Semua User di Zimbra

Today email server alert /opt 85% sizenya, bingung apa yg bikin penuh padahal dioutlook di seting auto delete.
cari - cari how to see ukuran inbox per email di zimbra, ternyata ada di wiki.

inilah dia, easy command :

untuk all account bisa gunakan ini :

su - zimbra
all_accounts=`zmprov -l gaa`; for account in $all_accounts; do mbox_size=`zmmailbox -z -m $account gms`; echo "Mailbox size of $account = $mbox_size"; done ;

untuk per user kita bisa gunakan contoh ini :


#su – zimbra

# zmprov gmi testuser@example.com -> To check User mailbox Size information in detail. This command show every Directory size and count of message like inbox, trash, Junk, draft and

1.  $zmmailbox -z -m testuser@example.com gms  # show only mailbox size
2.  $zmmailbox -z -m testuser@example.com gaf  #show specific directory size in detail
Here : Zmmailbox is zimbra command, -z -m is switch, testuser is your user account name, example.com is your Domain Name
gms – get mailbox size
gaf – get all file.






cortesy of
https://dilliganesh.wordpress.com/2014/05/30/how-to-check-mailbox-size-of-all-accounts-in-zimbra/
and
Zimbra wiki

ZIMBRA ZMPROV ERROR

beberapa hari yang lalu, mau coba blok spam yang selama ini ganggu banget di zimbra, mau ketik ZMPROV tau nya malah error,

zimbra ERROR: zclient.IO_ERROR (invoke sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, server: localhost) (cause: javax.net.ssl.SSLHandshakeException sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

masalah ini ternyata karena masalah sertifikat di zimbra pada saat installing certifikat tersebut / bisa karena sertifikat error saat dikenali oleh java,
bisa solve dengan 2 command berikut :

zimbra@server:~$ /opt/zimbra/bin/zmcertmgr deploycrt self

zimbra@server:~$ /opt/zimbra/bin/zmcertmgr deployca 

trs test deh run comman zmprov, hasilnya harus begini

zimbra@server:~$ zmprov

prov> exit

solve kan ?
hehehe semoga membantu.

source : 

https://forums.zimbra.org/viewtopic.php?f=15&t=57474

http://www.snapshotsofthemind.com/sun-security-validator-validatorexception-pkix-path-building-failed/ 

 

ESX Server (The remote server returned an error: (503) Server Unavailable.) HANG

Kemarin aga puyeng di sore hari.. mana mau pulang lagi karena tetiba Vcenter hang.. dan ga bisa akses production esx server, tapi drc dan esx lain bisa di akses. saat coba akses dari esx client error nya ini :

The server could not interpret the communication from the client. (The remote server returned an error: (503) Server Unavailable.)


bingung dah, karena ga pernah ngalamin error kaya gtu kan.. feeling sih karena si vcenter hang jadi agent di esx ini ikutan hank juga. finally browse sana ini dapet solusi yang kaya bgni deh yang works

 step nya cuma 1 koq:

restart My Management agents, vpxa agents and management network pake command ini  😁:

Service mgmt–vmware restart (VMware Management agents)

Service vmware-vpxa restart (Vcenter agent)

Service network restart (management network)

klo pake yg di atas ga bisa, coba pake command ini :

so. ga perlu restart hostnya !

ps: in this case ESX Server version 5.5

ZIMBRA High Cpu Because of Java

Today.. i get a lil bit messy day. because my mail server made me to came to office while in Off Day.
cus the server stop responing. and after get a lot of works to access the HTOP. i got this number. What a Shit kan !!!!.


this is what ive got from HTOP.

what a mess usage...

a lot of alternatives to solve this.

First, I started with disabling services that I really wasn’t using ( not working in this version  maybe )

zmprov ms su********.com  -zimbraServiceEnabled snmpzmprov ms su********.com -zimbraServiceEnabled logger (Server Statistics and Server Status information is not captured.)
zmprov ms su********.com -zimbraServiceEnabled stats

But it did not help much fixing the CPU problem.

Second, because i see alot of watch dogs i did this  ( not working in this version  maybe )

$ su zimbra

$ zmlocalconfig -e zmmtaconfig_interval=3600 

change the interval on your own want.

and change the crontab to be like this.

0 * * * * /opt/zimbra/libexec/zmstatuslog

or the posiblest time on your mind.

Third, and the work way in my zimbra is doing this.
based on this paper.

[root]# su - zimbra
[zimbra]$ zmlocalconfig -e nio_imap_enabled=false
[zimbra]$ zmmailboxdctl restart

by the way, my zimbra is
Release 8.5.1.GA.3056.UBUNTU12.64 UBUNTU12_64 FOSS edition.

Restore Setting Veeam Backup & Replication

Today, cb restore setingan veeam dari server yg menurut gw ga oke buat jadi server veeam,ke server yang lain... sekalian test performance virtual win 7 based server dengan fisik.

setelah install os dll. sampe versi veeam2 nya di dapat kesimpulan :

1. saat mau migrasiin veeam versi veeam nya harus benar - benar sama, sampai versi updatenya. klo ngak, ga bakal bisa di restore tuh setingan.
2. semua job ga akan bisa jalan klo kita belum reinsert password account kita di veeam.

dah 2 hal itu aja  yg perlu digaris bawahi saat kita mau restore setingan veeam dari server 1 ke server lain.


dimana sih kita harus reset password itu account2, disini, menu veeam yg di pojok kiri atas ya.

nah kita tinggal reinsert aja semua password account2 dstu.

dah gtu aja.

semoga bermanfaat ya.

Seting IP Static di Ubuntu Server

ini saya copy dari site nya ubuntu  yah, soalnya sering lupa saya nya juga :D

sudo vi /etc/network/interfaces

auto eth0:1
iface eth0:1 inet static
  address 192.168.1.24
  netmask 255.255.255.0
  network 192.168.1.1
  broadcast 192.168.1.255
  gateway 192.168.1.1

For these new settings to take effect you need to restart networking services using the following command

sudo /etc/init.d/networking restart

source  : https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

How To Upgrade ESXi 5.5 to update 1,2,3...

today im trying to upgrade my esxi server, from 5.5 to 5.5 update 1,2 and 3

steps :

download the update from :
https://www.vmware.com/patchmgr/findPatch.portal

after that  : copy downloaded files into datastore
note* if you try to make new folder in the datastore, better without any space or other simbols.

then.. we go to SSH an login as root
- do check before, so we can check later if our esx upgraded or not, using the build number.
how to check ?   -- > type vmware -v in ur console

\

now we try to find the upgrade files in our datastore .

after we find it.. do the installation with esxcli command.

esxcli software vib install -d /vmfs/volumes/52f25d31-555e3b54-4de6-40f2e9248bc2/UPDATE-ESXI-5.5/update-from-esxi5.5-5.5_update03.zip

the format is

 esxcli software vib install -d ( /vmvs/volumes/datastorename/zip file location )

and when done, you need to restart your server. In this case im trying to upgrade to update 1,2,3 so i dont do restart every upgrading. 

just install update 1,2 and 3.. then i do restart.. ( im not finding any error / effect ).

like this picture below.

now we check, if it upgraded or not by sync it with the build version from the web

vmware build version

                          Version                                                                    Release date  Build number

finally my esxi upgraded...

cheers...