Description

This Article is applicable to all QFX5k Platforms and explains the meaning of the log message “%PFE-3: fpc0 CPROD: A thread did not disown its tty”, cause, and ways to prevent it.

Symptoms

On QFX5k platforms below logs are continuously or intermittently generated on the device:-

Feb  2 11:48:31  router : %PFE-3: fpc0 CPROD: A thread did not disown its tty.

Feb  2 11:48:36  router : %PFE-3: fpc0 CPROD: A thread did not disown its tty.

Feb  2 11:48:36  router : %PFE-3: fpc0 CPROD: A thread did not disown its tty.

Feb  2 11:48:42  router : %PFE-3: fpc0 CPROD: A thread did not disown its tty.

Feb  2 11:48:47  router : %PFE-3: fpc0 CPROD: A thread did not disown its tty.

 

Solution

Cprod or cattle prod daemon executes PFE-level commands from shell mode on the device. The log message is generated whenever a PFE-level command is executed from the shell using cprod and it times out.

 

Below is the Output from the lab device:-

 

user@device> ...mmand "set dcbcm bcm \"phy diag 29 dsc\"" timeout 0  

 Feb 13 03:24:33

 SENT: Ukern command: set dcbcm bcm "phy diag 29 dsc"

 ERROR: Command timed out.

 Feb 13 03:23:17 device fpc0 CPROD: A thread did not disown its tty.

Feb 13 03:23:17 device fpc0 CPROD: A thread did not disown its tty.

Feb 13 03:24:16 device fpc0 CPROD: A thread did not disown its tty.

Feb 13 03:24:17 device fpc0 CPROD: A thread did not disown its tty.

 

Check if any PFE-level commands are being executed on the device resulting in the log message.

If the message is continuously generating without any PFE level commands being executed then open a case and engage JTAC for further investigation

 

Modification History

Revision 1