Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[M/MX] Syslog message - DAEMON-3-UI_CHILD_SIGNALED: Child received signal: PID X, signal Terminated, command='/sbin/ifinfo

0

0

Article ID: KB37322 KB Last Updated: 16 Jul 2021Version: 1.0
Summary:

This article explains why the syslog message "%DAEMON-3-UI_CHILD_SIGNALED: Child received signal: PID 8903, signal Terminated, command='/sbin/ifinfo'" may be seen on MX Series routers and clarifies that the message can be ignored because there is no associated service impact.

Symptoms:

Sometimes, customers may see the following log messages on the router:

May 27 13:11:16.291 2021  M1-r022-r080-member1-re1 mgd[7530]: %DAEMON-3-UI_CHILD_SIGNALED: Child received signal: PID 8903, signal Terminated, command='/sbin/ifinfo'
Cause:

This log is triggered when you run the show interfaces group of commands, such as show interfaces detail, show interfaces terse, and show interfaces <a specific interface>, and then interrupt the outputs by pressing Ctrl+C before the outputs are fully displayed.

labroot@M1-r022-r080-member1-re1> show interfaces detail      <<< Run 'show interfaces X' command.             
May 27 13:11:14
Physical interface: lc-0/0/0, Enabled, Physical link is Up
  Interface index: 717, SNMP ifIndex: 4598, Generation: 210
  Type: Unspecified, Link-level type: Unspecified, MTU: 0, Clocking: Unspecified, Speed: 800mbps
  Device flags   : Present Running
  Link type      : Unspecified
  Link flags     : None
  Physical info  : Unspecified
  Hold-times     : Up 0 ms, Down 0 ms
  Damping        : half-life: 0 sec, max-suppress: 0 sec, reuse: 0, suppress: 0, state: unsuppressed
  Current address: Unspecified, Hardware address: Unspecified
  Alternate link address: Unspecified
  Last flapped   : Never
  Statistics last cleared: Never
  Traffic statistics:
   Input  bytes  :                    0
   Output bytes  :                    0
   Input  packets:                    0
   Output packets:                    0
   IPv6 transit statistics:
    Input  bytes  :                   0
    Output bytes  :                   0
    Input  packets:                   0
    Output packets:                   0
 
  Logical interface lc-0/0/0.32769 (Index 4876) (SNMP ifIndex 4599) (Generation 4207)
    Flags: Up Encapsulation: ENET2
    Bandwidth: 0
    Traffic statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0
    Local statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0
    Transit statistics:
     Input  bytes  :                    0                    0 bps
---(more)---[abort]. <<< Run Ctrl + C to interrupt the outputs.

After pressing Ctrl+C, the %DAEMON-3-UI_CHILD_SIGNALED: Child received signal: PID X, signal Terminated, command='/sbin/ifinfo' log message can be seen.

May 27 13:11:16.291 2021  M1-r022-r080-member1-re1 mgd[7530]: %DAEMON-3-UI_CHILD_SIGNALED: Child received signal: PID 8903, signal Terminated, command='/sbin/ifinfo'

This is because some of the Junos CLI commands are translated into a corresponding shell command in the shell environment and the ifinfo command is one such shell command. ifinfo is a short-lived process that is created when the show interfaces command is issued via the Junos CLI. When Ctrl+ C is run to abort the show interfaces command, a signal is sent to terminate the shell command as well. The message thus indicates that a signal has been received to terminate the corresponding ifinfo command.

If, on the other hand, you type the ifinfo command in shell mode, the output will be in XML format as shown below:

labroot@M1-r022-r080-member1-re1> start shell user root
May 27 13:14:50
Password:
root@M1-r022-r080-member1-re1:/var/home/labroot # ifinfo xe-1/2/0
<interface-information xmlns="http://xml.juniper.net/junos/17.3R3/junos-interface" junos:style="normal">
<physical-interface>
<name>xe-1/2/0</name>
<admin-status junos:format="Enabled">up</admin-status>
<oper-status>up</oper-status>
<local-index>907</local-index>
<snmp-index>6221</snmp-index>
<link-level-type>Flexible-Ethernet</link-level-type>
<sonet-mode>LAN-PHY</sonet-mode>
<mtu>9100</mtu>
<mru>9108</mru>
<source-filtering>disabled</source-filtering>
<speed>10Gbps</speed>
<bpdu-error>none</bpdu-error>
<ld-pdu-error>none</ld-pdu-error>
<l2pt-error>none</l2pt-error>
<loopback>none</loopback>
<if-flow-control>disabled</if-flow-control>
<pad-to-minimum-frame-size>Disabled</pad-to-minimum-frame-size>
 
<if-device-flags>
<ifdf-present/>
<ifdf-running/>
</if-device-flags>
<ifd-specific-config-flags>
<internal-flags>0x200</internal-flags>
</ifd-specific-config-flags>
<if-config-flags>
<iff-snmp-traps/>
<internal-flags>0x4000</internal-flags>
</if-config-flags>
<if-media-flags>
<internal-flags>0x4808</internal-flags>
</if-media-flags>
<physical-interface-cos-information>
<physical-interface-cos-hw-max-queues>8</physical-interface-cos-hw-max-queues>
<physical-interface-cos-use-max-queues>8</physical-interface-cos-use-max-queues>
<physical-interface-schedulers>0</physical-interface-schedulers>
</physical-interface-cos-information>
<current-physical-address>78:fe:3d:a6:6f:c6</current-physical-address>
<hardware-physical-address>80:71:1f:9a:b8:f7</hardware-physical-address>
<interface-flapped junos:seconds="48054">2021-05-26 23:54:13 CST (13:20:54 ago)</interface-flapped>
<traffic-statistics junos:style="brief">
<input-bps>992</input-bps>
<input-pps>1</input-pps>
<output-bps>0</output-bps>
<output-pps>0</output-pps>
</traffic-statistics>
<active-alarms>
<interface-alarms>
<alarm-not-present/>
</interface-alarms>
</active-alarms>
<active-defects>
<interface-alarms>
<alarm-not-present/>
</interface-alarms>
</active-defects>
<ethernet-pcs-statistics junos:style="verbose">
<bit-error-seconds>2</bit-error-seconds>
<errored-blocks-seconds>2</errored-blocks-seconds>
</ethernet-pcs-statistics>
<link-degrade-information>
<lnk-degrd-mon>Disable</lnk-degrd-mon>
</link-degrade-information>
<interface-transmit-statistics>Disabled</interface-transmit-statistics>
<logical-interface>
<name>xe-1/2/0.32767</name>
<local-index>7278</local-index>
<snmp-index>6223</snmp-index>
<if-config-flags>
<iff-up/>
<iff-snmp-traps/>
<internal-flags>0x4004000</internal-flags>
</if-config-flags>
<link-address junos:format="VLAN-Tag [ 0x0000.0 ] ">[ 0x0000.0 ] </link-address>
<encapsulation>ENET2</encapsulation>
<policer-overhead>
</policer-overhead>
<traffic-statistics junos:style="brief">
<input-packets>382</input-packets>
<output-packets>383</output-packets>
</traffic-statistics>
<filter-information>
</filter-information>
<address-family>
<address-family-name>aenet</address-family-name>
<ae-bundle-name>ae6.32767</ae-bundle-name>
</address-family>
</logical-interface>
</physical-interface>
</interface-information>
Solution:

This log can be safely ignored because there is no associated service impact.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search