Something has happened recently? I never used to have this delay.
Any thoughts on diagnosing/fixing it. This is a short extract of the /var/log/boot.log file.
[32m OK [0m] Started LSB: VirtualBox watchdog daemon.
[32m OK [0m] Started LSB: VirtualBox autostart service.
[32m OK [0m] Started LSB: VirtualBox web service API.
[32m OK [0m] Created slice system-network.slice.
Starting ifup managed network interface enp10s2...
[32m OK [0m] Started ifup managed network interface enp10s2.
******Line Added my me ********* Long Delay Here ********* Timeout of some sort ? *********
[1;31mFAILED[0m] Failed to start LSB: Configure network interfaces and set up routing.
See 'systemctl status network.service' for details.
[32m OK [0m] Reached target Network.
Starting LSB: NFS client services...
[32m OK [0m] Reached target Host and Network Name Lookups.
Starting /etc/init.d/boot.local Compatibility...
[32m OK [0m] Started /etc/init.d/boot.local Compatibility.
[32m OK [0m] Started LSB: NFS client services.
[32m OK [0m] Reached target Remote File Systems (Pre).
[32m OK [0m] Reached target Remote File Systems.
Once booted, I do have a network and the routing is as it should be.
I know that a common answer to this type of question is: “If it is working - why worry”.
But it is not working as I think it should - and I do worry 
(about everything!)
Regards, Martin
Apparently enp10s2 cannot establish a connection and therefore the boot hangs until it times out.
Maybe have a look at the output of:
sudo systemctl status network@enp10s2.service
(I hope that is the correct way to write this… 
)
What network interface do you actually have? ("/sbin/ifconfig", f.e.)
Maybe that is just a stray configuration that should be deleted? (have a look in /etc/sysconfig/network/ and move ifcfg-enp10s2 out of the way if it exists, or remove it in YaST)
Maybe related to: https://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/#sec.131.systemd-networkif ?
You could of course also lower the timeout (“WAIT_FOR_INTERFACES”) in /etc/sysconfig/network/config if you want to, to get a faster boot. But that of course doesn’t fix the underlying issue…
Opps… Should have also added this information:
gzunder:~ # systemctl -l status network.service
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-01-07 11:29:32 GMT; 2min 24s ago
Process: 712 ExecStart=/etc/init.d/network start (code=exited, status=7)
Jan 07 11:29:02 gzunder network[712]: Setting up network interfaces:
Jan 07 11:29:02 gzunder network[712]: lo
Jan 07 11:29:02 gzunder network[712]: lo IP address: 127.0.0.1/8
Jan 07 11:29:07 gzunder network[712]: ..done..doneWaiting for mandatory devices: enp2s0
Jan 07 11:29:32 gzunder network[712]: 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Jan 07 11:29:32 gzunder network[712]: enp2s0 No interface found
Jan 07 11:29:32 gzunder network[712]: ..failedSetting up service network . . . . . . . . . . . . ...failed
Jan 07 11:29:32 gzunder systemd[1]: network.service: control process exited, code=exited status=7
Jan 07 11:29:32 gzunder systemd[1]: Failed to start LSB: Configure network interfaces and set up routing.
Jan 07 11:29:32 gzunder systemd[1]: Unit network.service entered failed state.
gzunder:~ #
So that must be the factor that has changed? But why/who/what thinks that it is a “mandatory” device?
Regards, Martin
PS - I’m “replying” because I can’t find the “Edit” button.
Martin, have a look in Yast at the properties of the network card. If it’s set to start at cable connection, set it to start at boottime.
martinprowe wrote:
> PS - I’m “replying” because I can’t find the “Edit” button.
Don’t ever edit - people using NNTP like me will never see what you
write. So always reply.
You have configuration for interface enp2s0 which is no more present on a system. So network start script timeouts waiting for it. It is mandatory because it is set as such in configuration (if you tell it to start on boot, it will expect device to be present on boot).
Thank you all for your advice.
Yep. That was my problem. I deleted (in fact renamed) a network interface.
That gave me a new /etc/sysconfig/network/<if-name> file BUT left the old one there as well!
Don’t think that I have seen this behaviour before 13.1?
Regards, Martin
On 2014-01-07 16:46, martinprowe wrote:
> Don’t think that I have seen this behaviour before 13.1?
Because 13.1 changed network names.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)