ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Odd Zimbra zmconfigd behavior

    IT Discussion
    zimbra zimbra 8.8.11
    5
    16
    2.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dbeatoD
      dbeato @EddieJennings
      last edited by

      @EddieJennings said in Odd Zimbra zmconfigd behavior:

      I typically do the same. I tried the restart command to see if there would be any difference.

      Zimbra is
      Release 8.8.11_GA_3737.RHEL7_64_20181207111719 RHEL7_64 FOSS edition, Patch 8.8.11_P1

      What's strange is that the service is eventually starting.

      I don't have it running
      2019-01-29_2123.png

      1 Reply Last reply Reply Quote 0
      • EddieJenningsE
        EddieJennings
        last edited by

        I also find this curious, since I've read there should be a zmconfigd.log file.

        [zimbra@zimbra log]$ pwd && ls zmcon*
/opt/zimbra/log
zmconfigd-audit.log  zmconfigd-log4j.log  zmconfigd.pid

        Perhaps that's another Network edition feature: having that particular log file.

        1 Reply Last reply Reply Quote 1
        • EddieJenningsE
          EddieJennings
          last edited by

          Outside of the scope of this a bit, but where this behavior's a problem for me is related to what I'm experimenting with as a full backup scheme. Part of the process is stopping all zimbra services, doing a task, and restarting them. With zmconfigd failing with the restart, that adds another 30 seconds at least to the startup time.

          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @EddieJennings
            last edited by

            @EddieJennings said in Odd Zimbra zmconfigd behavior:

            I've noticed what seems to be an odd behavior while I've been poking around Zimbra.

            [zimbra@zimbra ~]$ zmconfigdctl restart 
Stopping zmconfigd...done.
Starting zmconfigd...failed.
[zimbra@zimbra ~]$ zmconfigdctl status 
zmconfigd is not running.
[zimbra@zimbra ~]$ zmconfigdctl status
zmconfigd is running.

            What happens is if I were to stop and start the service, the service initial fails to start, but then apparently starts itself about 3 seconds later. I've noticed there is no zmconfigd.log file to be found.

            As I discover more, I'll post. Have any of you Zimbra users experienced this behavior with zmconfigd?

            This is new to me, I started seeing it about a week ago. I feel that it is something in the latest packages causing at issue.

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @dbeato
              last edited by

              @dbeato said in Odd Zimbra zmconfigd behavior:

              @EddieJennings said in Odd Zimbra zmconfigd behavior:

              st. Have any of you Zimbra users experienced this behavior with zmconfigd?

              No I have not, What Zimbra version are you on? Usually when I want to restart the services I just use

              zmmcontrol start
zmmcontrol stop

              I'm seeing it in 8.8.10

              dbeatoD 1 Reply Last reply Reply Quote 1
              • dbeatoD
                dbeato @scottalanmiller
                last edited by

                @scottalanmiller said in Odd Zimbra zmconfigd behavior:

                @dbeato said in Odd Zimbra zmconfigd behavior:

                @EddieJennings said in Odd Zimbra zmconfigd behavior:

                st. Have any of you Zimbra users experienced this behavior with zmconfigd?

                No I have not, What Zimbra version are you on? Usually when I want to restart the services I just use

                zmmcontrol start
zmmcontrol stop

                I'm seeing it in 8.8.10

                I saw it as well once I restarted on my lab one. The production one does not have that issue.

                black3dynamiteB 1 Reply Last reply Reply Quote 0
                • black3dynamiteB
                  black3dynamite @dbeato
                  last edited by

                  @dbeato said in Odd Zimbra zmconfigd behavior:

                  @scottalanmiller said in Odd Zimbra zmconfigd behavior:

                  @dbeato said in Odd Zimbra zmconfigd behavior:

                  @EddieJennings said in Odd Zimbra zmconfigd behavior:

                  st. Have any of you Zimbra users experienced this behavior with zmconfigd?

                  No I have not, What Zimbra version are you on? Usually when I want to restart the services I just use

                  zmmcontrol start
zmmcontrol stop

                  I'm seeing it in 8.8.10

                  I saw it as well once I restarted on my lab one. The production one does not have that issue.

                  Your production and lab using Ubuntu?

                  dbeatoD 1 Reply Last reply Reply Quote 0
                  • dbeatoD
                    dbeato @black3dynamite
                    last edited by

                    @black3dynamite said in Odd Zimbra zmconfigd behavior:

                    @dbeato said in Odd Zimbra zmconfigd behavior:

                    @scottalanmiller said in Odd Zimbra zmconfigd behavior:

                    @dbeato said in Odd Zimbra zmconfigd behavior:

                    @EddieJennings said in Odd Zimbra zmconfigd behavior:

                    st. Have any of you Zimbra users experienced this behavior with zmconfigd?

                    No I have not, What Zimbra version are you on? Usually when I want to restart the services I just use

                    zmmcontrol start
zmmcontrol stop

                    I'm seeing it in 8.8.10

                    I saw it as well once I restarted on my lab one. The production one does not have that issue.

                    Your production and lab using Ubuntu?

                    YEs.

                    1 Reply Last reply Reply Quote 0
                    • B
                      Bend3r
                      last edited by

                      Hi!
                      Got the same problem with 8.8.12 installed on a Centos 7.
                      Moreover, according to zimbra.log, zmconfigd restarts once a minute for me.
                      Have you managed to resolve this issue?

                      Thanks in advance.

                      dbeatoD 1 Reply Last reply Reply Quote 0
                      • dbeatoD
                        dbeato @Bend3r
                        last edited by

                        @Bend3r said in Odd Zimbra zmconfigd behavior:

                        Hi!
                        Got the same problem with 8.8.12 installed on a Centos 7.
                        Moreover, according to zimbra.log, zmconfigd restarts once a minute for me.
                        Have you managed to resolve this issue?

                        Thanks in advance.

                        What is it causing on your Zimbra? mine are unaffected.

                        1 Reply Last reply Reply Quote 0
                        • B
                          Bend3r
                          last edited by Bend3r

                          @dbeato said in Odd Zimbra zmconfigd behavior:

                          What is it causing on your Zimbra? mine are unaffected.

                          For me, everything is working smooth, the only thing I worry about is restart notice messages that are written to zimbra.log every minute.

                          Jul  2 00:47:20 mail zmconfigd[24959]: Fetching All configs
Jul  2 00:47:20 mail zmconfigd[24959]: All configs fetched in 0.07 seconds
Jul  2 00:47:26 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul  2 00:47:26 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul  2 00:47:26 mail zmconfigd[24959]: All restarts completed in 0.00 sec
Jul  2 00:48:26 mail zmconfigd[24959]: Fetching All configs
Jul  2 00:48:26 mail zmconfigd[24959]: All configs fetched in 0.10 seconds
Jul  2 00:48:33 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul  2 00:48:33 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul  2 00:48:33 mail zmconfigd[24959]: All restarts completed in 0.00 sec

                          Perhaps, such a behavior is OK (zmconfigd fetches configs,checks them for not being changed and assumes no restarts needed for services)?

                          scottalanmillerS 1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @Bend3r
                            last edited by

                            @Bend3r said in Odd Zimbra zmconfigd behavior:

                            @dbeato said in Odd Zimbra zmconfigd behavior:

                            What is it causing on your Zimbra? mine are unaffected.

                            For me, everything is working smooth, the only thing I worry about is restart notice messages that are written to zimbra.log every minute.

                            Jul  2 00:47:20 mail zmconfigd[24959]: Fetching All configs
Jul  2 00:47:20 mail zmconfigd[24959]: All configs fetched in 0.07 seconds
Jul  2 00:47:26 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul  2 00:47:26 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul  2 00:47:26 mail zmconfigd[24959]: All restarts completed in 0.00 sec
Jul  2 00:48:26 mail zmconfigd[24959]: Fetching All configs
Jul  2 00:48:26 mail zmconfigd[24959]: All configs fetched in 0.10 seconds
Jul  2 00:48:33 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul  2 00:48:33 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul  2 00:48:33 mail zmconfigd[24959]: All restarts completed in 0.00 sec

                            Perhaps, such a behavior is OK (zmconfigd fetches configs,checks them for not being changed and assumes no restarts needed for services)?

                            I think so. Nothing in there suggests a restart happened.

                            1 Reply Last reply Reply Quote 2
                            • 1 / 1
                            • First post
                              Last post