Regarding Issue 44013 - Junk after JSON on Termination

Archives Ansible Project
1

G’day.

I was looking at this particular closed case, https://github.com/ansible/ansible/issues/44013. In particular, the HPE NonStop platform’s SSH always reports a termination message for SSH sessions that results in a warning:

[WARNING]: Module invocation had junk after the JSON data: STN39 Session terminated - application closed terminal 01/09 07:57

Granted that this is just a warning, but the environment is one of High Availability and warnings are generally considered “bad” requiring explanation, resolution, or written exemption for why it can be ignored. Is there any way this particular change can be either undone or provide a playbook, environment variable, or some other option to suppress the warning?

There is no option on the platform for suppressing the “Session terminated” message short of aggressively closing the session when you think you are done. This applies to all three of the hardware/software platform variants of HPE NonStop (NSE, NSX, and NSV).

Please Note: This occurs in 100% of playbooks that execute tasks on this platform regardless of the client where ansible-playbook is initiated.

Kind Regards,
Randall

2

Hi ,

I am not sure whether you found solution or not ,

1 . why application is closing : reason , there is some session time out for the terminal . we need to make the properties of that to never.
2. Alternative solution: after starting session , run a backend script to display the current time for every 20min. so the session won’t go off.

I am starting with ansible for NSK , If possible can you the location of setup , I will try to understand the project , to write for the same .

Thanks
Bhaskar