| Summary: | udhcpc fails with the message: "start-stop-daemon: failed to start `/bin/busybox'" | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | Sten Herrlin <sten.herrlin> |
| Component: | Networking | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | critical | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Sten Herrlin
2011-08-16 22:56:21 UTC
(In reply to comment #0) > Network connection fails on my server because its DHCP client cannot do its > job. My server (as well as most other computer devices) is useless unless > network connection works. > > The failure message: > > # /etc/init.d/net.eth0 restart > * Bringing up interface eth0 > * dhcp ... > * Running udhcpc ... > * start-stop-daemon: failed to start `/bin/busybox' [ !! ] > * ERROR: net.eth0 failed to start I have no idea what /etc/init.d/net.eth0 does. Please provide more information. I'm using the Gentoo linux distribution (www.gentoo.org) which uses init-scripts to manage devices. '/etc/init.d/net.xxx cmd' means I'm calling the init-script for network device xxx (e.g. eth0) to execute "cmd" which can be "start", "stop", "restart"... The reason I encountered this problem seems to be that the DHCP client I used to use: "dhcdbd" has been removed from the gentoo distribution which made the init script fall-back to "udhcpc" implemented in busybox. I have worked my way around the problem by installing "dhcpcd" (originally proposed in the gentoo handbook) so this bug-report can be closed since I no longer care if "udhcpc" works in my environment. Thank you for your help. Reporter doesn't know what "provide more information" means. (In reply to comment #3) > Reporter doesn't know what "provide more information" means. Sorry, didn't mean to be rude. I know you guys do a tremendous job. Feels like I've "provided more information" for all my grown-up life. Still I've asked others to do the same for me. It doesn't calm my frustration though when stuck at a failing system. (In reply to comment #4) > (In reply to comment #3) > > Reporter doesn't know what "provide more information" means. > > Sorry, didn't mean to be rude. I think it's me who was a bit rude :( Sorry. > I'm using the Gentoo linux distribution (www.gentoo.org) which uses init-scripts to manage devices. '/etc/init.d/net.xxx cmd' means I'm calling the init-script for network device xxx (e.g. eth0) to execute "cmd" which can be "start", "stop", "restart"... Yes, I understand this. But I needed more than that. Since I have no access to your system, in these cases you need to dig deeper into those shell scripts. You need to experiment with your system, find where exactly it tries to execute /bin/busybox and emits this message: start-stop-daemon: failed to start `/bin/busybox' In the process you either will understand what the problem is, or will be able to provide more meaningful bug report. |