Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 559486 - net scripts error (failed to start /bin/busybox) is misleading when dhcp can not get IP
Summary: net scripts error (failed to start /bin/busybox) is misleading when dhcp can ...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: OpenRC (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: netifrc Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-03 09:26 UTC by Arackhaen
Modified: 2015-10-06 17:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arackhaen 2015-09-03 09:26:05 UTC
When starting wired network interface with net scripts, it fails with error about busybox:

# rc-service net.eth0 start
 * Bringing up interface eth0
 *   dhcp ...
 *     Running udhcpc ...
 *     start-stop-daemon: failed to start `/bin/busybox'     [ !! ]
 * ERROR: net.eth0 failed to start

This is really misleading, while error is really about dhcp-client (possibly not found) or due to bad link (mine was a bad switch).

Sorry if OpenRC was not correct category for this.

Reproducible: Always

Steps to Reproduce:
1. Provide bad link to NIC
2. start net.eth0 ("rc-service net.eth0 start")

Actual Results:  

 * Bringing up interface eth0
 *   dhcp ...
 *     Running udhcpc ...
 *     start-stop-daemon: failed to start `/bin/busybox'     [ !! ]
 * ERROR: net.eth0 failed to start

Expected Results:  
Error message should point users more to check their network connection and dhcp-client, instead of busybox, which is/can be working fine (probably busybox could be the reason also).



I found following links regarding this subject:
https://forums.gentoo.org/viewtopic-p-7416018.html
http://lists.busybox.net/pipermail/busybox-cvs/2011-August/032753.html