Error at boot, receive_packet failed on eth0: Network is down

Question

I have noticed the following seems to be present in my /var/log/errors.log. The ntpd.... seems to have been present on and off for a while but "plamuk dhcpcd[5789]: eth0: read: Network is down" seems to have only started occuring recently and I've noticed this error on screen at the final stage off boot up, just before going to graphical kdemod login. I would add that my network is working perfectly and more stable at the moment than ever (wireless only). Just wondered if anyone sees anything similar, or any ideas how clear it up.
Dec 25 08:18:51 plamuk dhclient: receive_packet failed on eth0: Network is down
Dec 25 08:18:51 plamuk dhcpcd[5789]: eth0: read: Network is down
Dec 25 08:19:43 plamuk ntpd[5625]: Cannot find existing interface for address 217.147.208.1
Dec 25 08:19:43 plamuk ntpd_initres[5626]: ntpd indicates no data available!
Dec 25 08:20:43 plamuk ntpd[5625]: Cannot find existing interface for address 217.147.208.1
Dec 25 08:20:43 plamuk ntpd_initres[5626]: ntpd indicates no data available!
Dec 25 08:21:43 plamuk ntpd[5625]: Cannot find existing interface for address 217.147.208.1
Dec 25 08:21:43 plamuk ntpd_initres[5626]: ntpd indicates no data available!
Dec 25 08:22:43 plamuk ntpd[5625]: Cannot find existing interface for address 217.147.208.1
Dec 25 08:22:43 plamuk ntpd_initres[5626]: ntpd indicates no data available!

Answer 1

Trilby wrote:
Torxed wrote:execve (/sbin/dhclient-script, ...): No such file or directory
There you go.  What's calling that?  That should resolve to /usr/bin/sbin.
What does `ls -l /sbin/dhclient-script` return?  Did you complete the recent filesystem upgrade without errors.
[elias@ubercool ~]$ ls -l /sbin/dhclient-script
-rwxr-xr-x 1 root root 12295 May 31 15:48 /sbin/dhclient-script
And yes i've successfully updated the filesystem with out any errors, oddly enough this script is sticking to the guns and satying in /sbin/ (thought all scripts and what not moved to /usr/{sbin, bin} but i guess not?)
fukawi2 wrote:Please do not post large pictures
Sorry about that, i knew there was a limit but there's so much rules to keep track of so i used "common sense" and i thought my image was at least not tremendously hughe.. but i guess that depends on what sort of connection and PC you got.
jrussell wrote:
try just
systemctl start dhcpcd
Won't do any good, considering i've already tried it (read the title and description of the issue).
Last edited by Torxed (2013-06-26 20:19:07)