Description

This KB addresses the error log observed after running "show ntp associations" command in operational mode :

 

{master:0}

root@QFX5100> show ntp associations

/usr/libexec/ld-elf.so.1: /usr/bin/ntpq: Shared object has no run-time symbol table

Symptoms

In the regular production setup, error logs are observed after executing the operational mode commands. No traffic impact was reported due to this issue.

Solution

  • Error logs are observed, after executing the below operational mode commands :

 

{master:0}
root@QFX5100> show ntp associations
/usr/libexec/ld-elf.so.1: /usr/bin/ntpq: Shared object has no run-time symbol table


{master:0}
root@QFX5100> show system processes extensive
mgd: unable to execute /usr/bin/top: Exec format error




{master:0}
root@QFX5100> monitor interface traffic
cli: unable to execute /usr/sbin/iftop: Input/output error


 

  • During the issue state, we might not be able to collect RSI and /var/logs. Input/Output errors are observed.

 

% more RSI.txt

/usr/bin/more: Input/output error.

 

 

  • Also, during the issue state, below errors could be seen while trying to enter the vty mode :

 

root@QFX5100:RE:0% vty fpc0
/usr/sbin/vty: Input/output error.
root@QFX5100:RE:0% vty fpc1
/usr/sbin/vty: Input/output error.

 

Message Logs :

 

Apr 25 10:30:41  QFX5100 mgd[89691]: UI_CHILD_EXEC: Child exec failed for command '/usr/libexec/ui/show-support': Input/output error
Apr 25 10:30:41  QFX5100 mgd[89690]: UI_CHILD_EXITED: Child exited: PID 89691, status 1, command '/usr/libexec/ui/show-support'
Apr 26 09:56:51  QFX5100 mgd[94134]: UI_CHILD_EXITED: Child exited: PID 94135, status 1, command '/usr/bin/ntpq'
Apr 26 10:09:04  QFX5100 mgd[94237]: UI_CHILD_EXEC: Child exec failed for command '/usr/bin/top': Exec format error
 

Resolution Steps :

  1. Restart the mgd process. Refer KB : KB25382 [juniper.net] for same.
  2. Power cycle/Reboot the switch.
  3. If the issue is still observed, please format install the switch using the KB : KB34749 [juniper.net].

 

After following the above steps, if the issue is still observed, we need to replace the switch.

Modification History

2024-05-16 : Article Created

2026-09-30: Updated and externalized