• Masim “Vavai” Sugianto

    Founder PT. Excellent Infotama Kreasindo– perusahaan email services provider (ESP) dan menjadi konsultan pada berbagai instansi pemerintah, korporasi besar, lembaga perbankan dan institusi pendidikan di Indonesia.

    Lebih detail tentang Vavai.




  • Publishing

  • Recent Posts

    • TOEFL ITP Score (Kedua)
    • Bisnis Kelapa Muda
    • Model Usaha
    • Back-End Developer, Front-End Developer & Staff IT Support
    • Markas Excellent Danita
  • Recent Comments

    • medicine-online.estranky.skclankyunderstand-covid-19-and-know-the-tricks-to-avoid-it-from-spreading-----medical-services.html on Instalasi Squid Proxy Server pada OpenSUSE
    • asebg.bigcartel.comcanadian-pharmacy on Instalasi Squid Proxy Server pada OpenSUSE
    • dkyubn.bizwebs.com on Instalasi Squid Proxy Server pada OpenSUSE
    • http://aonubs.website2.me/ on Instalasi Squid Proxy Server pada OpenSUSE
    • canadian pharmacy online on Instalasi Squid Proxy Server pada OpenSUSE
  • Archives

    • April 2022
    • January 2022
    • July 2021
    • June 2021
    • February 2021
    • January 2021
    • December 2020
    • August 2020
    • July 2020
    • April 2020
    • March 2020
    • August 2019
    • July 2019
    • June 2019
    • March 2019
    • February 2019
    • January 2019
    • November 2018
    • October 2018
    • August 2018
    • May 2018
    • April 2018
    • January 2018
    • December 2017
    • July 2017
    • December 2016
    • November 2016
    • April 2016
    • March 2016
    • November 2015
    • July 2015
    • April 2015
    • November 2014
    • October 2014
    • February 2014
    • January 2014
    • December 2013
    • November 2013
    • October 2013
    • September 2013
    • August 2013
    • June 2013
    • May 2013
    • March 2013
    • February 2013
    • January 2013
    • December 2012
    • November 2012
    • October 2012
    • September 2012
    • August 2012
    • July 2012
    • June 2012
    • May 2012
    • April 2012
    • March 2012
    • February 2012
    • January 2012
    • December 2011
    • November 2011
    • October 2011
    • September 2011
    • August 2011
    • July 2011
    • June 2011
    • May 2011
    • April 2011
    • March 2011
    • February 2011
    • January 2011
    • December 2010
    • November 2010
    • October 2010
    • September 2010
    • August 2010
    • July 2010
    • June 2010
    • May 2010
    • April 2010
    • March 2010
    • February 2010
    • January 2010
    • October 2008
    • September 2008
    • August 2008
    • July 2008
    • June 2008
    • May 2008
    • April 2008
    • March 2008
    • February 2008
    • January 2008
    • December 2007
    • November 2007
    • October 2007
    • September 2007
    • August 2007
    • July 2007
    • June 2007
    • May 2007
    • April 2007
    • March 2007
  • Home
  • Bisnis & Marketing
  • Computer & IT Related
  • Lifestyle
  • Publishing
  • Free Stuff
  • About
  • Kontak

Solusi Untuk Masalah Logger pada Zimbra 6.0.6 & SLES 10

May 2, 2010

Project pribadi saya saat ini adalah membuat Zimbra Appliance baik versi 32 bit maupun 64 bit berbasis SLES/openSUSE.

Zimbra 6.0.6 tersedia untuk SUSE Linux Enterprise 11 dan dapat digunakan pada openSUSE 11.x namun binary yang tersedia adalah versi 64 bit, sesuai rencana dari Zimbra mendorong penggunaan server-server 64 bit untuk menjalankan Zimbra. Meski demikian, karena sebagian besar pengguna komputer di Indonesia menggunakan mesin-mesin 32 bit, saya membuat Zimbra Appliance berbasis SLES 10 32 bit.

Proses instalasi berjalan lancar namun ada masalah pada Zimbra status dan logger problem. Service Zimbra semuanya running seperti terlihat pada screenshot berikut :

Namun jika membuka Zimbra Admin | Server Status atau Statistics, keluar pesan error sebagai berikut :

zmsoap -z GetLoggerStatsRequest stats/@name=zmmtastats | head -20 ERROR: service.FAILURE (system failure: Unable to read logger stats)

Masalah ini tidak terjadi pada Zimbra 6.0.6 yang berjalan pada SUSE Linux Enterprise 11. Setelah diskusi di forum openSUSE dan cari-cari dokumentasi di Zimbra forum, berikut adalah solusinya :

  1. Pastikan zmlogger stop. Jalankan perintah berikut :
    su - zimbra
    zmloggerctl stop
    ps ax | grep zmlogger
    

    Kalau masih ada zmlogger yang berjalan, lihat PID number dan stop dengan hak akses root (exit dari posisi Zimbra user) :
    kill -9 PIDNumber atau killall zmlogger

  2. Buat ulang file  database sqlite secara manual. Menggunakan hak akses root jalankan perintah berikut :
    rm -rf /opt/zimbra/logger/db/*
    /opt/zimbra/libexec/zmfixperms
    

    Kemudian berikan perintah :

    su - zimbra
    /opt/zimbra/libexec/zmlogger&
    
  3. Non aktifkan lagi zmlogger karena kita akan memodifikasi file syslog :
    zmloggerctl stop
    ps ax | grep zmlogger
    

    Kalau masih ada service yang running, stop dengan perintah kill -9 PIDNumber atau killall zmlogger

  4. Perbaiki file /etc/syslog-ng/syslog-ng.conf dengan perintah berikut (hak akses root) :
    service syslog stop
    mv /etc/syslog-ng/syslog-ng.conf /etc/syslog-ng/syslog-ng-backup.conf
    vi /etc/syslog-ng/syslog-ng.conf
    

    Kemudian paste kode berikut ini :

    #
    # /etc/syslog-ng/syslog-ng.conf
    #
    # Automatically generated by SuSEconfig on Sat May  1 17:40:24 UTC 2010.
    #
    # PLEASE DO NOT EDIT THIS FILE!
    #
    # you can modify /etc/syslog-ng/syslog-ng.conf.in instead
    #
    #
    #
    # File format description can be found in syslog-ng.conf(5)
    # and /usr/share/doc/packages/syslog-ng/syslog-ng.txt.
    #
    
    #
    # Global options.
    #
    options { long_hostnames(off); sync(0); perm(0640); stats(3600); };
    
    #
    # 'src' is our main source definition. you can add
    # more sources driver definitions to it, or define
    # your own sources, i.e.:
    #
    #source my_src { .... };
    #
    source src {
    #
    # include internal syslog-ng messages
    # note: the internal() soure is required!
    #
    internal();
    
    #
    # the following line will be replaced by the
    # socket list generated by SuSEconfig using
    # variables from /etc/sysconfig/syslog:
    #
    unix-dgram("/dev/log");
    unix-dgram("/var/lib/named/dev/log");
    
    #
    # uncomment to process log messages from network:
    #
    #udp(ip("0.0.0.0") port(514));
    };
    
    #
    # Filter definitions
    #
    filter f_iptables   { facility(kern) and match("IN=") and match("OUT="); };
    
    filter f_console    { level(warn) and facility(kern) and not filter(f_iptables)
    or level(err) and not facility(authpriv); };
    
    filter f_newsnotice { level(notice) and facility(news); };
    filter f_newscrit   { level(crit)   and facility(news); };
    filter f_newserr    { level(err)    and facility(news); };
    filter f_news       { facility(news); };
    
    filter f_mailinfo   { level(info)      and facility(mail); };
    filter f_mailwarn   { level(warn)      and facility(mail); };
    filter f_mailerr    { level(err, crit) and facility(mail); };
    filter f_mail       { facility(mail); };
    
    filter f_cron       { facility(cron); };
    
    filter f_local      { facility(local0, local1, local2, local3,
    local4, local5, local6, local7); };
    
    filter f_acpid      { match('^\[acpid\]:'); };
    filter f_netmgm     { match('^NetworkManager:'); };
    
    filter f_messages   { not facility(news, mail) and not filter(f_iptables); };
    filter f_warn       { level(warn, err, crit) and not filter(f_iptables); };
    filter f_alert      { level(alert); };
    
    #
    # Most warning and errors on tty10 and on the xconsole pipe:
    #
    destination console  { pipe("/dev/tty10"    group(tty) perm(0620)); };
    log { source(src); filter(f_console); destination(console); };
    
    destination xconsole { pipe("/dev/xconsole" group(tty) perm(0400)); };
    log { source(src); filter(f_console); destination(xconsole); };
    
    # Enable this, if you want that root is informed immediately,
    # e.g. of logins:
    #
    #destination root { usertty("root"); };
    #log { source(src); filter(f_alert); destination(root); };
    
    #
    # News-messages in separate files:
    #
    destination newscrit   { file("/var/log/news/news.crit"
    owner(news) group(news)); };
    log { source(src); filter(f_newscrit); destination(newscrit); };
    
    destination newserr    { file("/var/log/news/news.err"
    owner(news) group(news)); };
    log { source(src); filter(f_newserr); destination(newserr); };
    
    destination newsnotice { file("/var/log/news/news.notice"
    owner(news) group(news)); };
    log { source(src); filter(f_newsnotice); destination(newsnotice); };
    
    #
    # and optionally also all in one file:
    # (don't forget to provide logrotation config)
    #
    #destination news { file("/var/log/news.all"); };
    #log { source(src); filter(f_news); destination(news); };
    
    #
    # Mail-messages in separate files:
    #
    #destination mailinfo { file("/var/log/mail.info"); };
    #log { source(src); filter(f_mailinfo); destination(mailinfo); };
    
    #destination mailwarn { file("/var/log/mail.warn"); };
    #log { source(src); filter(f_mailwarn); destination(mailwarn); };
    
    #destination mailerr  { file("/var/log/mail.err" fsync(yes)); };
    #log { source(src); filter(f_mailerr);  destination(mailerr); };
    
    #
    # and also all in one file:
    #
    #destination mail { file("/var/log/mail"); };
    #log { source(src); filter(f_mail); destination(mail); };
    
    #
    # acpid messages in one file:
    #
    destination acpid { file("/var/log/acpid"); };
    log { source(src); filter(f_acpid); destination(acpid); flags(final); };
    
    #
    # NetworkManager messages in one file:
    #
    destination netmgm { file("/var/log/NetworkManager"); };
    log { source(src); filter(f_netmgm); destination(netmgm); flags(final); };
    
    #
    # Cron-messages in one file:
    # (don't forget to provide logrotation config)
    #
    #destination cron { file("/var/log/cron"); };
    #log { source(src); filter(f_cron); destination(cron); };
    
    #
    # Some boot scripts use/require local[1-7]:
    #
    destination localmessages { file("/var/log/localmessages"); };
    log { source(src); filter(f_local); destination(localmessages); };
    
    #
    # All messages except iptables and the facilities news and mail:
    #
    destination messages { file("/var/log/messages"); };
    log { source(src); filter(f_messages); destination(messages); };
    
    #
    # Firewall (iptables) messages in one file:
    #
    destination firewall { file("/var/log/firewall"); };
    log { source(src); filter(f_iptables); destination(firewall); };
    
    #
    # Warnings (except iptables) in one file:
    #
    destination warn { file("/var/log/warn" fsync(yes)); };
    log { source(src); filter(f_warn); destination(warn); };
    
    #
    # Enable this, if you want to keep all messages in one file:
    # (don't forget to provide logrotation config)
    #
    #destination allmessages { file("/var/log/allmessages"); };
    #log { source(src); destination(allmessages); };
    
    #filter f_local0 { facility(local0); }; # zimbra
    #destination zmail { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    #log { source(src); filter(f_mail); destination(zmail); }; # zimbra
    #destination local0 { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    #log { source(src); filter(f_local0); destination(local0); }; # zimbra
    #filter f_auth { facility(auth); }; # zimbra
    #destination zmauth { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    #log { source(src); filter(f_auth); destination(zmauth); }; # zimbra
    
    filter f_local0 { facility(local0); }; # zimbra
    filter f_local1 { facility(local1); }; # zimbra
    destination zmail { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    destination zmstats { file("/var/log/zimbra-stats.log" owner("zimbra") ); }; # zimbra
    log { source(src); filter(f_mail); destination(zmail); }; # zimbra
    destination local0 { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    log { source(src); filter(f_local0); destination(local0); }; # zimbra
    log { source(src); filter(f_local1); destination(zmstats); }; # zimbra
    filter f_auth { facility(auth); }; # zimbra
    destination zmauth { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
    log { source(src); filter(f_auth); destination(zmauth); }; # zimbra
    

    Kemudian simpan dengan menekan tombol ESC, :wq. Teruskan dengan mengaktifkan syslog kembali dengan perintah : service syslog start.

    Jika anda terhubung ke internet, cara berikut lebih sederhana :

    service syslog stop
    mv /etc/syslog-ng/syslog-ng.conf /etc/syslog-ng/syslog-ng-backup.conf
    cd /etc/syslog-ng/
    wget -c https://www.vavai.com/wp-content/uploads/syslog-ng-sles10-ok.conf
    mv syslog-ng-sles10-ok.conf syslog-ng.conf
    service syslog start
    
  5. Restart service Zimbra dnegan perintah :
    zmcontrol stop
    zmcontrol start
    

Error logger mestinya sudah tidak ada. Untuk service status, biasanya butuh waktu beberapa saat sehingga tanda silang status pada Zimbra Admin berubah. Jika statistics Zimbra Admin tidak menimbulkan error saat diklik, mestinya masalahnya sudah OK.

LoggeropenSUSE & SLESplanet-terasi-aggregatorSLESZimbra
Share

Migrasi Server  / openSUSE & SLES  / Tips, Tricks & Tutorial

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

Webinar Zimbra : Mindset untuk Team IT
July 29, 2020
Eskalasi Masalah Email : mailbox unavailable invalid DNS MX or A/AAAA resource record
July 14, 2020
Two Factor Authentication (2FA/TFA) untuk Meningkatkan Keamanan Akses Email
April 24, 2020

5 Comments


Steven Ratel
May 24, 2010 at 5:43 am

Awesome advice here! I plan to come back later!



Amkbar
November 4, 2011 at 11:05 am

Terima Kasih Pak Vavai, beberapa waktu yang lalu saya mendapat pesan error seperti pada Postingan ini, saat ini sudah Solved dengan mengikuti perintah-perintah pada postingan ini. Terima kasih



Marine Boiler
October 15, 2018 at 10:47 pm

thank you very much for the information



Boiler Kapal
October 15, 2018 at 10:50 pm

terimakasih banyak informasinya pak Vavai



Fire Tube Steam Boiler
October 15, 2018 at 10:52 pm

info artikelnya semoga berman faat terimakasih P Vavai



Leave a Reply

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

CAPTCHA
Refresh

*

  • Artikel



  • Blogroll

    • DNS Propagation Checker
    • Instagram Photo/Video Downloader
    • PT. Excellent Infotama Kreasindo
  • Publishing

  • Recent Posts

    • TOEFL ITP Score (Kedua)
    • Bisnis Kelapa Muda
    • Model Usaha
    • Back-End Developer, Front-End Developer & Staff IT Support
    • Markas Excellent Danita
    • Pekerjaan Excellent
    • iMac 2021
    • Problem Solving
    • Kolam Mina Padi/Mina Genjer
    • Team Excellent


  • Links Ads

  • Recent Post

    • TOEFL ITP Score (Kedua)
    • Bisnis Kelapa Muda
    • Model Usaha
    • Back-End Developer, Front-End Developer & Staff IT Support
    • Markas Excellent Danita
    • Pekerjaan Excellent
    • iMac 2021
    • Problem Solving
    • Kolam Mina Padi/Mina Genjer
    • Team Excellent
    • Telur Bebek Mentah
    • Kursi Kayu dan Gerobak Angkringan
    • Kebun Pisang Barangan dan Ambon Kuning
    • Ternak Bebek
    • Data Statistik Covid dan Edukasi Media
  • Recent Comments

    • medicine-online.estranky.skclankyunderstand-covid-19-and-know-the-tricks-to-avoid-it-from-spreading-----medical-services.html on Instalasi Squid Proxy Server pada OpenSUSE
    • asebg.bigcartel.comcanadian-pharmacy on Instalasi Squid Proxy Server pada OpenSUSE
    • dkyubn.bizwebs.com on Instalasi Squid Proxy Server pada OpenSUSE
    • http://aonubs.website2.me/ on Instalasi Squid Proxy Server pada OpenSUSE
    • canadian pharmacy online on Instalasi Squid Proxy Server pada OpenSUSE
    • site592154748.fo.team on Instalasi Squid Proxy Server pada OpenSUSE
    • kqwsh.wordpress.com20220516what-everybody-else-does-when-it-comes-to-online-pharmacies on Instalasi Squid Proxy Server pada OpenSUSE
    • canadian rx on Instalasi Squid Proxy Server pada OpenSUSE
    • kwersd.mystrikingly.com on Instalasi Squid Proxy Server pada OpenSUSE
    • canadian prescriptions online on Instalasi Squid Proxy Server pada OpenSUSE