Listener going into Suspend and Resume on it's own?

Tony Kilbarger · ‎08-19-2019

I was investigating an email slowdown this morning and when I brought up one of our Cloud CES ESA's in a browser it showed that the listener was suspended. I went to the CLI-Log and I can see this:

Mon Aug 19 08:14:58 2019 Info: PID 84174: User cics-admin login from 184.94.240.140 on 216.71.145.120

Mon Aug 19 08:15:01 2019 Info: PID 84174: User cics-admin executed batch command: 'status detail'

Mon Aug 19 08:15:02 2019 Info: PID 84174: User cics-admin logged out of Command Line Interface using SSH connection.

Mon Aug 19 08:15:16 2019 Info: PID 84316: User cics-admin login from 184.94.240.140 on 216.71.145.120

Mon Aug 19 08:15:18 2019 Info: PID 84316: User cics-admin executed batch command: 'suspendlistener all 30'

Mon Aug 19 08:15:44 2019 Info: PID 84316: User cics-admin logged out of Command Line Interface using SSH connection.

Mon Aug 19 08:17:24 2019 Info: PID 85015: User cics-admin login from 184.94.240.140 on 216.71.145.120

Mon Aug 19 08:17:26 2019 Info: PID 85015: User cics-admin executed batch command: 'resume'

Mon Aug 19 08:17:30 2019 Info: PID 85015: User cics-admin logged out of Command Line Interface using SSH connection.

Is this normal behaviour? Please advise?

dmccabej · ‎08-19-2019

Hello Tony,

Yes, this is expected for devices hosted within CES. We have a proactive team that monitors alerts such as workqueue backups and then will suspend the listeners temporarily to assist with letting the ESA clear out. This will not typically impact your mail flow as you'll have another ESA to continue processing. With the exception, of course, is if all of your ESAs are backed up.

Thanks!

-Dennis M.