8 Replies Latest reply on Jun 29, 2021 1:32 AM by Prasenjit Saha

    Service went down without any logs in node.log file

    User informatica Active Member

      Hi Team,

       

      I see the node services went down suddenly and when i checked the rootcause in node.log file , i don't see anything written in all three node,exception and catalina files.Could you please let me know what could be the reason and where we could find the rootcause.

       

      Thankyou!

        • 1. Re: Service went down without any logs in node.log file
          Pavan kumar Guru

          Please check the domain log if there are any errors at that time frame.

          • 2. Re: Service went down without any logs in node.log file
            User informatica Active Member

            Thanks for your response.

             

            No, i dont see any in admin console domain log .

            • 3. Re: Service went down without any logs in node.log file
              User informatica Active Member

              I see the below error in the admin console server log

               

              com.informatica.pcsf.servicesframework.client.impl.ClientFactoryImpl sendHeartbeatToRecipient ERROR: [Non-Resilient-HeartbeatSender-Thread-2] [JSF_0040] Heartbeat operation failed for connection [U:83bDZqylEeu1g32W_IG_KA] to the service [DomainService]. [[DTF_0001] An error occurred in the underlying transport layer: [java.util.concurrent.ExecutionException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.]].

              com.informatica.pcsf.datatransport.DataTransportException: [DTF_0001] An error occurred in the underlying transport layer: [java.util.concurrent.ExecutionException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.]

                      at com.informatica.pcsf.datatransport.impl.DataTransportChannelImpl.sendRequest(DataTransportChannelImpl.java:92)

                      at com.informatica.pcsf.servicesframework.client.impl.ClientFactoryImpl.sendHeartbeatToRecipient(ClientFactoryImpl.java:1115)

                      at com.informatica.pcsf.servicesframework.client.impl.ClientFactoryImpl.sendHeartbeatToRecipient(ClientFactoryImpl.java:1091)

                      at com.informatica.pcsf.servicesframework.client.impl.ClientFactoryImpl.access$3(ClientFactoryImpl.java:1090)

                      at com.informatica.pcsf.servicesframework.client.impl.ClientFactoryImpl$HeartbeatSender.run(ClientFactoryImpl.java:1072)

                      at java.lang.Thread.run(Thread.java:748)

              Caused by: org.beepcore.beep.core.BEEPException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.java.util.concurrent.ExecutionException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.

                      at org.beepcore.beep.core.ChannelImpl.sendMSG(ChannelImpl.java:493)

                      at com.informatica.pcsf.datatransport.impl.DataTransportChannelImpl.sendRequest(DataTransportChannelImpl.java:88)

                      ... 5 more

              Caused by: java.util.concurrent.ExecutionException: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.

                      at java.util.concurrent.FutureTask.report(FutureTask.java:122)

                      at java.util.concurrent.FutureTask.get(FutureTask.java:206)

                      at org.beepcore.beep.core.ChannelImpl.sendMSG(ChannelImpl.java:473)

                      ... 6 more

              Caused by: org.beepcore.beep.core.BEEPException: [sendMSG]: Channel is in [8 : ABORTED] state.

                      at org.beepcore.beep.core.ChannelImpl.sendMsgInternal(ChannelImpl.java:398)

                      at org.beepcore.beep.core.ChannelImpl.access$0(ChannelImpl.java:388)

                      at org.beepcore.beep.core.ChannelImpl$AsyncMessageSender.call(ChannelImpl.java:1351)

                      at org.beepcore.beep.core.ChannelImpl$AsyncMessageSender.call(ChannelImpl.java:1)

                      at java.util.concurrent.FutureTask.run(FutureTask.java:266)

                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                      ... 1 more

              • 4. Re: Service went down without any logs in node.log file
                Prasenjit Saha Guru

                Hi,

                 

                Did you check if any other services were running or only the Admin console was not accessible?

                What did you do to overcome the issue? Restarted the node?

                 

                Please try to share the node.log file once (at least for that date if large file). Just to re-confirm that no evidence is there

                • 5. Re: Service went down without any logs in node.log file
                  Pavan kumar Guru

                  Hi,

                   

                  Please check if there are any errors in the node.log/catalina.out. If possible, please share these logs here.

                   

                  Thank you,

                  Pavan

                  • 6. Re: Service went down without any logs in node.log file
                    Pavan kumar Guru

                    In case if the files are huge, filter the logs of that date and share them with us.

                     

                    Thank you,

                    Pavan

                    • 7. Re: Service went down without any logs in node.log file
                      user136699 Guru

                      Check the domain log to see if any node is marked inactive ( search for the word inactive). If  you do find any entry, does that correspond with the services going down?

                      - Girish

                      • 8. Re: Service went down without any logs in node.log file
                        Prasenjit Saha Guru

                        Hello,

                         

                        I hope this issue got resolved already. If not, please comment here for any further discussion.

                         

                        Regards,

                        Prasenjit