Ask questions about your setup or get help installing ZCS server (ZD section below).
fbzimblet
Advanced member
Posts: 119 Joined: Sun Apr 17, 2016 4:15 pm
Post
by fbzimblet » Tue Mar 28, 2017 5:18 am
below are CRITICAL messages that keeps repeating in zmconfigd.log
Code: Select all
[zimbra@mta2 ~]$ grep "2017-03-28" log/zmconfigd.log | grep CRITICAL | uniq
2017-03-28 13:11:50,967 zmconfigd CRITICAL [21680-MainThread] zmconfigd started on mta2.domain.my with loglevel=3 pid=21680
2017-03-28 13:12:55,907 zmconfigd CRITICAL [21680-MainThread] Tracking service antispam
2017-03-28 13:12:55,927 zmconfigd CRITICAL [21680-MainThread] Tracking service imapproxy
2017-03-28 13:12:55,940 zmconfigd CRITICAL [21680-MainThread] Tracking service ldap
2017-03-28 13:12:55,956 zmconfigd CRITICAL [21680-MainThread] Tracking service memcached
2017-03-28 13:12:56,365 zmconfigd CRITICAL [21680-MainThread] Tracking service mta
2017-03-28 13:12:56,380 zmconfigd CRITICAL [21680-MainThread] Tracking service sasl
2017-03-28 13:12:56,395 zmconfigd CRITICAL [21680-MainThread] Tracking service snmp
2017-03-28 13:12:56,753 zmconfigd CRITICAL [21680-MainThread] Tracking service stats
I tried "zmauthupdatekeys" as zimbra and "zmfixperms -v -e" as root. but did not fix this issue.
Where should I lookt to next?
fbzimblet
Advanced member
Posts: 119 Joined: Sun Apr 17, 2016 4:15 pm
Post
by fbzimblet » Tue Mar 28, 2017 6:57 am
I also tried commenting and deleting IPv6 line in /etc/hosts, and restart zimbra services but it still failed to start
#::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
DualBoot
Elite member
Posts: 1326 Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:
Post
by DualBoot » Tue Mar 28, 2017 9:45 am
Hello,
grep only pattern CRITICAL let you miss some clues, in my own opinion.
Regards,
fbzimblet
Advanced member
Posts: 119 Joined: Sun Apr 17, 2016 4:15 pm
Post
by fbzimblet » Wed Mar 29, 2017 4:01 am
when I ran zmcontrol stop and check for remaining zimbra processes, it seemed that zmconfigd is running
Code: Select all
$ ps -ef | grep zimbra
root 8626 8527 0 18:21 tty1 00:00:00 su - zimbra
zimbra 8627 8626 0 18:21 tty1 00:00:00 -bash
zimbra 11028 1 48 19:59 ? 00:00:26 /opt/zimbra/java/bin/java -XX:ErrorFile=/opt/zimbra/log -client -Xmx256m -Dzimbra.home=/opt/zimbra -Djava.library.path=/opt/zimbra/lib -Djava.ext.dirs=/opt/zimbra/java/jre/lib/ext:/opt/zimbra/lib/jars:/opt/zimbra/lib/ext-common -Djava.io.tmpdir=/opt/zimbra/data/tmp -Dpython.cachedir=/opt/zimbra/data/tmp/jython-cachedir org.python.util.jython /opt/zimbra/libexec/zmconfigd
root 11455 4832 0 20:00 pts/0 00:00:00 su - zimbra
zimbra 11456 11455 0 20:00 pts/0 00:00:00 -bash
zimbra 12573 11456 0 20:00 pts/0 00:00:00 ps -ef
zimbra 12574 11456 0 20:00 pts/0 00:00:00 grep zimbra
Then, I tried manually restarting zmconfigd, it said failed but zmconfigdctl success. I'm not sure what that means
Code: Select all
$ zmconfigdctl restart
Stopping zmconfigdctl...success
Stopping zmconfigd...zmconfigd is not running.
Starting zmconfigd...failed.
Starting zmconfigdctl...success
fbzimblet
Advanced member
Posts: 119 Joined: Sun Apr 17, 2016 4:15 pm
Post
by fbzimblet » Wed Mar 29, 2017 4:26 am
I also tried killing that process and when I start it again, it still fail to start
Code: Select all
]$ zmconfigdctl start
Starting zmconfigd.../opt/zimbra/bin/zmconfigdctl: line 109: kill: (27870) - No such process
failed.
Starting zmconfigdctl...success
$ zmconfigdctl status
zmconfigd is not running.
I also found that second mta and second mailbox have certificate issues
Code: Select all
[root@mail2 ~]# /opt/zimbra/bin/zmcertmgr viewdeployedcrt
::service mta::
XXXXX ERROR: /opt/zimbra/conf/smtpd.crt does not exist
::service proxy::
XXXXX ERROR: /opt/zimbra/conf/nginx.crt does not exist
::service mailboxd::
XXXXX ERROR: failed to export /opt/zimbra/mailboxd/etc/mailboxd.pem from keystore.
keytool error: java.lang.Exception: Keystore file does not exist: /opt/zimbra/mailboxd/etc/keystore
XXXXX ERROR: /opt/zimbra/mailboxd/etc/mailboxd.pem does not exist
::service ldap::
XXXXX ERROR: /op[root@mta2 ~]# /opt/zimbra/bin/zmcertmgr viewdeployedcrt
::service mta::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=
::service proxy::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=
::service mailboxd::
XXXXX ERROR: failed to export /opt/zimbra/mailboxd/etc/mailboxd.pem from keystore.
keytool error: java.lang.RuntimeException: Usage error, /opt/zimbra/conf/keystore is not a legal command
XXXXX ERROR: /opt/zimbra/mailboxd/etc/mailboxd.pem does not exist
::service ldap::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=t/zimbra/conf/slapd.crt does not exist
[root@mta2 ~]# /opt/zimbra/bin/zmcertmgr viewdeployedcrt
::service mta::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=
::service proxy::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=
::service mailboxd::
XXXXX ERROR: failed to export /opt/zimbra/mailboxd/etc/mailboxd.pem from keystore.
keytool error: java.lang.RuntimeException: Usage error, /opt/zimbra/conf/keystore is not a legal command
XXXXX ERROR: /opt/zimbra/mailboxd/etc/mailboxd.pem does not exist
::service ldap::
notBefore=Apr 14 05:57:48 2013 GMT
notAfter=Apr 12 05:57:48 2023 GMT
subject= /C=US/ST=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mta2.domain.my
issuer= /C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=mail1.domain.my
SubjectAltName=
DualBoot
Elite member
Posts: 1326 Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:
Post
by DualBoot » Wed Mar 29, 2017 7:24 am
What is the version of your current running Zimbra ?
fbzimblet
Advanced member
Posts: 119 Joined: Sun Apr 17, 2016 4:15 pm
Post
by fbzimblet » Wed Mar 29, 2017 7:29 am
it is ZCS NE 7.1.4
DualBoot
Elite member
Posts: 1326 Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:
Post
by DualBoot » Wed Mar 29, 2017 7:34 am
For the mailstore, ath this point, I will try to regenerate the self signed certificate et redeploy it.