Newbie here. I’ve been using Ubuntu. It boots up fairly fast (around 20 or 30 seconds). Opensuse takes a couple minutes to boot up. Is something wrong?
Related question: is there a log file viewer?
My 12.1 _64 stock kde - from grub to login screen, less than 10 secs - login > desktop 10 secs
Is in one of the repos
Index of /distribution/12.1/repo/oss/suse
Install it then remove the repo
+1 here for caf4926
Thanks for the replies. It is good to know the potential for a fast boot is there. I did this:
sudo zypper install bootchart
That worked. But why would I want to remove that repo?
> zypper lr
| Alias | Name | Enabled | Refresh
–±------------------±---------------------------±--------±-------
1 | repo-debug | openSUSE-12.1-Debug | No | Yes
2 | repo-debug-update | openSUSE-12.1-Update-Debug | No | Yes
3 | repo-non-oss | openSUSE-12.1-Non-Oss | Yes | Yes
4 | repo-oss | openSUSE-12.1-Oss | Yes | Yes
5 | repo-source | openSUSE-12.1-Source | No | Yes
6 | repo-update | openSUSE-12.1-Update | Yes | Yes
I’m reading the bootchart instructions. What are the minimal install steps I need to use in opensuse? I’m not going to enable process accounting. I will install JDK and ant later, but for now, I will use the web renderer. I just want to do the minimal steps to diagnose this boot issue at the moment. Thanks.
But why would I want to remove that repo?
It’s OK leave it I was mixed up
OSS is fine
In my search it looked different
On 2012-01-16 05:36, caf4926 wrote:
>
> My 12.1 _64 stock kde - from grub to login screen, less than 10 secs -
> login > desktop 10 secs
>
> ‘Bootchart’ (http://www.bootchart.org/)
You don’t need it in 12.1, you have a boot chart natively.
systemd-analyze plot > bootchart.svg
then view the chart.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Wow, very nice! Thanks. I guess I can do
zypper rm bootchart
now.
From looking at the chart, the things taking a long time are my NFS mounts. My Ubuntu machine has the same NFS mounts on the same server and it boots in 20 to 30 seconds instead of a couple minutes. Hopefully, there is some tuning I can do on this OpenSuse client. The mounts were set up at install time. Here’s /etc/fstab
cat /etc/fstab
LABEL=Root / ext4 noatime,acl,user_xattr,discard 1 1
LABEL=Home /home ext4 acl,user_xattr 1 2
192.168.1.1:/shared /shared nfs4 noatime 0 0
tmpfs /tmp tmpfs noatime,size=8% 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
The only other really long process in the boot chart is NetworkManager-wait-online.service. Any ideas how to resolve that? In general, networking on this OpenSuse box seems slower than networking on my Ubuntu box. Web pages take longer to load, for example. But the wait seems to be in the lookup phase. Speedtest.net shows that my download speeds are the same (around 30 Mbps on Comcast cable).
Problem is that the mount is attempted before the network is up.
Try pressing F3 at boot and changing to a systemV boot SystemD is now the default but it has issues. There are several recent thread related to this with much more detail.
Right sorry about that F5
typo 
Wow, that sounds like quite some problem. I read the links below and some others and it would take me quite some time to fully understand this issue. However, this SystemD issue explains a lot of the problems I’m seeing with my networking and mounts (and the slow boot). Now, suddenly, it is all starting to make sense.
I knew that making the move to OpenSuse in the middle of a project would be a tough challenge, but after all of the issues I’m seeing I am starting to think I bit off more than I can handle right now. And I understand that paid support is not available for the OpenSuse version of Suse. It looks like I’ve got a tough decision to make: stay the course and switch to OpenSuse or retreat to more familiar ground.
The funny thing is that I ran the LiveDVD for a couple days and didn’t see any of these issues. They all showed up only after I did the install.
Running commands (that depend on a process being started) in after.local
http://forums.opensuse.org/english/other-forums/development/programming-scripting/469832-running-commands-depend-process-being-started-after-local.html
BUG: nmb on + systemd + more than 1 ethernet card.
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/469461-bug-nmb-systemd-more-than-1-ethernet-card.html#post2418061
12.1_F5_sysV.jpg (JPEG Image, 2048 × 1536 pixels) - Scaled (63%)
https://dl.dropbox.com/u/10573557/12.1_Misc/12.1_F5_sysV.jpg
Bug 725503 – multiminute hang/delay during systemd boot
https://bugzilla.novell.com/show_bug.cgi?id=725503
Bug 731308 – systemd deadlocks starting network on if-up.d/21-dhcpcd-hook-samba
https://bugzilla.novell.com/show_bug.cgi?id=731308
add_systemV1.jpg (JPEG Image, 1363 × 732 pixels) - Scaled (97%)
https://dl.dropbox.com/u/10573557/systemV/add_systemV1.jpg
add_systemV2.jpg (JPEG Image, 1364 × 732 pixels) - Scaled (97%)
https://dl.dropbox.com/u/10573557/systemV/add_systemV2.jpg
Problem with Samba in openSUSE 12.1 re systemd
http://forums.opensuse.org/english/get-technical-help-here/network-internet/468521-problem-samba-opensuse-12-1-re-systemd.html
Bug 735943 – If NMB is enabled while booting in systemd on system with several ethernet cards, only the first card gets IP address
https://bugzilla.novell.com/show_bug.cgi?id=735943
System V as default Init Program
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/470045-system-v-default-init-program.html
F5 System V . Should be on install menu and notes and on download page!
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/469800-f5-system-v-should-install-menu-notes-download-page.html
This no longer works for me. I guess that would be expected after switching to sysvinit …
On 2012-01-17 07:46, MountainX wrote:
>> then view the chart.
>> >
>> >
> This no longer works for me. I guess that would be expected after
> switching to sysvinit …
Absolutely, it is a feature of systemd.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-01-17 04:16, MountainX wrote:
> From looking at the chart, the things taking a long time are my NFS
> mounts. My Ubuntu machine has the same NFS mounts on the same server and
> it boots in 20 to 30 seconds instead of a couple minutes. Hopefully,
> there is some tuning I can do on this OpenSuse client. The mounts were
> set up at install time. Here’s /etc/fstab
>
>
> Code:
> --------------------
>
> cat /etc/fstab
> 192.168.1.1:/shared /shared nfs4 noatime 0 0
>
> --------------------
You can add the option “_netdev”, so that the mount script does not attempt
to mount the network share before the network is up.
> The only other really long process in the boot chart is
> NetworkManager-wait-online.service. Any ideas how to resolve that?
Why do don’t you use if-up? Assuming you are connected by cable, don’t use
network manager.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I read that the option “_netdev” has no affect yet (because it remains “to be implemented”) in NSFv4. Is that true? Here’s the ref:
Note that _netdev only works with nfs version 3 and before. nfs4 ignores this option.
https://help.ubuntu.com/community/SettingUpNFSHowTo
Good suggestion. I’ll try switching back. The reason I tried network manager is that, while OpenSuse had been fine when running from the LiveDVD, once I installed it I started seeing a number of network related issues. I just tried a few things to resolve it and switching to network manager was something that worked.
Now I am learning that these SystemD issues may be related to my networking problems. Furthermore, my system has 2 intel Gigabit NICs and I think I saw some posts mentioning bugs related to two NICs. Maybe that is affecting me too. Getting OpenSuse to work on my computer is becoming quite complicated.
The biggest problem at this moment is that my NFS mounts no longer “work”. The only change I made was to switch to sysvinit in response to this thread. I have not changed /etc/fstab nor have I changed anything on the server. When I attempt to open an NFS mount in Dolphin I get the error "An error occured while accessing ‘mount_name’, the system responded: mount: only root can mount ‘mount_name’
Is there an easy fix for this so that I don’t have to manually mount all my NFS exports now? Thank you.
It looks to be working… (fingers crossed)
Summary of what I learned:
- default settings (systemd, ifup) plus NFS client doesn’t seem to work (I saw a host of problems)
- systemd + network manager + NFS client works but booting up is extremely slow
- sysvinit + network manager + NFS client doesn’t work well - the NFS shares are not mounted at boot time
-
sysvinit + ifup + NFS client does work
. This combo might have solved my problems.
Without mounting NFS shares my boot time is about 8-9 seconds for phase 1 and another 8-9 seconds for the 2nd part.
With NFS shares the second part increases about 5 seconds. But this is much better than a couple minutes to boot up, as I was seeing when I started this thread.
Thanks for the help!
On 2012-01-17 22:16, MountainX wrote:
> I read that the option “_netdev” has no affect yet (because it remains
> “to be implemented”) in NSFv4. Is that true? Here’s the ref:
>
>> Note that _netdev only works with nfs version 3 and before. nfs4
>> ignores this option.
>> https://help.ubuntu.com/community/SettingUpNFSHowTo
It’s news to me. No idea. I learnt about that parameter not long ago.
On 2012-01-18 00:16, MountainX wrote:
>
> It looks to be working… (fingers crossed)
>
> Summary of what I learned:
>
>
> - default settings (systemd, ifup) plus NFS client doesn’t seem to
> work (I saw a host of problems)
> - systemd + network manager + NFS client works but booting up is
> extremely slow
I would expect it to not work at all…
> - sysvinit + network manager + NFS client doesn’t work well - the NFS
> shares are not mounted at boot time
Expected
> - sysvinit + ifup + NFS client does work. This combo might have
> solved my problems.
So, what you haven’t tried is systemd + ifup. Ah, yes, you did, first
paragraph. Dunno what to say, not knowing what those problems were. It
works for me (I have a bugzilla on a related problem).
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Can anyone point me to the bug report for this? I want to follow it so I can know when it has been resolved.
I just read this:
The systemd fallacy | monolight
Also, this:
Suse is in the process of adopting [systemd], but it’s not a user-driven change at all. Just a few developers/maintainers are pushing the change, and a very few fan-boy users who just cheer whatever the devs do without really having an opinion of their own that’s based on any technical arguments, and most users who say anything on the topic at all, hate it.
For now systemd works ok on suse for the utterly typical desktop most of the time, and server admins know how to manually revert to sysv since both packages are still packaged and supported for this release, and regular users that have problems are generally told by other users how to switch back to sysv and that always fixes the problem.
That last part was exactly what happened to me, as evidenced by this thread.
Does anyone care to comment on whether systemd will continue to be the future for OpenSuse?