Hi, I hit this issue too. In my case, I found the guilty to be 'nmb' service, which was taking reaaaaally long to start, I still don't know why. I disabled it and everything seems to start normally now. Kind regards, Eduard Huguet 2011/11/18 Anil Seth :

On 11 November 2011 15:07, Sascha Manns wrote:

...

Hi Andreas,

...

When I'm calling systemctl list-jobs is shows about 15 jobs waiting and one job running (network.service).

I had a similar issue on Fedora. It turned out that NetworkManager was managing the ethernet device as well. Network service was not needed. I disabled it and all has been well.

Regards Anil -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Dear Freek de Kruijf, Dear list, I have had IPv6 turned off and a I'm using a statically assigned IPv4 to the only ethernetadapter in the system (Intel 82579V). There is no wireless network adapter available in this system. The only thing that is different on my machine is, that I'm using the bugfixed systemd which fixes the md-raid bug, which keeps the system from booting in some cases.

https://bugzilla.novell.com/show_bug.cgi?id=724912

Greetings Andreas On Fri, Nov 11, 2011 at 10:40, Freek de Kruijf wrote:

On vrijdag 11 november 2011 10:26:50 Andreas Hoffmann wrote:

...

Dear List,

I've discovered another problem with systemd in RC2 of 12.1. After booting the system, the login is available incredibly fast, but it take AGES (at least 4-5 minutes) until all the network-services (xvnc, ssh, smb, nmb) are up and running. When I'm calling systemctl list-jobs is shows about 15 jobs waiting and one job running (network.service). Then after 4-5 minutes the lists clears quite fast, within 20 seconds. After the jobs list cleared, all the required network services are up and running. After the job list cleared I ran systemctl list-units and there the network.service shows 2 times fail. I can start it then with systemctl start network.service and its fast. But even it shows fail fail it seems everything is working. (at least until now I didn't miss any functionality and the system behaves normally).

Did you try to disable IPv6 or only DHCP4 instead of the default DHCP4+DHCP6?

Do you have wireless in your system? So can you elaborate more on the details of your network system.

-- fr.gr.

Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Monday, November 14, 2011 02:30:50 PM Raymond Wooninck wrote:

On Friday 11 November 2011, Andreas Hoffmann wrote:

...

booting the system, the login is available incredibly fast, but it take AGES (at least 4-5 minutes) until all the network-services (xvnc, ssh, smb, nmb) are up and running. When I'm calling systemctl

It seems that you are still lucky that the system comes up. With the current Factory, I have the situation that if NetworkManager can not find a connection (e.g. while being in a plane), the system stops at this point and hangs. Sometimes it continues after 5 minutes, but most of the time it just hangs.

Booting with init=/sbin/sysvinit seems to resolve it (at this moment, although I had in the past that even with using the old boot method, the system came to a halt).

If NM can find a network connection (either wired or wireless), the boot process is indeed fast and without issues. Unfortunately with a laptop you can never be sure if you have a network connection available.

I will report this as a bug.

Regards

Raymond That all seems rather odd as I haven't experienced any network anomalies whatsoever in RC2. But what that is really saying is the bug is more complicated than it may seem on the surface. -- Modern man is the missing link between apes and human beings.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi all, for me I've solved it by changing back to sysvinit which is way more fast for me on my system and less buggy it didn't mess up with my raids which systemd still did 2 times by now, despite of the fix in md.service. With sysvinit my system is up and runnign all services in round about 15 seconds from the time grub starts booting to all services up and running. For systemd it took over 5 minutes until all network services were available. I'll give systemd a next try in 12.2 ;) Thanks all for your help with systemd but its still to new so I'm personally stick with the old sysvinit in the 12.1 release until systemd lost all its initial problems. Sorry for not helping in further debugging but now I need to set up the machine to production and I'm not able to risk any problems with the RAIDs again. Greetings, Andreas On Tue, Nov 15, 2011 at 07:02, Raymond Wooninck wrote:

On Monday 14 November 2011, Roger Luedecke wrote:

...

That all seems rather odd as I haven't experienced any network anomalies whatsoever in RC2. But what that is really saying is the bug is more complicated than it may seem on the surface. --

Hi Roger,

But did you ever tried to boot the system without a network connection ? In the meantime I have found the little bugger and I will discuss the issue further with Frederic Crozat to see how we can resolve it.

Regards

Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org