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
Disabling networking.service or removing ifupdown would only hide the problem.
Also, before doing so, make sure that another service will take over configuring the loopback interface.
I can confirm that my Debian stable system will configure the loopback interface correctly even if networking.service is enabled with the loopback lines commented out in /etc/network/interfaces
@OP: you should have mentioned that you are running testing/unstable.
drexl@debianWorkstation:~$ sudo journalctl -xe
[sudo] password for drexl:
-- Subject: Unit networking.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit networking.service has begun starting up.
Sep 29 19:38:47 debianWorkstation dhclient[2321]: Internet Systems Consortium DHCP Client 4.3.5
Sep 29 19:38:47 debianWorkstation ifup[2295]: Internet Systems Consortium DHCP Client 4.3.5
Sep 29 19:38:47 debianWorkstation ifup[2295]: Copyright 2004-2016 Internet Systems Consortium.
Sep 29 19:38:47 debianWorkstation ifup[2295]: All rights reserved.
Sep 29 19:38:47 debianWorkstation ifup[2295]: For info, please visit https://www.isc.org/software/dhcp/
Sep 29 19:38:47 debianWorkstation dhclient[2321]: Copyright 2004-2016 Internet Systems Consortium.
Sep 29 19:38:47 debianWorkstation dhclient[2321]: All rights reserved.
Sep 29 19:38:47 debianWorkstation dhclient[2321]: For info, please visit https://www.isc.org/software/dhcp/
Sep 29 19:38:47 debianWorkstation dhclient[2321]:
Sep 29 19:38:47 debianWorkstation ifup[2295]: Cannot find device "eth0"
Sep 29 19:38:47 debianWorkstation dhclient[2321]: Failed to get interface index: No such device
Sep 29 19:38:47 debianWorkstation ifup[2295]: Failed to get interface index: No such device
Sep 29 19:38:47 debianWorkstation ifup[2295]: If you think you have received this message due to a bug rather
Sep 29 19:38:47 debianWorkstation ifup[2295]: than a configuration issue please read the section on submitting
Sep 29 19:38:47 debianWorkstation ifup[2295]: bugs on either our web page at www.isc.org or in the README file
Sep 29 19:38:47 debianWorkstation ifup[2295]: before submitting a bug. These pages explain the proper
Sep 29 19:38:47 debianWorkstation ifup[2295]: process and the information we find helpful for debugging..
Sep 29 19:38:47 debianWorkstation ifup[2295]: exiting.
Sep 29 19:38:47 debianWorkstation dhclient[2321]:
Sep 29 19:38:47 debianWorkstation dhclient[2321]: If you think you have received this message due to a bug rather
Sep 29 19:38:47 debianWorkstation dhclient[2321]: than a configuration issue please read the section on submitting
Sep 29 19:38:47 debianWorkstation dhclient[2321]: bugs on either our web page at www.isc.org or in the README file
Sep 29 19:38:47 debianWorkstation dhclient[2321]: before submitting a bug. These pages explain the proper
Sep 29 19:38:47 debianWorkstation dhclient[2321]: process and the information we find helpful for debugging..
Sep 29 19:38:47 debianWorkstation dhclient[2321]:
Sep 29 19:38:47 debianWorkstation dhclient[2321]: exiting.
Sep 29 19:38:47 debianWorkstation ifup[2295]: ifup: failed to bring up eth0
Sep 29 19:38:47 debianWorkstation systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 19:38:47 debianWorkstation systemd[1]: Failed to start Raise network interfaces.
-- Subject: Unit networking.service has failed
jalisco wrote:I think as L_V mentioned, it's a bug with ifupdown, when it has nothing to do, it kicks back an error, even though everything is fine.
The messages about eth0 you reported have nothing to do with the bug report pointed to by L_V. ifup does not invent non-existing interfaces and tries to configure them with DHCP.
If eth0 is not present in /etc/network/interfaces, it is likely that it is present in a file in the /etc/network/interfaces.d/ directory. You must find and delete this file.
@jalisco
The previous "apt-cache policy" command I asked you to report will not break your system at all, but will just give the current status of ifupdown package in your system, then no worry, you can do it.
To clarify among some confusion around a minor bug, there are at least three ways to manage network connection:
You currently use NetworkManager, your /etc/network/interfaces file is OK, and don't need ifupdown.
Then, if you want to get rid of these errors, just remove ifupdown package, at least to verify, and reinstall it if you want/need it, what you did not mention.
So far, everything seems fine. No more error message.
EDIT: After a few days, every seems fine with rogue network messages. They are gone, and I don't seem to be experiencing any other errors or dependency issues.
Last edited by jalisco on 2018-10-04 18:22, edited 1 time in total.
Great.
BTW, you don't need ifup/ifdown commands from ifupdown package in console mode to manage your connections (it can help without X environment)
The correct command is /bin/ip (from iproute2 package):
(create if needed, configure and activate the interface according to /etc/network/interfaces)
jalisco wrote:Thanks L_V, removing the ifupdown seemed to work.
So far, everything seems fine. No more error message.
You removed the package which installs the service having an error, and the error is gone. What a surprise.
This looks like Maslow's hammer rather than a real solution (find and fix the wrong config file) to me.