Results 1 to 9 of 9

Thread: [Zimbra 7.1.4] Admin console server status down and no statistic

  1. #1
    Join Date
    Feb 2012
    Posts
    3
    Rep Power
    3

    Default [Zimbra 7.1.4] Admin console server status down and no statistic

    Hi guys,

    I've a new Zimbra 7.1.4 installation (into a fresh RHEL 6.2 x86_64 server), with zcs-patch-7.1.4_GA_2568 already installed.

    Version:
    [zimbra@mail ~]$ zmcontrol -v
    Release 7.1.4_GA_2555.RHEL6_64_20120105094542 RHEL6_64 FOSS edition, Patch 7.1.4_P1.
    [zimbra@mail ~]$
    As already reported in other threads, in admin console all the zimbra services shows as down, and I'm not be able to see the server statistics.

    Procedures already done without success:

    1. Regenerating ssh keys, update, stop and start:
    su - zimbra
    zmsshkeygen
    zmupdateauthkeys
    zmloggerctl stop; zmloggerctl start
    2. check with visudo if requiretty was commented out:
    #Defaults requiretty
    3. Run the command:
    /opt/zimbra/libexec/zmsyslogsetup

    4. Check the server hostname, MX record, and so on:
    [root@mail ~]# cat /etc/hosts
    127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
    ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

    10.100.1.13 mail.mydomain.net mail
    [root@mail ~]#
    [root@mail ~]# cat /etc/resolv.conf
    # Generated by NetworkManager
    nameserver 127.0.0.1
    nameserver 8.8.4.4
    search mydomain.net
    [root@mail ~]#
    [root@mail ~]# dig mydomain.net mx

    ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 <<>> mydomain.net mx
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39918
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;mydomain.net. IN MX

    ;; ANSWER SECTION:
    mydomain.net. 10497 IN MX 0 mail.mydomain.net.

    ;; ADDITIONAL SECTION:
    mail.mydomain.net. 2592000 IN A 10.100.1.13

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Sun Feb 26 13:18:23 2012
    ;; MSG SIZE rcvd: 74

    [root@mail ~]#
    [root@mail ~]# dig mydomain.net any

    ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 <<>> mydomain.net any
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34024
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;mydomain.net. IN ANY

    ;; ANSWER SECTION:
    mydomain.net. 10434 IN MX 0 mail.mydomain.net.

    ;; ADDITIONAL SECTION:
    mail.mydomain.net. 2592000 IN A 10.100.1.13

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Sun Feb 26 13:19:26 2012
    ;; MSG SIZE rcvd: 74

    [root@mail ~]#
    [root@mail ~]# host `hostname`
    mail.mydomain.net has address 10.100.1.13
    mail.mydomain.net mail is handled by 10 mail.mydomain.net.
    [root@mail ~]#
    [zimbra@mail ~]$ zmcontrol status
    Host mail.mydomain.net
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Running
    mta Running
    snmp Running
    spell Running
    stats Running
    zmconfigd Running
    [zimbra@mail ~]$
    [zimbra@mail ~]$ zmprov gcf zimbraLogHostname
    zimbraLogHostname: mail.mydomain.net
    [zimbra@mail ~]$

    Can someone help to to solve that issue?


    Giordano

  2. #2
    Join Date
    Feb 2012
    Posts
    4
    Rep Power
    3

    Default

    Hi, I had the same problem, fix here http://www.zimbra.com/forums/adminis...s-ones-up.html.
    Good luck, Bye

  3. #3
    Join Date
    Nov 2008
    Location
    Grand Rapids, MI
    Posts
    123
    Rep Power
    6

    Default

    Another thing to check is if you have an AllowUsers line in the sshd_config file on your server. If you do, the zimbra user needs to be listed on it. If you don't have an AllowUsers line then that's probably not the problem.

  4. #4
    Join Date
    Nov 2008
    Location
    Grand Rapids, MI
    Posts
    123
    Rep Power
    6

    Default

    I've also seen hostname mismatches confuse things. Check that the output from 'zmloggerhostmap' is sane.

  5. #5
    Join Date
    Feb 2012
    Posts
    3
    Rep Power
    3

    Default

    @jcsnake:
    I checked the /etc/rsyslog.conf but it seems ok:

    local0.* -/var/log/zimbra.log
    local1.* -/var/log/zimbra-stats.log
    auth.* -/var/log/zimbra.log
    mail.* -/var/log/zimbra.log

    @ justdave:

    No AllowUsers on sshd_config, and below the command output:

    [zimbra@mail ~]$ zmloggerhostmap
    Zimbra Logger Service Hostname Map

    --------------------- ---------------------
    DNS Hostname Zimbra Hostname
    --------------------- ---------------------
    mail.myhostname. mail.myhostname.
    mail mail.myhostname.
    So, at this time I search on google and find:

    http://www.zimbra.com/forums/migrati...ervername.html

    I'll try it to see if works or not.

  6. #6
    Join Date
    Feb 2012
    Posts
    3
    Rep Power
    3

    Default

    Deleting and adding it as suggest have no success, and now I see:

    [zimbra@mail ~]$ zmloggerhostmap
    Zimbra Logger Service Hostname Map

    --------------------- ---------------------
    DNS Hostname Zimbra Hostname
    --------------------- ---------------------
    mail mail
    mail.mydomain. mail.mydomain.

    I still see all the services as down

  7. #7
    Join Date
    Sep 2008
    Location
    Dallas, TX
    Posts
    17
    Rep Power
    7

    Default

    Did you ever resolve your problem? I'm fighting the same battle except we've been up and running for 8 months. Suddenly, I'm seeing red on the Server Status screen, but when I look at it on the server, everything's fine.

  8. #8
    Join Date
    Apr 2008
    Posts
    22
    Rep Power
    7

    Default

    Quote Originally Posted by sbhnet View Post
    Did you ever resolve your problem? I'm fighting the same battle except we've been up and running for 8 months. Suddenly, I'm seeing red on the Server Status screen, but when I look at it on the server, everything's fine.
    Make sure the server is listening! Zimbra's installer gets the syslog forwarding configuration right, but on ubuntu server for example, by default, rsyslogd isn't listening to outside forwarded messages. Check /etc/rsyslogd.conf and make sure these lines are uncommented:

    # provides UDP syslog reception
    $ModLoad imudp
    $UDPServerRun 514

    Then do a service rsyslog reload, and to verify:

    netstat -tlnup | grep 514

    If you see these two lines:


    udp 0 0 0.0.0.0:514 0.0.0.0:* 16662/rsyslogd
    udp6 0 0 :::514 :::* 16662/rsyslogd

    You're golden, and your status will show green within a couple of minutes.

  9. #9
    Join Date
    Sep 2008
    Location
    Dallas, TX
    Posts
    17
    Rep Power
    7

    Default

    We just upgraded to 7.2 two nights ago, and that seems to have solved the problem. What was weird is that we had been rocking along with no changes since the first of the year. Everything's green now. Fingers crossed... Thanks!

Posting Permissions

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