Results 1 to 9 of 9

Thread: Zimbra server is not accessible

  1. #1
    tezarin is offline Senior Member
    Join Date
    Dec 2008
    Posts
    61
    Rep Power
    6

    Default Zimbra server is not accessible

    Hi all,

    I have set Bacula to perform backup at 8 PM every night and the mail server is up and running until around 11 PM and then for some unknown reasons it is not accessible until 8:15 AM or so. Found the info below in /var/log/messages. Can someone please help me fix this issue?

    Thanks,
    t

    Code:
    Jan  8 04:10:47 mail syslogd 1.4.1: restart.
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l 0b7eb407-50d9-4a82-b834-75deb1890693
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "getattr" to /var/spool/clientmqueue/dfq0899nxx025466 (var_spool_t). For complete SELinux messages. run sealert -l 16e5fbf8-d3da-464c-aa5d-6bfe95e31eaa
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "lock" to /var/spool/clientmqueue/dfq0899nxx025466 (var_spool_t). For complete SELinux messages. run sealert -l e92982cb-0930-47b6-9ed9-934f8564a3df
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to /var/spool/clientmqueue/dfq0899nxx025466 (var_spool_t). For complete SELinux messages. run sealert -l 590552ab-881d-4aa7-bf6b-808b350de52c
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq0899nxx025466 (var_spool_t). For complete SELinux messages. run sealert -l 74ff6372-3f9a-431e-9656-b9ab11e98327
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq0899nxx025466 (var_spool_t). For complete SELinux messages. run sealert -l bf95a808-a201-4fa0-b20c-7a04c6064400
    Jan  8 05:10:10 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l f90d4113-e8f2-40a9-96b6-7131e31bf3fb
    Jan  8 07:46:28 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan  8 07:46:28 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
    Jan  8 11:09:23 mail auditd[2698]: Audit daemon rotating log files
    Jan  9 04:51:59 mail syslogd 1.4.1: restart.
    Jan  9 06:47:27 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l 0b7eb407-50d9-4a82-b834-75deb1890693
    Jan  9 06:47:27 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "getattr" to /var/spool/clientmqueue/dfq099pIep018825 (var_spool_t). For complete SELinux messages. run sealert -l 8591e45e-dc4c-41ec-ada3-c2b6bdf691a9
    Jan  9 06:47:27 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "lock" to /var/spool/clientmqueue/dfq099pIep018825 (var_spool_t). For complete SELinux messages. run sealert -l 3afa34bf-24b4-4d20-a082-d55f11e9ccee
    Jan  9 06:47:27 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to /var/spool/clientmqueue/dfq099pIep018825 (var_spool_t). For complete SELinux messages. run sealert -l ea707dfb-a5cb-4310-8fc5-c03a769a9975
    Jan  9 06:47:27 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq099pIep018825 (var_spool_t). For complete SELinux messages. run sealert -l 5338f7f1-4a11-46fa-9c71-53b153d4c491
    Jan  9 06:47:29 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq099pIep018825 (var_spool_t). For complete SELinux messages. run sealert -l c885c5dc-3b0e-4651-9816-bc975de30d8a
    Jan  9 06:47:29 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l f90d4113-e8f2-40a9-96b6-7131e31bf3fb
    Jan  9 07:24:38 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan  9 07:24:38 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
    Jan 10 00:29:59 mail auditd[2698]: Audit daemon rotating log files
    Jan 10 05:36:29 mail syslogd 1.4.1: restart.
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l 0b7eb407-50d9-4a82-b834-75deb1890693
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "getattr" to /var/spool/clientmqueue/dfq0AAZltI001720 (var_spool_t). For complete SELinux messages. run sealert -l 43160841-b691-4a84-b3b7-8e9901ad9a4d
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "lock" to /var/spool/clientmqueue/dfq0AAZltI001720 (var_spool_t). For complete SELinux messages. run sealert -l 1ff3ba76-0a16-4725-b18b-9abd49c7f3cf
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to /var/spool/clientmqueue/dfq0AAZltI001720 (var_spool_t). For complete SELinux messages. run sealert -l f0b51294-3227-4749-ac43-575833cb5794
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq0AAZltI001720 (var_spool_t). For complete SELinux messages. run sealert -l 32ecb4fe-5d73-4cc5-b890-e644a23fa465
    Jan 10 07:52:42 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq0AAZltI001720 (var_spool_t). For complete SELinux messages. run sealert -l adcff514-e331-4d6c-90fa-d759c4e657a9
    Jan 10 08:23:09 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan 10 08:23:09 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin

  2. #2
    tezarin is offline Senior Member
    Join Date
    Dec 2008
    Posts
    61
    Rep Power
    6

    Default

    Anyone? Please help. This is the log for this morning:

    Code:
    Jan 12 05:30:24 mail syslogd 1.4.1: restart.
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to ./clientmqueue (var_spool_t). For complete SEL
    inux messages. run sealert -l 0b7eb407-50d9-4a82-b834-75deb1890693
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "getattr" to /var/spool/clientmqueue/dfq0CAU5TM011890 (va
    r_spool_t). For complete SELinux messages. run sealert -l b783b897-e00a-4b25-b2e4-a26fb95aecb2
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "lock" to /var/spool/clientmqueue/dfq0CAU5TM011890 (var_s
    pool_t). For complete SELinux messages. run sealert -l 868e7e30-3879-4610-a373-4f9cbb933b36
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to /var/spool/clientmqueue/dfq0CAU5TM011890 (var_
    spool_t). For complete SELinux messages. run sealert -l 9d94fb12-2c1b-41e9-840b-f3551cffb950
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq0CAU5TM011890 (var_spool_t). For complete
    SELinux messages. run sealert -l be657efb-7250-4f8e-ae9f-81597ee82975
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq0CAU5TM011890 (var_spool_t). For co
    mplete SELinux messages. run sealert -l 17e4928f-a571-4e36-9fb5-6ab47ab1af1f
    Jan 12 05:46:57 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./clientmqueue (var_spool_t). For complete SELi
    nux messages. run sealert -l f90d4113-e8f2-40a9-96b6-7131e31bf3fb
    Jan 12 08:15:57 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan 12 08:15:57 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
    The mail server is getting backed up with Bacula and bacula logs show the backup ended at 5:45 AM and the only thing that was running on the backup server was the backupcatalog job.

    Could you help please?

    Thanks in advance

  3. #3
    tezarin is offline Senior Member
    Join Date
    Dec 2008
    Posts
    61
    Rep Power
    6

    Default Server not accessible - zmmtacondig error

    Hi all,

    I've noticed my Zimbra mail server will be accessible at 7:15 ish every morning. It goes down sometimes at night (due to bacula backup process) but the backup process ends around 5 AM so I am not sure why the mail server stays down for two three hours after the backup process ended. This is the log I found on the mail server, could you please help me with this problem?

    Thanks in advance

    Code:
    Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
    Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Memcached Servers update. 
    Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update. 
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Configuration for server gauss.domain.com update. 
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: gs:gauss.domain.com ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
    Jan 13 07:15:26 mail zimbramon[6828]: 6828:info: Starting services initiated by zmcontrol 
    Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
    Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:28 mail slapd[7019]: @(#) $OpenLDAP: slapd 2.3.42 (May 29 2008 13:41:01) $ 	build@build11:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.42.6z/servers/slapd 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:29 mail slapd[7131]: slapd starting 
    Jan 13 07:15:33 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
    Jan 13 07:15:35 mail zimbramon[6828]: 6828:info: Rewriting configs  antispam amavis antivirus amavis imapproxy   webxml mailbox amavis antispam antivirus mta sasl    
    Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting logger via zmcontrol 
    Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting mailbox via zmcontrol 
    Jan 13 07:15:48 mail zimbramon[8086]: 8086:info: zmmtaconfig: zmmtaconfig already running at 31338 
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: status requested
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: no manager process is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: start requested
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: checking if another instance of manager is already running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
    Jan 13 07:16:09 mail zimbramon[6828]: 6828:info: Starting imapproxy via zmcontrol 
    Jan 13 07:16:09 mail zmmailboxdmgr[9049]: wrote manager pid 9049 to /opt/zimbra/log/zmmailboxd_manager.pid
    Jan 13 07:16:09 mail zmmailboxdmgr[9049]: manager started mailboxd/JVM with pid 9052
    Jan 13 07:16:09 mail zmmailboxdmgr[9052]: wrote java pid 9052 to /opt/zimbra/log/zmmailboxd_java.pid
    Jan 13 07:16:10 mail zimbramon[6828]: 6828:info: Starting antispam via zmcontrol 
    Jan 13 07:16:11 mail zimbramon[9106]: 9106:info: zmmtaconfig: zmmtaconfig already running at 31338 
    Jan 13 07:16:13 mail amavis[9170]: starting.  /opt/zimbra/amavisd/sbin/amavisd at gauss.domain.com amavisd-new-2.5.4 (20080312), Unicode aware, LANG="en_US.UTF-8"
    Jan 13 07:16:13 mail amavis[9170]: user=500, EUID: 500 (500);  group=, EGID: 500 501 500 5 4 (500 501 500 5 4)
    Jan 13 07:16:13 mail amavis[9170]: Perl version               5.008008
    Jan 13 07:16:16 mail amavis[9170]: SpamControl: init_pre_chroot done
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Process Backgrounded
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: 2012/01/13-07:16:16 Amavis (type Net::Server::PreForkSimple) starting! pid(9186)
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to UNIX socket file /opt/zimbra/data/amavisd/amavisd.sock using SOCK_STREAM
    Jan 13 07:16:16 mail zimbramon[6828]: 6828:info: Starting antivirus via zmcontrol 
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1

  4. #4
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,581
    Rep Power
    57

    Default

    Quote Originally Posted by tezarin View Post
    I've noticed my Zimbra mail server will be accessible at 7:15 ish every morning.
    Then why is this posted in the Zimbra Desktop forums?


    Quote Originally Posted by tezarin View Post
    It goes down sometimes at night (due to bacula backup process) but the backup process ends around 5 AM so I am not sure why the mail server stays down for two three hours after the backup process ended.
    That doesn't really tell give us much information. How are you starting and stopping the Zimbra services? How long has this been happening? Have you tried some of the solutions in the forums for this problem? site:zimbra.com +"zmmtaconfig: gacf ERROR:" - Yahoo! Search Results

    Quote Originally Posted by tezarin View Post
    This is the log I found on the mail server, could you please help me with this problem?

    Thanks in advance

    Code:
    Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
    Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
    Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Memcached Servers update. 
    Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update. 
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Configuration for server gauss.domain.com update. 
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: gs:gauss.domain.com ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
    Jan 13 07:15:26 mail zimbramon[6828]: 6828:info: Starting services initiated by zmcontrol 
    Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
    Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:28 mail slapd[7019]: @(#) $OpenLDAP: slapd 2.3.42 (May 29 2008 13:41:01) $ 	build@build11:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.42.6z/servers/slapd 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
    Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
    Jan 13 07:15:29 mail slapd[7131]: slapd starting 
    Jan 13 07:15:33 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
    Jan 13 07:15:35 mail zimbramon[6828]: 6828:info: Rewriting configs  antispam amavis antivirus amavis imapproxy   webxml mailbox amavis antispam antivirus mta sasl    
    Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting logger via zmcontrol 
    Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting mailbox via zmcontrol 
    Jan 13 07:15:48 mail zimbramon[8086]: 8086:info: zmmtaconfig: zmmtaconfig already running at 31338 
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: status requested
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9041]: no manager process is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: start requested
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: checking if another instance of manager is already running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
    Jan 13 07:16:09 mail zimbramon[6828]: 6828:info: Starting imapproxy via zmcontrol 
    Jan 13 07:16:09 mail zmmailboxdmgr[9049]: wrote manager pid 9049 to /opt/zimbra/log/zmmailboxd_manager.pid
    Jan 13 07:16:09 mail zmmailboxdmgr[9049]: manager started mailboxd/JVM with pid 9052
    Jan 13 07:16:09 mail zmmailboxdmgr[9052]: wrote java pid 9052 to /opt/zimbra/log/zmmailboxd_java.pid
    Jan 13 07:16:10 mail zimbramon[6828]: 6828:info: Starting antispam via zmcontrol 
    Jan 13 07:16:11 mail zimbramon[9106]: 9106:info: zmmtaconfig: zmmtaconfig already running at 31338 
    Jan 13 07:16:13 mail amavis[9170]: starting.  /opt/zimbra/amavisd/sbin/amavisd at gauss.domain.com amavisd-new-2.5.4 (20080312), Unicode aware, LANG="en_US.UTF-8"
    Jan 13 07:16:13 mail amavis[9170]: user=500, EUID: 500 (500);  group=, EGID: 500 501 500 5 4 (500 501 500 5 4)
    Jan 13 07:16:13 mail amavis[9170]: Perl version               5.008008
    Jan 13 07:16:16 mail amavis[9170]: SpamControl: init_pre_chroot done
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Process Backgrounded
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: 2012/01/13-07:16:16 Amavis (type Net::Server::PreForkSimple) starting! pid(9186)
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to UNIX socket file /opt/zimbra/data/amavisd/amavisd.sock using SOCK_STREAM
    Jan 13 07:16:16 mail zimbramon[6828]: 6828:info: Starting antivirus via zmcontrol 
    Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1
    According to that information it would appear that it's a problem with LDAP, have you looked for LDAP errors?
    Do you also have the imapproxy & memcached installed on this server (you shouldn't on a single server)? You might also consider disabling SELinux to see if the problem goes away, if it does you'll need to fix the SELinux configuration.

    In future don't post duplicate threads on the same topic and post in the correct forum for your topic. I'll merg your two threads on this topic.
    Last edited by phoenix; 01-14-2012 at 04:49 AM.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    tezarin is offline Senior Member
    Join Date
    Dec 2008
    Posts
    61
    Rep Power
    6

    Default

    Sorry if I posted in the wrong place first and thank you for your reply.

    The mail server gets backed up by another server which has Bacula installed on it. I disabled Bacula on the backup server so the mail server's log didn't complain about the same stuff as before and started working at aroud 7:25 AM or so.

    Please tell me what commands I should run to answer your questions, the previous IT person told me that he had to install imapproxy, but didn't say why.

    SELinux is on Permissive mode, do I still need to disable it?

    Also, after I disabled the backup process, the log doesn't complain about LDAP. But I did checked for the ldap information in /etc/ldap.conf and everything looked normal, what should I be looking for there?

    Here'e the new log:

    Code:
    Jan 17 04:38:38 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq0H99m9n002032 (var_spool_t). For complete SELinux messages. run sealert -l af8d29c8-042d-424f-9fd0-70b7c9ec541a
    Jan 17 04:38:38 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq0H99m9n002032 (var_spool_t). For complete SELinux messages. run sealert -l e79d0433-c7ef-4dc9-95e1-2443ae3de968
    Jan 17 04:38:38 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l f90d4113-e8f2-40a9-96b6-7131e31bf3fb
    Jan 17 07:21:08 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan 17 07:21:08 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
    Jan 18 02:36:34 mail auditd[2695]: Audit daemon rotating log files
    Jan 18 04:56:00 mail syslogd 1.4.1: restart.
    Jan 18 06:57:53 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l 0b7eb407-50d9-4a82-b834-75deb1890693
    Jan 18 06:58:05 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "getattr" to /var/spool/clientmqueue/dfq0I9tohu002547 (var_spool_t). For complete SELinux messages. run sealert -l 5febd43f-492b-4d5f-8cc5-0ad47a196ea3
    Jan 18 06:58:05 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "lock" to /var/spool/clientmqueue/dfq0I9tohu002547 (var_spool_t). For complete SELinux messages. run sealert -l de9633d3-448f-4d36-8adb-6827c824b1d7
    Jan 18 06:58:05 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "write" to /var/spool/clientmqueue/dfq0I9tohu002547 (var_spool_t). For complete SELinux messages. run sealert -l 1e09910e-f02e-447e-bb74-196abfb18e8f
    Jan 18 06:58:05 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./dfq0I9tohu002547 (var_spool_t). For complete SELinux messages. run sealert -l 2fe1312d-3a9c-41d2-a63f-5536aef3cfbb
    Jan 18 06:58:06 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "remove_name" to ./tfq0I9tohu002547 (var_spool_t). For complete SELinux messages. run sealert -l 483a0ba8-8648-4caf-8acb-c0a8645dac30
    Jan 18 06:58:06 mail setroubleshoot: SELinux is preventing sendmail (system_mail_t) "read" to ./clientmqueue (var_spool_t). For complete SELinux messages. run sealert -l f90d4113-e8f2-40a9-96b6-7131e31bf3fb
    Jan 18 07:38:02 mail saslauthd: auth_zimbra_init: zimbra_cert_check is off!
    Jan 18 07:38:02 mail saslauthd: auth_zimbra_init: 1 auth urls initialized for round-robin
    Last edited by tezarin; 01-18-2012 at 08:43 AM.

  6. #6
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,581
    Rep Power
    57

    Default

    Quote Originally Posted by tezarin View Post
    Please tell me what commands I should run to answer your questions, the previous IT person told me that he had to install imapproxy, but didn't say why.
    The imapproxy & memcached are, as I've already said, not required on a single server and may cause problems. There are several forum threads that give you full details of how to disable those serveices and stop them from being installed during your next upgrade, you will also find details on how to reset the ports to tehir defaults in those threads (you'll need to do that as well).

    Quote Originally Posted by tezarin View Post
    SELinux is on Permissive mode, do I still need to disable it?
    Yes, or find a way to make it work with Zimbra. IIRC, there's also some threads and possibly a wiki article on the subject - I'd initially disable it for testing.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    sjangra's Avatar
    sjangra is offline Intermediate Member
    Join Date
    May 2011
    Posts
    24
    Rep Power
    4

    Default

    disable selinux using #setenforce 0
    Thanks & Regards
    S. Jangra
    System Admin

  8. #8
    tezarin is offline Senior Member
    Join Date
    Dec 2008
    Posts
    61
    Rep Power
    6

    Default

    sjangra and phoenix, thanks for your replies.

    I cannot understand why the SSH connection to the mail server suddenly stopped working. The SSH port was not 22 and was changed to a different number for security purposes.

    phoenix, you mentioned I can reset the port to its default value which is not what I would like to do, I just want to be able to get the SSH working through the new port as before.

    I restarted the ssh on that box and rebooted it via the console and still no luck.

    Almost all of the boxes I'm working with are in permissive mode.

    Can you please help me find out what's causing this issue?

    Thanks

  9. #9
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,581
    Rep Power
    57

    Default

    Quote Originally Posted by tezarin View Post
    Almost all of the boxes I'm working with are in permissive mode.

    Can you please help me find out what's causing this issue?
    Disable SElinux (not permissive mode) and see if that fixes the problem.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Mysql.server Does Not Start
    By carnold in forum Administrators
    Replies: 7
    Last Post: 01-16-2012, 07:13 AM
  2. ZCS7 Beta only Listens on IPv6
    By tobru in forum Installation
    Replies: 2
    Last Post: 03-25-2011, 03:31 AM
  3. Issues after upgrading from 6.0.10 to 7
    By rhorist in forum Administrators
    Replies: 8
    Last Post: 02-25-2011, 08:38 AM
  4. Zimbra 6 on Ubuntu 8.04 x64 reverting to IPv6
    By nimble7 in forum Installation
    Replies: 1
    Last Post: 11-30-2010, 12:03 AM
  5. My Zimbra Server crashed this morning...
    By glitch23 in forum Administrators
    Replies: 3
    Last Post: 04-07-2008, 01:28 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •