Cold standby instance not syncing plus the primary instance says channel unregistered | Community
Skip to main content
A
Alisahali
Level 3
January 31, 2022

Cold standby instance not syncing plus the primary instance says channel unregistered

  • January 31, 2022
  • 3 replies
  • 4074 views

Hello there,

As part of our 6.5 upgrade, we've decided to derive a standby instance from the primary author instance. I've thoroughly followed the steps mentioned in the official adobe documentation. However, when I goto the JMX console on the primary author, It says 'channel unregistered'. Whereas, on the standby instance, the status is stuck at 'initializing'. I've restarted these instances multiple times only to run into the same problem over and over again. Any pointers about how to troubleshoot this problem would be greatly appreciated. Thanks!

 

 

P.S. Tagging @milind_bachani and @pavan_kalyan-1 for a quick response. As always, thanks in advance guys for being sooo helpful 🙂

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Pavan_Kalyan-1
Pavan_Kalyan-1
Level 3
February 1, 2022

Hi @alisahali 

I believe you must me missing something while doing the process.

Please refer this below link for reference 

https://www.youtube.com/watch?v=Sr0n-P5PnhA

kindly revert me back if you still face the same issue.!

Thanks!

    A
    AlisahaliAuthor
    Level 3
    February 2, 2022

    Hey @pavan_kalyan-1 . Unfortunately, I haven't had any luck resolving it. I did follow every step as mentioned here. My last resort is to try and remove all the old config files on the primary instance, set up new configuration files and then derive a standby instance from it. I'm going to try it in a few hours. Hopefully that resolves it.

     

    Also, I see the 'writing segments' and 'loading segments' logs on the primary instance tarmk-coldstandby.log file. However, all I see on the standby instance logs is ''head state did not change: skipping flush". There's something preventing the standby from establishing a TCP/IP connection with the primary instance. I noticed that the TCP port on our primary instance is active. Also, the standby entry for the standby instance (with standby's clientid)  on the jmx console on our primary instance is missing, which sort of confirms that the connection hasn't been established yet. 

      milind_bachani
      Adobe Employee
      milind_bachaniAdobe Employee
      Adobe Employee
      February 8, 2022

      hi @alisahali , Sorry for the delayed response as I was away for a while.

      Have you installed latest service pack and tried ? If not can you please refer https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en
      and try installing the same.

       

      Once done restart and check, let me know if that doesnt help. Many thanks.

        A
        AlisahaliAuthor
        Level 3
        February 9, 2022

        @milind_bachani yes we had already upgraded to 6.5.11.0 using the service pack, hence we can rule out the possibility of it being a service pack related issue. 

          milind_bachani
          Adobe Employee
          milind_bachaniAdobe Employee
          Adobe Employee
          February 9, 2022

          @alisahali do you see any relevant error logs ? If yes, can you share them, I am trying to replicate the issue , I disabled the jmx console provider but in that case the JMX console totally disappears and I am not able to catch up with the error 'channel unregistered' that you have mentioned.

            L
            lnotarantonio
            March 4, 2022

            Hi,

            we ran into the same problem with a clean install of AEM 6.5+SP12. Everything seems correct but the standby seems not to call the primary istance. From the standby or primary log I didn't find anything relevant.

            Trying a curl to the primary also results in error "io.netty.handler.codec.DecoderException:   not an SSL/TLS record"

             

            In the meantime I will try with the workaround suggested by @jugs installing oak-segment-tar-1.24.0.jar 

             

              J
              jugs
              Level 2
              March 4, 2022

              Hi,

               

              Try v1.22.9 of the oak-segment-tar which is what adobe support gave us and said will be in the next service pack.

               

              It worked for us as well.

                Terms & ConditionsAccessibility statement

                Loading footer...