I originally submitted a bug report about this on bugzilla.kernel. The only way to solve it is to make sure my hostname in /etc/hosts is behind the real network address, not the local loopback (the default for e.g. I think systemd should make sure that loopback is fully setup and has a valid ip assigned before network.target finishes since systemd already takes up the job of bringing up the loopback interface. These loopback IP addresses are managed entirely by and within the operating system and enable testing of communications in client-server architecture systems on a single machine. I recently tried to dig linux source and found that it tries to add the ip after inetdev_event event is triggered, so i think maybe on a slow machine the event is not triggered in time? In IPv4 the range 127.0.0.0 127.255.255.255 is reserved for loopback, i.e. My friend also has the problem when starting transmission-daemon on boot which tries to bind to 127.0.0.1 (he has a Intel Pentium Dual E2180 2GHz, 1996MiB DDR2 RAM), we didn't know what was causing this services to fail half the time and were confused since 127.0.0.1 was available when system was already fully booted and we didn't know how it worked and how lo was setup in first place. I run a znc service which starts after network.target, it has a configured port that binds on the 127.0.0.1 ip so that it's only available locally and it fails to start some times because the machine is slow (core (I) duo T2350 1.86GHz), and sometimes still doesn't have the ip address assigned to lo after network.target has been reached. On a slow machine the kernel might not add the ip address to the lo interface in time for the services that might try to bind to it are run. So that means you do not need a NIC to be able to ping your loopback addresses. The loopback interface allows IT professionals to test IP software without worrying about broken or corrupted drivers or hardware. Systemd takes care of setting up loopback interface as part of it's main() functionīut it doesn't ensure that ip address (127.0.0.1) has been assigned to lo interface when running services. The loopback interface has no hardware associated with it, and it is not physically connected to a network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |