Exception occurred while restarting the listener (File Listener)

General
, , ,
1

Hello, Pega community,

I am facing a sudden failure on all of our file listeners in our staging environment with what appears to be little in lieu of error logging or stack traces.

We have 3 applications that share this environment. In this environment, we have 4 web nodes and 2 background processing nodes with the file listeners configured to start up on the background processing nodes. We are currently using Pega 8.2.2 and are running baseline performance testing prior to upgrading to 8.6.3.

When attempting to start the file listeners from Admin Studio, I am greeted with the red banner stating
“: Exception occurred while restarting the listener FILE-Thread-xx” on every file listener.

Things that I have attempted thus far:

  • Validate that the operator on the file listener rule form is accurate and has the appropriate access groups and credentials.
  • Log into a background processing node directly and test the connection from the rule form.
    • This shows a positive access test, so I’ve concluded it’s not an authorization problem.
  • Restarted the entire environment and confirmed Kafka and other required services have come online.
  • Validated there are no unreachable stream nodes and cross-validated the node ID to the nodes in the “Systems and Nodes”
  • Compared the stage environment to other regions that are not upgraded and concluded we do not have a code sync issue.

Is there any logging I can set for these listeners when attempting to start them up that I could use to isolate the root cause?

Thanks,

Will McHugh

2

@WilliamM9222 We have enabled logging for the file listeners and are attempting a server restart. I’ll attach the log output once that is completed.

3

@WilliamM9222 Please check the admin studio for knowing if the file listener is working on one single node.

4

@VarshiniD8035 Thank you very much for the reply.

We opened an SR to identify the root cause. After setting logging to ALL on the file listeners, we did see an authentication issue with the operator record assigned to the listener. Once we changed the operator password and applied it in the listener form, we could restart the listeners. However, we did see some odd behavior in Admin Studio whereby an error was presented stating the listeners could not be started. However, once refreshing that part of admin studio, the listeners showed as sleeping.

I hope this helps others facing a similar issue.

5

Thanks @WilliamM9222 for sharing your resolution! I went ahead and marked your reply as such.

You mentioned that you opened an SR, could you please share that ID with us so that we can track that on our end?

Thank you so much!