Junos
Highlighted
Junos

UI_CHILD_SIGNALED: Child received signal: PID 77365

‎06-04-2020 09:29 PM

Hi all,

 

- I've found a system log message like this and I find no information about it 😞 

mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo'

 

- Some log messages occurred at the same time:

bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618431
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618437
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618438
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618438
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618441
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618442
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618442
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618444
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618445
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618445
mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo

bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618448
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618450
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618450
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618454
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618455
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618455

 

Hoping someone can help or give me more information, thank you a lot!!

6 REPLIES 6
Highlighted
Junos

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

[ Edited ]
‎06-04-2020 09:44 PM

Hello ,

Good day!

 

mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo'

 

The above log info would mean that the process was taken down. Please check the following.
1. Was it the process been deactivated or restarted through CLI?
2. If not, check if there is any core-file or crash file dumped <show system core-dumps>

 

And in regards to the messages below,

 

bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618431
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618437

 

In Junos OS release 16.1 and later, the MX BRAS added a default syslog message to be displayed if the subscriber management daemon received an unknown packet type. In earlier versions, however, the default behavior was to silently discard the packet. These are informational messages to indicate packet drops, which would otherwise have been silently discarded. If there are no issues with subscriber connectivity or throughput, the messages can be ignored.

 

https://kb.juniper.net/InfoCenter/index?page=content&id=KB33016&actp=METADATA


Regards,
Vishaal


Accept as Solution = cool ! (Help fellow community members with similar query be redirected here instead of them reposting again)
Accept as Solution+Kudo = You are a Star !
Highlighted
Junos

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

[ Edited ]
‎06-04-2020 09:45 PM

Hi n2t,

 

The message "mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo'" indicates that the current mgd daemon is terminated and a new mgd daemon will be initiated. This process does not cause harm to the system as we sometimes also, manually kill daemons and re-initiate them for proper functionality. Here, it was triggered by the system internally. This message could have been triggered due to another event happening in parallel such as reboot/upgrade.

 

I see there are also messages around receiving packets on IFL with unknown protocol type and sending packets with unknown packet types from the logs that you pasted.

 

Hope this helps 🙂

 

Please mark " Accepted Solution" if this helps you solve your queries.

Kudos are always appreciated!

Highlighted
Junos

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

‎06-04-2020 09:47 PM

Hi n2t, 

 

Greetings, 

 

mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo' 
  • As per my understanding, whenever some interface (ifinfo) information related config is changed and the code trying to execute is terminated you observe such logs. 
  • Try matching the process and also understand the config change performed at that point in time.
  • Looking at the other logs this points to something related to pp0 interface.
  • Also check the process related to this. using command:

          show system processes | match 77365

  • These messages are harmless and can be ignored.

 

Hope this helps. Please mark "Accept as solution" if this answers your query. 

 

Kudos are appreciated too! 

 

Regards, 

Sharat Ainapur

Highlighted
Junos
Solution
Accepted by topic author n2t
‎06-05-2020 01:58 AM

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

‎06-05-2020 12:44 AM

Hello n2t,

 

Greetings!.

 

  • Regarding the below log:

mgd[77353]: UI_CHILD_SIGNALED: Child received signal: PID 77365, signal Terminated: 15, command='/sbin/ifinfo'

 

These messages are noticed in the output of the show interfaces command when syslog is configured to include the interactive-commands facility and the info severity:

 

ifinfo is a short-live process that is created when the show interfaces command is issued via the Junos CLI. Some of the Junos CLI commands are associated with the shell command and in this case, the ifinfo command is executed. If you type the ifinfo command in the shell mode, the output will be in the XML format:

 

lab@rollpanna-re0> start shell user root
Password:
root@rollpanna-re0% ifinfo ge-0/0/0
<interface-information xmlns="http://xml.juniper.net/junos/10.3R1/junos-interface" junos:style="normal">
<physical-interface>
<name>ge-0/0/0</name>
<admin-status junos:format="Enabled">up</admin-status>
<oper-status>up</oper-status>
<local-index>144</local-index>
<snmp-index>19217</snmp-index>
<link-level-type>Ethernet</link-level-type>
<mtu>1514</mtu>
<source-filtering>disabled</source-filtering>
<speed>1000mbps</speed>
<bpdu-error>none</bpdu-error>
<l2pt-error>none</l2pt-error>
<loopback>disabled</loopback>
<if-flow-control>enabled</if-flow-control>
<if-auto-negotiation>enabled</if-auto-negotiation>
<if-remote-fault>online</if-remote-fault>
<if-device-flags>
<ifdf-present/>
<ifdf-running/>
</if-device-flags>
<if-config-flags>
<iff-snmp-traps/>
<internal-flags>0x4000</internal-flags>
</if-config-flags>
<if-media-flags>
<ifmf-none/>
</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-cos-information>
<current-physical-address>00:19:e2:b6:a8:00</current-physical-address>
<hardware-physical-address>00:19:e2:b6:a8:00</hardware-physical-address>
<interface-flapped junos:seconds="12032">2010-12-28 12:45:17 JST (03:20:32 ago)</interface-flapped>
<traffic-statistics junos:style="brief">
<input-bps>0</input-bps>
<input-pps>0</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>
</physical-interface>
</interface-information>

 

For more information:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB19675

 

 The above logs are harmless and are at info level severity so you can safely ignore it.

 

  • Regarding the below logs:

 

bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618431
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618432
bbe=smgd[2202]: bbe_if_ppp_input: Rx unknown packet protocol 0x8281 code 0x1 on ifl pp0.3221618437
bbe=smgd[2202]: bbe_if_ppp_output: Tx LCP unknown pkt code 0x4 on ifl pp0.3221618438

 

On an MX Series router that terminates Point-to-Point Protocol (PPP) subscribers, if the subscriber management daemon (bbe-smgd) that handles subscriber connections receives a packet that uses an unknown PPP protocol on the local pp0 interface, it will log a syslog message with the following syntax:

 

These are informational messages to indicate packet drops, which would otherwise have been silently discarded. If there are no issues with subscriber connectivity or throughput, the messages can be ignored.

 

For more info:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB33016&actp=METADATA

 

I hope this helps. Please mark this post "Accept as solution" if this answers your query.

 

Kudos are always appreciated! Smiley Happy

 

Best Regards,

Lingabasappa H

Highlighted
Junos

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

‎06-05-2020 01:59 AM

thank you @shlinga

Highlighted
Junos

Re: UI_CHILD_SIGNALED: Child received signal: PID 77365

[ Edited ]
‎06-05-2020 02:01 AM

Hello n2t,

 

Thanks for accepting my solution. I am glad that my solution helped you to resolve the issue.

 

Regards,

Lingu

Feedback