Creating VLAN always fails and the phosphor network service aborts

Ratan Gupta ratagupt at linux.vnet.ibm.com
Wed Jan 8 22:29:31 AEDT 2020


Hi Troy,

Let me see this, it was working before.I will push a fix for the same.

Regards
Ratan


On 08/01/20 3:43 PM, Troy.Lee at vertiv.com wrote:
>
> Hi Team,
>
> We met an issue that creating a VLAN is always fail, and the 
> phosphor-network-manager/systemd-networkd are caught abort signal.
>
> Does anyone have any thought about this?
>
> root@ ast2500evb:~# ps | grep network
>
> 4432 root      8804 S    phosphor-network-manager
>
> 4444 systemd- 16828 S    /lib/systemd/systemd-networkd
>
> root@ ast2500evb:~# busctl --no-pager call xyz.openbmc_project.Network \
>
> /xyz/openbmc_project/network \
>
> xyz.openbmc_project.Network.VLAN.Create \
>
>                                    VLAN su "eth0" 123
>
> Call failed: Remote peer disconnected
>
> root@ ast2500evb:~# ps | grep network
>
> 4489 root      8804 S    phosphor-network-manager
>
> 4500 systemd-  1448 R    /lib/systemd/systemd-networkd
>
> Journal log has the following error:
>
> Jan 01 00:21:10 ast2500evb phosphor-network-manager[4432]: Refreshing 
> the objects.
>
> Jan 01 00:21:11 ast2500evb phosphor-network-manager[4432]:ioctl failed 
> for SIOCETHTOOL:
>
> Jan 01 00:21:11 ast2500evb phosphor-network-manager[4432]: ioctl 
> failed for SIOCETHTOOL:
>
> Jan 01 00:21:11 ast2500evb phosphor-network-manager[4432]: Refreshing 
> complete.
>
> Jan 01 00:21:13 ast2500evb phosphor-network-manager[4432]: ioctl 
> failed for SIOCGIFHWADDR:
>
> Jan 01 00:21:13 ast2500evb phosphor-network-manager[4432]: terminate 
> called after throwing an instance of 
> 'sdbusplus::xyz::openbmc_project::Common::Error::InternalFailure'
>
> Jan 01 00:21:13 ast2500evb phosphor-network-manager[4432]: what():  
> xyz.openbmc_project.Common.Error.InternalFailure: The operation failed 
> internally.
>
> Jan 01 00:21:13 ast2500evb phosphor-network-manager[4432]: The 
> operation failed internally.
>
> Jan 01 00:21:13 ast2500evb systemd[1]: 
> xyz.openbmc_project.Network.service: Main process exited, code=killed, 
> status=6/ABRT
>
> Jan 01 00:21:13 ast2500evb systemd[1]: 
> xyz.openbmc_project.Network.service: Failed with result 'signal'.
>
> Jan 01 00:21:14 ast2500evb systemd[1]: 
> xyz.openbmc_project.Network.service: Service RestartSec=1s expired, 
> scheduling restart.
>
> Jan 01 00:21:14 ast2500evb systemd[1]: 
> xyz.openbmc_project.Network.service: Scheduled restart job, restart 
> counter is at 3.
>
> Jan 01 00:21:14 ast2500evb systemd[1]: Stopped Phosphor Network Manager.
>
> Jan 01 00:21:14 ast2500evb systemd[1]: Starting Phosphor Network 
> Manager...
>
> Jan 01 00:21:14 ast2500evb systemd[1]: Started Phosphor Network Manager.
>
> Jan 01 00:21:17 ast2500evb systemd[1]: Stopping Network Service...
>
> Jan 01 00:21:18 ast2500evb systemd[1]: systemd-networkd.service: 
> Succeeded.
>
> Jan 01 00:21:18 ast2500evb systemd[1]: Stopped Network Service.
>
> Jan 01 00:21:18 ast2500evb systemd[1]: Starting Network Service...
>
> Thanks,
>
> Troy Lee
>
> CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it 
> are intended solely for the use of the individual or entity to whom 
> they are addressed and may contain confidential and privileged 
> information protected by law. If you received this e-mail in error, 
> any review, use, dissemination, distribution, or copying of the e-mail 
> is strictly prohibited. Please notify the sender immediately by return 
> e-mail and delete all copies from your system. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200108/730ee832/attachment-0001.htm>


More information about the openbmc mailing list