A start job is running for ifup for eth0

Troubleshooting
1

Hello.
I installed today for the first time Dietpi on a thinclient to control a 3D printer with Octoprint.

Now the boot process is heavily delayed by a job.

IMG_20230612_110802
IMG_20230612_1108021920×1440 241 KB

“a start job is running for ifup for eth0”.
Do I need this?
Thanks

2

This is your network interface. It seems taking quite long to get it up and to have an IP address assigned. Does it finish at some point?

3

Thanks for the answer.
Yes, it stops after approx. 1m13s.
Then it boots normally.
Only a USB wifi stick is connected

4

You can than deactivate your eth0 interface with dietpi-config because you’re not using it.

3 Likes
5

Perfect. Many Thanks.

6

I know it’s an old post, but, I’m facing this issue.

Is there any way to lower the time or disable the check completely? I’m doing a special build using dietpi for a PlayStation 4 Jailbreak. The jailbreak script exploits the ppoe protocol trough a cable connection between the device and PS4 and I need the network interface enabled for the script to work.

1 Like
7

Can you check systemctl status dhcpcd@eth0.

Not sure why it takes so long, maybe it waites for an IP assignment via DHCP? You could try and set the IP to static instead of dhcp.

8

I need it disabled or A way to lower the time… it’s annoying an time consuming.

image
image695×136 2.59 KB

Also did that
image

9

can you check following

journalctl -u ifup*
1 Like
10

I don’t think I even need that to be up. I just want to disable the 5 minute checker…

image
image802×672 32.9 KB

11

Simply assign a static IP or disable the interface if not needed. Actually your system is waiting to receive an IP address via DHCP

12

It has an IP and like I said above the interface has to be enabled for what I’m using it. I just want to lower that time check to like 1-3 sec.

13

The job is running because it wait’s to get an IP via DHCP.
You say, it has an IP. If you configured a static IP but it waits for DHCP assingment then something is off here…
If you lower the time to 3 seconds it will abort and does not get any IP, I think.

Can you share

cat /etc/network/interfaces
14

as already said

15

HI,i have same problem,after modify dhclient.conf,i finally solve it.U can add timeout 10; retry 5; reboot 10; initial-interval 2; select-timeout 5;
in file ’ /etc/dhcp/dhclient.conf’,it reduce half time. if u want to less time,you can decrease the number.
After i read the ifup* log ,i finally find the reason.
It take 1 min to get the IP,because it retry several times

1 Like
16

This usually means that your device is not assigned an IP by the DHCP server. Otherwise there would be no retries.

17

Yes, ifup@eth0.service takes 1 minute only happens when I don’t plug in the network cable. If I plug in the router, it can get the IP address very quickly. But sometimes my device needs to plug in the network cable, and sometimes it doesn’t. Network cable, I hope whether or not the network cable is plugged in will not affect my startup speed.

18

yes this is expected behavior

Did you test if this dietpi-config option makes a difference or not?

Boot wait for network : [On]
19

i tested,this config option not affect ifup@eth0.service.

20

ok thx