Uploaded image for project: 'ejabberd development'
  1. ejabberd development
  2. EJAB-1700

CLONE - ejabberdctl - incoming-s2s-number and outgoing-s2s-number shows all the time 0

    Details

      Description

      I have problem with ejabberdctl in ejabberd 14.05. It shows all the time 0 when I would like to show incoming and outgoing S2S connections... Web panel shows good information. I checked this issue on another server and domain with new mnesia database. The result is the same.

        Issue Links

          Activity

          Hide
          beherit Krzysztof Grochocki added a comment -

          I clone issue because nobody answer in EJAB-1698. As I say:

          t's really some problem with this two commands! When I type in SSH "ejabberdctl outgoing_s2s_numbe" or "ejabberdctl incoming_s2s_number" it's return everytime value 0. It's not possible! I have many incoming/outgoing connections! Important: on ejabberd 2.1.13 this problem doesn't exists in my server. This same things I can get by using mod_statsdx:

          ejabberdctl getstatsdx s2sconnections
          ejabberdctl getstatsdx s2sservers

          It's work fine for me. But why ejabberdctl incoming_s2s_number/outgoing_s2s_number don't work? Please repair it.

          Show
          beherit Krzysztof Grochocki added a comment - I clone issue because nobody answer in EJAB-1698 . As I say: t's really some problem with this two commands! When I type in SSH "ejabberdctl outgoing_s2s_numbe" or "ejabberdctl incoming_s2s_number" it's return everytime value 0. It's not possible! I have many incoming/outgoing connections! Important: on ejabberd 2.1.13 this problem doesn't exists in my server. This same things I can get by using mod_statsdx: ejabberdctl getstatsdx s2sconnections ejabberdctl getstatsdx s2sservers It's work fine for me. But why ejabberdctl incoming_s2s_number/outgoing_s2s_number don't work? Please repair it.
          Hide
          holger Holger Weiß added a comment -

          With ejabberd 14.05, incoming_s2s_number and outgoing_s2s_number will only work if you called ./configure with the --enable-transient_supervisors flag while building ejabberd. Otherwise, these commands will always return 0 indeed.

          Show
          holger Holger Weiß added a comment - With ejabberd 14.05, incoming_s2s_number and outgoing_s2s_number will only work if you called ./configure with the --enable-transient_supervisors flag while building ejabberd. Otherwise, these commands will always return 0 indeed.
          Hide
          gturner Gerald Turner added a comment -

          Is this bug really fixed in 14.07? I'm using the Debian jessie package version 14.07-4 and ejabberdctl outgoing-s2s-number or incoming-s2s-number always report 0. Note that the debian package is not built with --enable-transient_supervisors, as a work-around that Holger Weiß suggested for an earlier version of ejabberd.

          Show
          gturner Gerald Turner added a comment - Is this bug really fixed in 14.07? I'm using the Debian jessie package version 14.07-4 and ejabberdctl outgoing-s2s-number or incoming-s2s-number always report 0. Note that the debian package is not built with --enable-transient_supervisors, as a work-around that Holger Weiß suggested for an earlier version of ejabberd.
          Hide
          holger Holger Weiß added a comment -

          In ejabberd 15.02 and newer, --enable-transient_supervisors is the default, so this will probably be fixed in a future version of the Debian package. I'm not sure it's possible to apply this change to the Jessie package at this point, but I see you already posted a bug report on the Debian tracker, so that can be clarified over there.

          Show
          holger Holger Weiß added a comment - In ejabberd 15.02 and newer, --enable-transient_supervisors is the default, so this will probably be fixed in a future version of the Debian package. I'm not sure it's possible to apply this change to the Jessie package at this point, but I see you already posted a bug report on the Debian tracker , so that can be clarified over there.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development