Tutorial Instalasi Zimbra Mail Server 7.1.1 pada Ubuntu Server-Bagian 3, Instalasi Zimbra

July 13, 2011

Tulisan ini merupakan tulisan ketiga dari tiga tulisan. Untuk tulisan sebelumnya bisa merujuk ke :

  1. Tutorial Instalasi Zimbra Mail Server 7.1.1 pada Ubuntu Server-Bagian 1
  2. Tutorial Instalasi Zimbra Mail Server 7.1.1 pada Ubuntu Server-Bagian 2, Setup DNS Server

Setelah semua persiapan selesai dilakukan, kita bisa mulai melakukan instalasi Zimbra dengan proses sebagai berikut :

  1. Pastikan kita sudah melakukan download file binary Zimbra dan menempatkannya pada folder /opt.
  2. Ekstrak file binary, masuk ke folder hasil ekstrak dan jalankan script instalasi (jangan lupa sesuaikan nama file .tar.gz yang digunakan) :
    cd /opt
tar -zxvf zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124.tgz
cd zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124
./install.sh

Berikut adalah proses instalasi Zimbra, perhatikan bagian yang dicetak tebal (tanda # merupakan tanda bahwa semua perintah dijalan dengan hak akses root/sudo). Beberapa tampilan yang terlalu panjang saya potong untuk alasan kerapian tulisan tanpa menghilangkan kejelasan alur proses instalasi.

Tanda pemotongan baris yang terlalu panjang saya berikan dalam bentuk tanda titik tiga kali (…).

# tar -zxvf zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124.tgz

zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124/
zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124/packages/
...
zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124/readme_binary_en_US.txt
zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124/install.sh
zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124/README.txt

# cd zcs-7.1.1_GA_3196.UBUNTU10_64.20110527011124
# ./install.sh

Operations logged to /tmp/install.log.17313
Checking for existing installation...
zimbra-ldap...NOT FOUND
zimbra-logger...NOT FOUND
zimbra-mta...NOT FOUND
zimbra-snmp...NOT FOUND
zimbra-store...NOT FOUND
zimbra-apache...NOT FOUND
zimbra-spell...NOT FOUND
zimbra-convertd...NOT FOUND
zimbra-memcached...NOT FOUND
zimbra-proxy...NOT FOUND
zimbra-archiving...NOT FOUND
zimbra-cluster...NOT FOUND
zimbra-core...NOT FOUND
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
ZIMBRA, INC. ("ZIMBRA") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.
License Terms for the Zimbra Collaboration Suite: http://www.zimbra.com/license/zimbra_public_eula_2.1.html
Do you agree with the terms of the software license agreement? [N] y
Checking for prerequisites...
FOUND: NPTL
...
FOUND: perl-5.10.0
FOUND: sysstat
Prerequisite check complete.
Checking for installable packages
Found zimbra-core
...
Select the packages to install
Install zimbra-ldap [Y] y
Install zimbra-logger [Y] y
Install zimbra-mta [Y] y
Install zimbra-snmp [Y] y
Install zimbra-store [Y] y
Install zimbra-apache [Y] y
Install zimbra-spell [Y] y
Install zimbra-memcached [N] n
Install zimbra-proxy [N] n
Checking required space for zimbra-core
checking space for zimbra-store
Installing:
zimbra-core
zimbra-ldap
zimbra-logger
zimbra-mta
zimbra-snmp
zimbra-store
zimbra-apache
zimbra-spell
The system will be modified. Continue? [N] y
Removing /opt/zimbra
Removing zimbra crontab entry...done.
Cleaning up zimbra init scripts...done.
Cleaning up /etc/ld.so.conf...done.
Cleaning up /etc/security/limits.conf...done.
Finished removing Zimbra Collaboration Suite.
Installing packages

...

Operations logged to /tmp/zmsetup.01202011-203128.log
Installing LDAP configuration database...done.
Setting defaults...
DNS ERROR resolving MX for mail.vavai.com
It is suggested that the domain name have an MX record configured in DNS
Create domain: [mail.vavai.com] vavai.com

Jika mendapat pertanyaan soal “DNS ERROR resolving MX”. Jawab “Y” untuk mengubah nama domain dan kemudian ketik nama domain (dalam contoh misalnya : vavai.com) bukan mail.vavai.com.

CATATAN : Jangan by pass proses ini. Jika masih tetap bermasalah di tahap ini, periksa ulang konfigurasi DNS yang dilakukan pada tahap 2 karena kemungkinan besar ada masalah pada saat setting DNS Server.

Setelah di enter, proses install akan berlanjut :

MX: mail.vavai.com (192.168.10.250)
Interface: 192.168.10.250
Interface: 127.0.0.1
Interface: 127.0.0.2
done.
Checking for port conflicts
Main menu
1) Common Configuration:
2) zimbra-ldap: Enabled
3) zimbra-store: Enabled
+Create Admin User: yes
+Admin user to create: admin@vavai.com
******* +Admin Password UNSET
+Enable automated spam training: yes

...

4) zimbra-mta: Enabled
5) zimbra-snmp: Enabled
6) zimbra-logger: Enabled
7) zimbra-spell: Enabled
8) Default Class of Service Configuration:
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit
Address unconfigured (**) items (? - help) 3

Pada proses diatas, ketik angka 3 untuk mengubah pilihan yang belum disetting, dalam hal ini adalah konfigurasi password untuk Admin.

Zimbra akan memberikan informasi mengenai pilihan yang belum disetting, yaitu Zimbra Password :

Store configuration
1) Status: Enabled
2) Create Admin User: yes
3) Admin user to create: admin@vavai.com
** 4) Admin Password UNSET
5) Enable automated spam training: yes
...

Select, or 'r' for previous menu [r] 4
Password for admin@vavai.com (min 6 characters): [RGu2usa9S] MySecretPassword

Zimbra akan bertanya soal Zimbra Admin password pada konfirmasi akhir sebelum proses instalasi. Ketikkan saja password pada kotak yang disediakan, tapi awas hati-hati, password akan ditulis dalam formasi plain text dan tidak dimasking/enkripsi.
Masukkan password kemudian tekan ENTER

Store configuration
1) Status: Enabled
2) Create Admin User: yes


...

23) Version update notification email: admin@vavai.com
24) Version update source email: admin@vavai.com

Select, or 'r' for previous menu [r] r

Tekan huruf r untuk kembali ke menu pilihan

Main menu
1) Common Configuration:
2) zimbra-ldap: Enabled

...

x) Expand menu
q) Quit
*** CONFIGURATION COMPLETE - press 'a' to apply
Select from menu, or press 'a' to apply config (? - help) a
Save configuration data to a file? [Yes] yes
Save config in file: [/opt/zimbra/config.22361]
Saving config in /opt/zimbra/config.22361...done.
The system will be modified - continue? [No] yes

Sampai tahap ini proses akan berlanjut secara otomatis, kita hanya perlu memperhatikannya saja.

Operations logged to /tmp/zmsetup.01202011-203128.log
Setting local config values...done.
Setting up CA...done.

...

Checking for default IM conference room...not present.
Initializing default IM conference room...done.
Setting up syslog.conf...done.

You have the option of notifying Zimbra of your installation.
This helps us to track the uptake of the Zimbra Collaboration Suite.
The only information that will be transmitted is:
The VERSION of zcs installed (7.1.1_GA_2692_UBUNTU10_64)
The ADMIN EMAIL ADDRESS created (admin@vavai.com)

Notify Zimbra of your installation? [Yes] yes

Sebagai bagian proses tracking statistik pengguna Zimbra, Zimbra akan memberikan notifikasi ke server pusat. Kita bisa memilih untuk memberikan notifikasi atau tidak.

Notifying Zimbra of installation via http://www.zimbra.com/cgi-bin/notify.cgi?VER=7.1.1_GA_3196_UBUNTU10_64&MAIL=admin@vavai.com
Notification complete
Starting servers...done.
Installing common zimlets...
com_zimbra_date...done.
com_zimbra_bulkprovision...done.
com_zimbra_dnd...done.
com_zimbra_email...done.
com_zimbra_cert_manager...done.
com_zimbra_phone...done.
com_zimbra_url...done.
com_zimbra_adminversioncheck...done.
com_zimbra_ymemoticons...done.
Finished installing common zimlets.
Initializing Documents...done.
Restarting mailboxd...done.
Setting up zimbra crontab...done.
Moving /tmp/zmsetup.01202011-203128.log to /opt/zimbra/log
Configuration complete - press return to exit

Setelah proses instalasi selesai, kita bisa melakukan proses pengecekan status menggunaka perintah zmcontrol status :

su - zimbra
zimbra@mail:> zmcontrol status
Host mail.vavai.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running
zimbra@mail:~> zmcontrol -v
Release 7.1.1_GA_3196.UBUNTU10_64 UBUNTU10_64 FOSS edition.

Zimbra web mail dapat diakses menggunakan host name atau IP Address (dalam contoh saya : http://mail.vavai.com atau http://192.168.10.250) sedangkan Zimbra Admin dapat diakses menggunakan protokol https pada port 7071 (https://mail.vavai.com:7071 atau https://192.168.10.250:7071)


Share

Debian/Ubuntu Family  / Migrasi Server

Masim Vavai Sugianto
Masim Vavai Sugianto, Tinggal di Bekasi, Bekerja sebagai wirausahawan/Konsultan IT. Penganjur penggunaan sistem Linux dan aplikasi Open Source. Hobby Membaca, Hiking dan Avonturir. Mengembangkan PT. Excellent Infotama Kreasindo sebagai lembaga training dan IT consulting.

You might also like

Perputaran Roda Kehidupan
March 6, 2019
Kumpul Bersama Team Excellent
February 28, 2019
Usia 40
January 28, 2019

66 Comments


Bambang
June 18, 2012 at 9:18 am

@ Mas Dani
Thanks mas.. udah solve sekarang. kemaren aku ganti nama hostname nya.
tadinya hostname nya cuma “mailserver” terus aku ganti sesuai dengan yang di /etc/hosts yaitu “mail.domain.com” dan proses instalasi bisa jalan.


edi
June 19, 2012 at 3:22 pm

zimbra@zimbra:/home/edi$ zmcontrol status
host zimbra.sanggarbatik.com
antispam Running
antivirus Running
imapproxy Stopped
zmnginxctl is not running
Idap Running
logger Running
mailbox Running
memcached Running
mta Stopped
postfix is not running
snmp Running
spell Running
stats Running
zmconfigd Running

ip lan : 192.168.80.1/24

ip zimbra 192.168.20.200

unutk kasus : saya tidak bisa buka https:192.168.20.200:7071 dari ip lan ..
dari sttatus ada yang tidak running, tetapi saya tidak tau file apakah itu, dan saya tidak bisa akses zimbra nya,, mohon koreksi dan bantuannya mas,, di maana salah nya,, terimakasih sebellum nya.


ariec
November 28, 2012 at 10:06 am

mas saya habis install kok pas ketik IP atau domain selalu muncul 192.168.1.3/zimbra. apa /zimbra itu gak bisa d hilangkan


Abie Zamhur
January 25, 2013 at 6:41 pm

Zimbra saya berhasil jalan , tp tidak bisa send and receive email dari user lain meskipun kedua user tsb dari server zimbra yg sama
saya pake ZCS 8.0.2 di ubuntu server 12.04, mohon bantuan nya mas


Masim Vavai Sugianto
January 27, 2013 at 5:25 am

@Abie Zamhur,

Coba dipaste error message yang ada di file /var/log/zimbra.log atau bisa juga di check di Zimbra Admin | Queue | Error Queue, disisi kanan biasanya ada pesan errornya.


Bagus
February 13, 2013 at 1:03 pm

mas, ada tutorial cara konfigurasi zimbra mail server nya ngga y…
klo blum, diadain dong mas..


Arie
March 6, 2013 at 1:20 am

mas saya mau tanya, klo pake IP lan gitu berarti kan under mikrotik ya, trus gemana caranya biar bisa di akses di luar dari jaringan lan tersebut apakah harus port forwarding
Contohnya server mail saya pake koneksi Firstmedia atau speedy


aan
September 30, 2013 at 1:06 pm

mas vavai , saya mau tanya , saya dah setup dns dan install zimbra , test uji coba lewat jaringan lokal bisa , yang jadi permasalahan adalah , tidak bisa kirim email ke luar dan tidak bisa menerima email keluar, hal apa saja yang harus saya install , mohon dibantu , terimakasih.


imam
March 5, 2014 at 9:15 am

mas, kalau di tempat saya, service-nya jalan semua, send-receive juga bisa, tapi di zimbra administration-nya statusnya “not running” semua kalau lewat webmail padahal kalau cek lewat command Promp Jalan, dan masalahnya itu pas install zimbra, pas di tahap “Notify Zimbra of your installation? [Yes]” terus layar blank..,

untuk Notify itu bisa gak mas, diinstalin lagi tanpa instal ulang zimbra?


Harlen
July 15, 2014 at 3:32 pm

sore mas
saya sudah coba install zimbra, tapi tidak selesai karena packages libper15.10 missing
saya coba update dan upgrade dari repo ugm yg mas kasi, gk bsa mas
solusiny gmn ya mas???
thanks


Deny
July 21, 2014 at 4:51 pm

mas saya mau tanya kalau email server saya sudah berhasil kirim ke gmail dll tapi ketika di balas melalui misalnya gmail tapi gagal, saya masih pake domain gratis.


Deden
October 14, 2014 at 4:09 pm

saat proses instalasi zimbra error seperti dibawah ini
mohon pencerahannya

Install zimbra-mta [Y] y
Conflicting package: postfix

###ERROR###

One or more package conflicts exists.
Please remove them before running this installer.

Installation cancelled.


dessy
October 24, 2014 at 2:00 pm

assalamualikum

saya baru saja install zimbra version 8.0.7

semua server running tidak ada masalah, hanya saja ketika ingin masuk ke webmail client terdapat eror sebagai berikut:

“The username or password is incorrect. Verify that CAPS LOCK is not on, and then retype the current username and password.”

padahal semua user dan password sudah saya pastikan benar tetapi kenapa masih tidak bisa juga masuk ke webmail client.

mohon bantuannya mas


Khairil
January 16, 2015 at 2:00 pm

Mas Vavai,

Saya install zimbra 8.6.0_GA_1153.RHEL6_64_20141215151155 RHEL6_64 FOSS edition di Centos 6.6, namun mailboxnya tidak mau jalan. IPtable ama selinux sudah saya matikan. Postfix bawaan centos jg sudah saya matikan servicenya.

Log zmmailboxd.out:
Caused by: java.lang.IllegalStateException: Insufficient max threads in ThreadPool: max=250 < needed=277
at org.eclipse.jetty.server.Server.doStart(Server.java:321)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
… 7 more

Usage: java -jar start.jar [options] [properties] [configs]
java -jar start.jar –help # for more information

Saya dah coba ikutin saran di forum ini:
http://community.zimbra.com/collaboration/f/1888/t/1137269

Ketika saya jalankan instruksinya,
$ zmprov ms mail.mydomain.web.id zimbraHttpNumThreads 500
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

$ zmprov ms mail.mydomain.web.id zimbraHttpSSLNumThreads 250
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

Ada saran gak mas?

Terima kasih


hendro
April 17, 2015 at 11:41 am

Dear Pak Vavai,
Pak saya ada sedikit kendalam dalam install zimbra di linux unbuntu 12.04.5 64bit.untuk install zimbra sudah sukses tapi pas akses web admin zimbra di https://ipaddess:7071 lewat browser firefox tidak bisa hanya loading saja berikut saya lampirkan beberapa log nya
zimbra@mail:/root$ zmcontrol start
Host mail.sentrawatch.com
Starting ldap…Done.
Starting zmconfigd…Done.
Starting logger…Done.
Starting mailbox…Done.
Starting memcached…Done.
Starting proxy…Done.
Starting antispam…Done.
Starting antivirus…Done.
Starting snmp…Done.
Starting spell…Done.
Starting mta…Done.
Starting stats…Done.
zimbra@mail:/root$ zmcontrol -v
Release 8.0.2.GA.5569.UBUNTU12.64 UBUNTU12_64 FOSS edition.

log zimbra di /var/log/zimbra.log

Apr 17 10:45:50 mail postfix/lmtp[7871]: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out
Apr 17 10:45:50 mail postfix/lmtp[7831]: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out
Apr 17 10:45:50 mail postfix/lmtp[7873]: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out
Apr 17 10:45:50 mail postfix/lmtp[7874]: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out
Apr 17 10:45:50 mail postfix/lmtp[7872]: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out
Apr 17 10:45:52 mail postfix/lmtp[7871]: 78B2420857: to=, relay=none, delay=706, delays=637/5.1/64/0, dsn=4.4.1, status=deferred (connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:52 mail postfix/lmtp[7831]: 7A59820852: to=, relay=none, delay=711, delays=616/31/64/0, dsn=4.4.1, status=deferred (connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:52 mail postfix/lmtp[7874]: 8672720854: to=, relay=none, delay=711, delays=644/3.9/64/0, dsn=4.4.1, status=deferred (connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:52 mail postfix/lmtp[7873]: 8953E20858: to=, relay=none, delay=706, delays=638/3.9/64/0, dsn=4.4.1, status=deferred (connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:52 mail postfix/lmtp[7872]: A09DC20859: to=, relay=none, delay=706, delays=638/3.9/64/0, dsn=4.4.1, status=deferred (connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7907]: 439F920856: to=, relay=none, delay=711, delays=639/71/0/1.7, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7906]: 80A9220853: to=, relay=none, delay=716, delays=644/71/0/1.7, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7914]: 4299420855: to=, relay=none, delay=711, delays=640/69/0/1.7, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7906]: C1E0F20801: to=, relay=none, delay=717, delays=646/70/0/0.16, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7916]: C0FF12083F: to=, relay=none, delay=400, delays=329/69/0/1.8, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:45:55 mail postfix/error[7915]: 4164A20851: to=, relay=none, delay=717, delays=646/69/0/1.9, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to mail.sentrawatch.com[103.28.149.50]:7025: Connection timed out)
Apr 17 10:47:53 mail amavis[4733]: (04733-03) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:47:54 mail amavis[4733]: (04733-03) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:47:55 mail amavis[4733]: (04733-03) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:09 mail amavis[4728]: (04728-03) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:09 mail amavis[4728]: (04728-03) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:09 mail amavis[4728]: (04728-03) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:10 mail amavis[4731]: (04731-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:10 mail amavis[4731]: (04731-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:11 mail amavis[4731]: (04731-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:13 mail amavis[4732]: (04732-03) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:13 mail amavis[4732]: (04732-03) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:13 mail amavis[4732]: (04732-03) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:24 mail amavis[4729]: (04729-03) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:24 mail amavis[4729]: (04729-03) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:24 mail amavis[4729]: (04729-03) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:57 mail amavis[4739]: (04739-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:57 mail amavis[4734]: (04734-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:57 mail amavis[4739]: (04739-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:57 mail amavis[4734]: (04734-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:57 mail amavis[4739]: (04739-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:48:58 mail amavis[4735]: (04735-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:48:59 mail amavis[4735]: (04735-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:48:59 mail amavis[4734]: (04734-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:49:00 mail amavis[4737]: (04737-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:49:00 mail amavis[4737]: (04737-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:49:00 mail amavis[4737]: (04737-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:49:16 mail amavis[4735]: (04735-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:49:16 mail amavis[4736]: (04736-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 112) line 598.\n
Apr 17 10:49:26 mail amavis[4736]: (04736-02) (!)WARN: all primary virus scanners failed, considering backups
Apr 17 10:49:30 mail amavis[4736]: (04736-02) (!!)AV: ALL VIRUS SCANNERS FAILED
Apr 17 10:49:45 mail amavis[4733]: (04733-03) SA info: dns: socket buffer size error: __alarm__ignore__(152/::PerMsgStatus::check/584)
Apr 17 10:50:10 mail amavis[4735]: (04735-02) (!)checking with spam scanner SpamAssassin failed: timed out
Apr 17 10:48:50 mail postfix/qmgr[5258]: 63BE72075C: from=, size=1169, nrcpt=1 (queue active)
Apr 17 10:50:11 mail amavis[4736]: (04736-02) (!!)TROUBLE in check_mail: spam-wb-list FAILED: timed out
Apr 17 10:50:14 mail amavis[4735]: (04735-02) (!!)TROUBLE in check_mail: spam_scan FAILED: SpamAssassin failed: timed out at (eval 113) line 158.
Apr 17 10:50:39 mail amavis[4734]: (04734-02) (!)SA TIMED OUT, backtrace: at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin.pm line 538.\n\teval {…} called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin.pm line 538\n\tMail::SpamAssassin::parse(‘Mail::SpamAssassin=HASH(0x4c47a88)’, ‘SCALAR(0x3960fa8)’, 0, ‘HASH(0x398a710)’) called at (eval 114) line 720\n\teval {…} called at (eval 114) line 793\n\tAmavis::SpamControl::SpamAssassin::call_spamassassin(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amavis::In::Message=HASH(0x6e35920)’, ‘ARRAY(0x39a3ea0)’, undef) called at (eval 114) line 887\n\teval {…} called at (eval 114) line 896\n\tAmavis::SpamControl::SpamAssassin::check(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amavis::In::Message=HASH(0x6e35920)’) called at (eval 113) line 148\n\teval {…} called at (eval 113) line 149\n\tAmavis::SpamControl::spam_scan(‘Amavis::SpamControl=HASH(0x1a10328)’, ‘Amavis::In::Message=HASH(0x6e35[…]
Apr 17 10:50:41 mail amavis[4737]: (04737-02) (!)SA TIMED OUT, backtrace: at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/Message/Node.pm line 180.\n\teval {…} called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/Message/Node.pm line 180\n\tMail::SpamAssassin::Message::Node::header(‘Mail::SpamAssassin::Message=HASH(0x6e95520)’, ‘Date’, ‘ Fri, 17 Apr 2015 10:06:58 +0700 (WIB)\134x{a}’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/Message.pm line 253\n\tMail::SpamAssassin::Message::new(‘Mail::SpamAssassin::Message’, ‘HASH(0x6e9e0f0)’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin.pm line 548\n\tMail::SpamAssassin::parse(‘Mail::SpamAssassin=HASH(0x4c47a88)’, ‘SCALAR(0x3960fa8)’, 0, ‘HASH(0x398a710)’) called at (eval 114) line 720\n\teval {…} called at (eval 114) line 793\n\tAmavis::SpamControl::SpamAssassin::call_spamassassin(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amavis::In::Message=HASH(0x6e35920)’, ‘ARRAY(0x39a3[…]
Apr 17 10:50:45 mail amavis[4739]: (04739-02) (!)SA TIMED OUT, backtrace: at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 133.\n\teval {…} called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 133\n\tMail::SpamAssassin::PerMsgStatus::new(‘Mail::SpamAssassin::PerMsgStatus’, ‘Mail::SpamAssassin=HASH(0x4c47a88)’, ‘Mail::SpamAssassin::Message=HASH(0x6e954e0)’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin.pm line 583\n\tMail::SpamAssassin::check(‘Mail::SpamAssassin=HASH(0x4c47a88)’, ‘Mail::SpamAssassin::Message=HASH(0x6e954e0)’) called at (eval 114) line 736\n\teval {…} called at (eval 114) line 793\n\tAmavis::SpamControl::SpamAssassin::call_spamassassin(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amavis::In::Message=HASH(0x6e35920)’, ‘ARRAY(0x39a3ea0)’, undef) called at (eval 114) line 887\n\teval {…} called at (eval 114) line 896\n\tAmavis::SpamControl::SpamAssassin::check(‘Amavis::Sp[…]
Apr 17 10:50:47 mail amavis[4728]: (04728-03) SA info: check: exceeded time limit, skipping further tests
Apr 17 10:50:47 mail amavis[4739]: (04739-02) SA info: check: exceeded time limit in pms check
Apr 17 10:50:49 mail amavis[4732]: (04732-03) SA info: check: exceeded time limit, skipping further tests
Apr 17 10:50:58 mail amavis[4736]: (04736-02) (!)Requesting process rundown, task exceeded allowed time
Apr 17 10:50:58 mail amavis[4735]: (04735-02) (!)Requesting process rundown, task exceeded allowed time
Apr 17 10:51:02 mail amavis[4733]: (04733-03) SA info: check: exceeded time limit, skipping further tests
Apr 17 10:51:10 mail amavis[4735]: (04735-02) (!)TempDir removal: tempdir is to be PRESERVED: /opt/zimbra/data/amavisd/tmp/amavis-20150417T103437-04735-HCmw9qV3
Apr 17 10:51:14 mail amavis[4737]: (04737-02) SA info: check: exceeded time limit in pms check
Apr 17 10:51:15 mail amavis[4734]: (04734-02) SA info: check: exceeded time limit in pms check
Apr 17 10:51:20 mail amavis[4736]: (04736-02) (!)TempDir removal: tempdir is to be PRESERVED: /opt/zimbra/data/amavisd/tmp/amavis-20150417T103437-04736-hvFRy5rz
Apr 17 10:51:23 mail amavis[4731]: (04731-02) SA info: check: exceeded time limit, skipping further tests
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: no callback for id: 11359/sentrawatch.com.dob.sibl.support-intelligence.net/A/IN, ignored; packet: ;; Answer received from 192.168.5.1 (83 bytes)
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; HEADER SECTION
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; id = 11359
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; qr = 1 opcode = QUERY aa = 0 tc = 0 rd = 1
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; ra = 0 ad = 0 cd = 0 rcode = NOERROR
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; qdcount = 1 ancount = 1 nscount = 0 arcount = 0
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […]
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; QUESTION SECTION (1 record)
Apr 17 10:50:39 mail postfix/qmgr[5258]: warning: problem talking to service rewrite: Connection timed out
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; sentrawatch.com.dob.sibl.support-intelligence.net. IN A
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […]
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] ;; ANSWER SECTION (1 record)
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […] sentrawatch.com.dob.sibl.support-intelligence.net. 85253 IN A 118.98.96.151
Apr 17 10:51:30 mail amavis[4728]: (04728-03) SA info: dns: […]
Apr 17 10:51:38 mail amavis[4728]: (04728-03) SA info: dns: […] ;; AUTHORITY SECTION (0 records)
Apr 17 10:51:38 mail amavis[4728]: (04728-03) SA info: dns: […]
Apr 17 10:51:38 mail amavis[4728]: (04728-03) SA info: dns: […] ;; ADDITIONAL SECTION (0 records)
Apr 17 10:51:38 mail amavis[4729]: (04729-03) SA info: check: exceeded time limit, skipping further tests
Apr 17 10:51:38 mail amavis[4739]: (04739-02) (!)Auto-learn failed: timed out
Apr 17 10:51:46 mail amavis[4739]: (04739-02) (!!)TROUBLE in check_mail: decide_mail_destiny FAILED: timed out
Apr 17 10:51:48 mail postfix/qmgr[5258]: warning: problem talking to service rewrite: Connection timed out
Apr 17 10:52:12 mail amavis[4734]: (04734-02) (!)checking with spam scanner SpamAssassin failed: timed out
Apr 17 10:52:14 mail amavis[4739]: (04739-02) (!)Requesting process rundown, task exceeded allowed time
Apr 17 10:52:18 mail amavis[4734]: (04734-02) (!!)TROUBLE in check_mail: spam_scan FAILED: SpamAssassin failed: timed out at (eval 113) line 158.
Apr 17 10:52:18 mail amavis[4737]: (04737-02) (!!)TROUBLE in check_mail: decide_mail_destiny FAILED: timed out
Apr 17 10:52:23 mail amavis[4728]: (04728-03) (!)SA TIMED OUT, backtrace: at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1410.\n\teval {…} called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1410\n\tMail::SpamAssassin::PerMsgStatus::_get_tag(‘Mail::SpamAssassin::PerMsgStatus=HASH(0x22975d0)’, ‘TESTS’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1212\n\tMail::SpamAssassin::PerMsgStatus::get_tag(‘Mail::SpamAssassin::PerMsgStatus=HASH(0x22975d0)’, ‘TESTS’) called at (eval 114) line 755\n\teval {…} called at (eval 114) line 793\n\tAmavis::SpamControl::SpamAssassin::call_spamassassin(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amavis::In::Message=HASH(0x6746d18)’, ‘ARRAY(0x39a3ea0)’, undef) called at (eval 114) line 887\n\teval {…} called at (eval 114) line 896\n\tAmavis::SpamControl::SpamAssassin::check(‘Amavis::SpamControl::SpamAssassin=HASH(0x3c2c668)’, ‘Amav[…]
Apr 17 10:52:26 mail amavis[4732]: (04732-03) (!)SA TIMED OUT, backtrace: at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 725.\n\teval {…} called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 725\n\tMail::SpamAssassin::PerMsgStatus::_get_added_headers(‘Mail::SpamAssassin::PerMsgStatus=HASH(0x6e34e58)’, ‘headers_spam’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1401\n\tMail::SpamAssassin::PerMsgStatus::__ANON__() called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1413\n\tMail::SpamAssassin::PerMsgStatus::_get_tag(‘Mail::SpamAssassin::PerMsgStatus=HASH(0x6e34e58)’, ‘ADDEDHEADERSPAM’) called at /opt/zimbra/zimbramon/lib/Mail/SpamAssassin/PerMsgStatus.pm line 1212\n\tMail::SpamAssassin::PerMsgStatus::get_tag(‘Mail::SpamAssassin::PerMsgStatus=HASH(0x6e34e58)’, ‘ADDEDHEADERSPAM’) called at (eval 114) line 755\n\teval {…} called at (eval 114) line 793[…]
Apr 17 10:52:26 mail amavis[4739]: (04739-02) (!)TempDir removal: tempdir is to be PRESERVED: /opt/zimbra/data/amavisd/tmp/amavis-20150417T103437-04739-cx57xEWm
Apr 17 10:52:30 mail amavis[4737]: (04737-02) (!)Requesting process rundown, task exceeded allowed time
Apr 17 10:52:31 mail postfix/proxymap[8131]: error: dict_ldap_connect: Unable to set STARTTLS: -5: Timed out
Apr 17 10:52:31 mail postfix/trivial-rewrite[8100]: warning: proxy:ldap:/opt/zimbra/conf/ldap-transport.cf lookup error for “*”
Apr 17 10:52:41 mail amavis[4734]: (04734-02) (!)Requesting process rundown, task exceeded allowed time
Apr 17 10:52:49 mail amavis[4737]: (04737-02) (!)TempDir removal: tempdir is to be PRESERVED: /opt/zimbra/data/amavisd/tmp/amavis-20150417T103437-04737-CBQH7LqM
Apr 17 10:52:49 mail amavis[4734]: (04734-02) (!)TempDir removal: tempdir is to be PRESERVED: /opt/zimbra/data/amavisd/tmp/amavis-20150417T103437-04734-C3Og0kDt
Apr 17 10:52:58 mail amavis[4732]: (04732-03) (!!)TROUBLE in check_mail: spam_scan FAILED: timed out

port listen:

root@mail:~# lsof -i -n -P
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 1087 root 3r IPv4 8755 0t0 TCP *:60890 (LISTEN)
sshd 1087 root 4u IPv6 8776 0t0 TCP *:60890 (LISTEN)
sshd 1087 root 5u IPv4 8778 0t0 TCP *:22 (LISTEN)
sshd 1087 root 6u IPv6 8782 0t0 TCP *:22 (LISTEN)
named 1167 bind 20u IPv6 8941 0t0 TCP *:53 (LISTEN)
named 1167 bind 21u IPv4 8946 0t0 TCP 127.0.0.1:53 (LISTEN)
named 1167 bind 22u IPv4 8948 0t0 TCP 192.168.5.68:53 (LISTEN)
named 1167 bind 23u IPv4 8951 0t0 TCP 127.0.0.1:953 (LISTEN)
named 1167 bind 24u IPv6 8952 0t0 TCP [::1]:953 (LISTEN)
named 1167 bind 512u IPv6 8940 0t0 UDP *:53
named 1167 bind 513u IPv4 8945 0t0 UDP 127.0.0.1:53
named 1167 bind 514u IPv4 8947 0t0 UDP 192.168.5.68:53
sshd 1237 root 3r IPv4 9156 0t0 TCP 192.168.5.68:22->192.168.5.207:57491 (ESTABLISHED)
sshd 2168 root 3r IPv4 11067 0t0 TCP 192.168.5.68:22->192.168.5.207:57494 (ESTABLISHED)
slapd 2430 zimbra 7u IPv4 11417 0t0 TCP 192.168.5.68:389 (LISTEN)
slapd 2430 zimbra 10u IPv4 12282 0t0 TCP 192.168.5.68:389->192.168.5.68:35394 (ESTABLISHED)
slapd 2430 zimbra 12u IPv4 12284 0t0 TCP 192.168.5.68:389->192.168.5.68:35395 (ESTABLISHED)
slapd 2430 zimbra 13u IPv4 12287 0t0 TCP 192.168.5.68:389->192.168.5.68:35396 (ESTABLISHED)
slapd 2430 zimbra 15u IPv4 13970 0t0 TCP 192.168.5.68:389->192.168.5.68:35418 (ESTABLISHED)
slapd 2430 zimbra 16u IPv4 13974 0t0 TCP 192.168.5.68:389->192.168.5.68:35419 (ESTABLISHED)
slapd 2430 zimbra 17u IPv4 18727 0t0 TCP 192.168.5.68:389->192.168.5.68:35433 (ESTABLISHED)
slapd 2430 zimbra 18u IPv4 18775 0t0 TCP 192.168.5.68:389->192.168.5.68:35435 (ESTABLISHED)
slapd 2430 zimbra 19u IPv4 18802 0t0 TCP 192.168.5.68:389->192.168.5.68:35436 (ESTABLISHED)
slapd 2430 zimbra 20u IPv4 18963 0t0 TCP 192.168.5.68:389->192.168.5.68:35444 (ESTABLISHED)
slapd 2430 zimbra 21u IPv4 18964 0t0 TCP 192.168.5.68:389->192.168.5.68:35445 (ESTABLISHED)
slapd 2430 zimbra 22u IPv4 18965 0t0 TCP 192.168.5.68:389->192.168.5.68:35446 (ESTABLISHED)
slapd 2430 zimbra 23u IPv4 18966 0t0 TCP 192.168.5.68:389->192.168.5.68:35447 (ESTABLISHED)
slapd 2430 zimbra 24u IPv4 18967 0t0 TCP 192.168.5.68:389->192.168.5.68:35448 (ESTABLISHED)
java 2551 zimbra 109u IPv4 12276 0t0 UDP *:47454
java 2551 zimbra 114u IPv4 12281 0t0 TCP 192.168.5.68:35394->192.168.5.68:389 (ESTABLISHED)
java 2551 zimbra 115u IPv4 12283 0t0 TCP 192.168.5.68:35395->192.168.5.68:389 (ESTABLISHED)
java 2551 zimbra 117u IPv4 12665 0t0 TCP 127.0.0.1:7171 (LISTEN)
java 2551 zimbra 118u IPv4 12286 0t0 TCP 192.168.5.68:35396->192.168.5.68:389 (ESTABLISHED)
java 2551 zimbra 121u IPv4 19574 0t0 TCP 127.0.0.1:7171->127.0.0.1:36425 (CLOSE_WAIT)
mysqld 3772 zimbra 26u IPv4 13219 0t0 TCP 127.0.0.1:7306 (LISTEN)
mysqld 3772 zimbra 47u IPv4 13968 0t0 TCP 127.0.0.1:7306->127.0.0.1:60468 (ESTABLISHED)
zmlogger: 3785 zimbra 3u IPv4 13204 0t0 TCP 127.0.0.1:10663 (LISTEN)
java 3850 zimbra 87u IPv4 13758 0t0 TCP *:7110 (LISTEN)
java 3850 zimbra 89u IPv4 13761 0t0 TCP *:7995 (LISTEN)
java 3850 zimbra 90u IPv4 13762 0t0 TCP *:7143 (LISTEN)
java 3850 zimbra 91u IPv4 13763 0t0 TCP *:7993 (LISTEN)
java 3850 zimbra 92u IPv4 13764 0t0 TCP *:7025 (LISTEN)
java 3850 zimbra 94u IPv4 13803 0t0 TCP 127.0.0.1:80 (LISTEN)
java 3850 zimbra 95u IPv4 13806 0t0 TCP *:443 (LISTEN)
java 3850 zimbra 96u IPv4 13807 0t0 TCP *:7071 (LISTEN)
java 3850 zimbra 97u IPv4 13808 0t0 TCP *:7072 (LISTEN)
java 3850 zimbra 132u IPv4 16138 0t0 UDP *:41255
java 3850 zimbra 136u IPv4 13967 0t0 TCP 127.0.0.1:60468->127.0.0.1:7306 (ESTABLISHED)
java 3850 zimbra 137u IPv4 13969 0t0 TCP 192.168.5.68:35418->192.168.5.68:389 (ESTABLISHED)
java 3850 zimbra 138u IPv4 13973 0t0 TCP 192.168.5.68:35419->192.168.5.68:389 (ESTABLISHED)
memcached 3858 zimbra 26u IPv4 13332 0t0 TCP *:11211 (LISTEN)
memcached 3858 zimbra 27u IPv6 13333 0t0 TCP *:11211 (LISTEN)
memcached 3858 zimbra 28u IPv4 13337 0t0 UDP *:11211
memcached 3858 zimbra 29u IPv6 13338 0t0 UDP *:11211
memcached 3858 zimbra 30u IPv4 13395 0t0 TCP 192.168.5.68:11211->192.168.5.68:34621 (ESTABLISHED)
memcached 3858 zimbra 31u IPv4 13397 0t0 TCP 192.168.5.68:11211->192.168.5.68:34622 (ESTABLISHED)
memcached 3858 zimbra 32u IPv4 13399 0t0 TCP 192.168.5.68:11211->192.168.5.68:34623 (ESTABLISHED)
memcached 3858 zimbra 33u IPv4 13401 0t0 TCP 192.168.5.68:11211->192.168.5.68:34624 (ESTABLISHED)
nginx 3885 zimbra 5u IPv4 13376 0t0 TCP *:143 (LISTEN)
nginx 3885 zimbra 6u IPv4 13377 0t0 TCP *:993 (LISTEN)
nginx 3885 zimbra 7u IPv4 13378 0t0 TCP *:110 (LISTEN)
nginx 3885 zimbra 8u IPv4 13379 0t0 TCP *:995 (LISTEN)
nginx 3887 zimbra 5u IPv4 13376 0t0 TCP *:143 (LISTEN)
nginx 3887 zimbra 6u IPv4 13377 0t0 TCP *:993 (LISTEN)
nginx 3887 zimbra 7u IPv4 13378 0t0 TCP *:110 (LISTEN)
nginx 3887 zimbra 8u IPv4 13379 0t0 TCP *:995 (LISTEN)
nginx 3887 zimbra 11u IPv4 13398 0t0 TCP 192.168.5.68:34623->192.168.5.68:11211 (ESTABLISHED)
nginx 3888 zimbra 5u IPv4 13376 0t0 TCP *:143 (LISTEN)
nginx 3888 zimbra 6u IPv4 13377 0t0 TCP *:993 (LISTEN)
nginx 3888 zimbra 7u IPv4 13378 0t0 TCP *:110 (LISTEN)
nginx 3888 zimbra 8u IPv4 13379 0t0 TCP *:995 (LISTEN)
nginx 3888 zimbra 13u IPv4 13394 0t0 TCP 192.168.5.68:34621->192.168.5.68:11211 (ESTABLISHED)
nginx 3889 zimbra 5u IPv4 13376 0t0 TCP *:143 (LISTEN)
nginx 3889 zimbra 6u IPv4 13377 0t0 TCP *:993 (LISTEN)
nginx 3889 zimbra 7u IPv4 13378 0t0 TCP *:110 (LISTEN)
nginx 3889 zimbra 8u IPv4 13379 0t0 TCP *:995 (LISTEN)
nginx 3889 zimbra 15u IPv4 13400 0t0 TCP 192.168.5.68:34624->192.168.5.68:11211 (ESTABLISHED)
nginx 3890 zimbra 5u IPv4 13376 0t0 TCP *:143 (LISTEN)
nginx 3890 zimbra 6u IPv4 13377 0t0 TCP *:993 (LISTEN)
nginx 3890 zimbra 7u IPv4 13378 0t0 TCP *:110 (LISTEN)
nginx 3890 zimbra 8u IPv4 13379 0t0 TCP *:995 (LISTEN)
nginx 3890 zimbra 17u IPv4 13396 0t0 TCP 192.168.5.68:34622->192.168.5.68:11211 (ESTABLISHED)
/opt/zimb 4001 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4001 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4117 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4117 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4117 zimbra 9u IPv4 18733 0t0 TCP 127.0.0.1:10024->127.0.0.1:58186 (ESTABLISHED)
/opt/zimb 4117 zimbra 11u IPv4 18950 0t0 TCP 192.168.5.68:35446->192.168.5.68:389 (ESTABLISHED)
/opt/zimb 4117 zimbra 12u IPv4 20452 0t0 UDP 192.168.5.68:14285->192.168.5.1:53
/opt/zimb 4118 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4118 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4118 zimbra 9u IPv4 18736 0t0 TCP 127.0.0.1:10024->127.0.0.1:58187 (ESTABLISHED)
/opt/zimb 4118 zimbra 11u IPv4 18951 0t0 TCP 192.168.5.68:35448->192.168.5.68:389 (ESTABLISHED)
/opt/zimb 4118 zimbra 12u IPv4 20451 0t0 UDP 192.168.5.68:35868->192.168.5.1:53
/opt/zimb 4119 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4119 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4119 zimbra 9u IPv4 18737 0t0 TCP 127.0.0.1:10024->127.0.0.1:58188 (ESTABLISHED)
/opt/zimb 4119 zimbra 11u IPv4 18948 0t0 TCP 192.168.5.68:35447->192.168.5.68:389 (ESTABLISHED)
/opt/zimb 4119 zimbra 12u IPv4 20455 0t0 UDP 192.168.5.68:20119->192.168.5.1:53
/opt/zimb 4120 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4120 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4120 zimbra 9u IPv4 18738 0t0 TCP 127.0.0.1:10024->127.0.0.1:58189 (ESTABLISHED)
/opt/zimb 4120 zimbra 11u IPv4 18947 0t0 TCP 192.168.5.68:35444->192.168.5.68:389 (ESTABLISHED)
/opt/zimb 4120 zimbra 12u IPv4 20453 0t0 UDP 192.168.5.68:31970->192.168.5.1:53
/opt/zimb 4121 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4121 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4121 zimbra 9u IPv4 18741 0t0 TCP 127.0.0.1:10024->127.0.0.1:58191 (ESTABLISHED)
/opt/zimb 4121 zimbra 11u IPv4 18949 0t0 TCP 192.168.5.68:35445->192.168.5.68:389 (ESTABLISHED)
/opt/zimb 4121 zimbra 12u IPv4 20454 0t0 UDP 192.168.5.68:46617->192.168.5.1:53
/opt/zimb 4122 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4122 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4123 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4123 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4124 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4124 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4125 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4125 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
/opt/zimb 4126 zimbra 6u IPv4 13880 0t0 TCP 127.0.0.1:10024 (LISTEN)
/opt/zimb 4126 zimbra 7u IPv4 13881 0t0 TCP 127.0.0.1:10026 (LISTEN)
httpd 4337 zimbra 3u IPv4 16188 0t0 TCP *:7780 (LISTEN)
httpd 4340 zimbra 3u IPv4 16188 0t0 TCP *:7780 (LISTEN)
httpd 4341 zimbra 3u IPv4 16188 0t0 TCP *:7780 (LISTEN)
httpd 4342 zimbra 3u IPv4 16188 0t0 TCP *:7780 (LISTEN)
master 4621 root 13u IPv4 18519 0t0 TCP *:25 (LISTEN)
master 4621 root 17u IPv4 18522 0t0 TCP *:465 (LISTEN)
master 4621 root 20u IPv4 18525 0t0 TCP *:587 (LISTEN)
master 4621 root 113u IPv4 18617 0t0 TCP 127.0.0.1:10025 (LISTEN)
master 4621 root 116u IPv4 18621 0t0 TCP 127.0.0.1:10029 (LISTEN)
smtp 4629 postfix 14u IPv4 18678 0t0 TCP 127.0.0.1:58186->127.0.0.1:10024 (ESTABLISHED)
smtp 4630 postfix 14u IPv4 18679 0t0 TCP 127.0.0.1:58187->127.0.0.1:10024 (ESTABLISHED)
smtp 4631 postfix 14u IPv4 18690 0t0 TCP 127.0.0.1:58188->127.0.0.1:10024 (ESTABLISHED)
smtp 4632 postfix 14u IPv4 18691 0t0 TCP 127.0.0.1:58189->127.0.0.1:10024 (ESTABLISHED)
smtp 4633 postfix 14u IPv4 18740 0t0 TCP 127.0.0.1:58191->127.0.0.1:10024 (ESTABLISHED)
proxymap 4635 postfix 11u IPv4 18723 0t0 TCP 192.168.5.68:35433->192.168.5.68:389 (ESTABLISHED)
opendkim 4652 zimbra 4u IPv4 18774 0t0 TCP 192.168.5.68:35435->192.168.5.68:389 (ESTABLISHED)
opendkim 4652 zimbra 5u IPv4 18801 0t0 TCP 192.168.5.68:35436->192.168.5.68:389 (ESTABLISHED)
opendkim 4653 zimbra 3u IPv4 18805 0t0 TCP 127.0.0.1:8465 (LISTEN)
opendkim 4653 zimbra 4u IPv4 18774 0t0 TCP 192.168.5.68:35435->192.168.5.68:389 (ESTABLISHED)
opendkim 4653 zimbra 5u IPv4 18801 0t0 TCP 192.168.5.68:35436->192.168.5.68:389 (ESTABLISHED)
nc 5248 zimbra 3u IPv4 20877 0t0 TCP 127.0.0.1:36425->127.0.0.1:7171 (FIN_WAIT2)

Mohon bantuannya ya Pak

Terima kasih

Hendro


Fitrandi Rahayu
November 12, 2017 at 7:28 pm

Terimakasih Om 😀
Akhirnya tugas sekolah saya jadi 😀 hehehe





Leave a Reply

Your email address will not be published. Required fields are marked *

CAPTCHA

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.