Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

networking.service exit when one of interface not available during dhcp

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
wpsd2006
Posts: 2
Joined: 2022-05-28 03:31

networking.service exit when one of interface not available during dhcp

#1 Post by wpsd2006 »

Hi I'm just notice something strange.

running Debian 11 in vm.
There is two configuration eth0 and eth1 both are setup using auto dhcp.
Then I remove the second network interface from vm host, and forgot to change the configuraiton.

On start / restart eth0 works ok normally. Then after some time when ttl from dhcp server requesting renewal ( same ip )
due to interface eth1 not found it drop networking.service ( exit state ). restarting the service also doesn't work
Only by restarting the whole vm it will return to normal

Code: Select all

ifup[507]: Cannot find device "eth1"                                                                                                                                         
dhclient[501]: Failed to get interface index: No such device
ifup[501]: Failed to get interface index: No such device
ifup[501]: If you think you have received this message due to a bug rather
ifup[501]: than a configuration issue please read the section on submitting
ifup[501]: bugs on either our web page at www.isc.org or in the README file
ifup[501]: before submitting a bug.  These pages explain the proper
ifup[501]: process and the information we find helpful for debugging.
ifup[501]: exiting.
dhclient[501]: 
dhclient[501]: If you think you have received this message due to a bug rather
dhclient[501]: than a configuration issue please read the section on submitting
dhclient[501]: bugs on either our web page at www.isc.org or in the README file
dhclient[501]: before submitting a bug.  These pages explain the proper
dhclient[501]: process and the information we find helpful for debugging.
dhclient[501]: 
dhclient[501]: exiting.
ifup[456]: ifup: failed to bring up eth1
systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: networking.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Raise network interfaces.
Is this bug in networking service ? shouldn't it just ignore if the interface is not found and continue to enable network

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: networking.service exit when one of interface not available during dhcp

#2 Post by p.H »

wpsd2006 wrote: 2022-05-28 03:41 There is two configuration eth0 and eth1 both are setup using auto dhcp.
This is so wrong (conflicting default routes and DNS...). What is the purpose of such setup ?
wpsd2006 wrote: 2022-05-28 03:41 shouldn't it just ignore if the interface is not found and continue to enable network
Not with "auto" or "allow-auto". It will with "allow-hotplug" instead.

wpsd2006
Posts: 2
Joined: 2022-05-28 03:31

Re: networking.service exit when one of interface not available during dhcp

#3 Post by wpsd2006 »

The config is created automatically when creating the vm. Eth1 has entirely different subnet and vlan i think ( vendor side I don't know about their implementation SDN stuff )

Should take care of the config after removing the nic

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: networking.service exit when one of interface not available during dhcp

#4 Post by p.H »

/etc/network/interfaces is a static file. It's up to the admin (you) to update it when needed.

Post Reply