On 11/28/2011 01:06 PM, elksi wrote:
>
> Thanks i will try it.
>
> I have just discovered that i have a similar issue with my home server.
> It is running 12.1 (upgraded from 11.4) with no nfs mounts but with nfs
> server. It has a slow boot as well and i’m getting the following:
>
>
> Code:
> --------------------
> systemctl status network.service
> network.service - LSB: Configure the localfs depending network interfaces
> Loaded: loaded (/etc/init.d/network)
> Active: failed since Mon, 14 Nov 2011 23:02:29 +0200; 2 weeks and 0 days ago
> Process: 719 ExecStart=/etc/init.d/network start (code=killed, signal=TERM)
> CGroup: name=systemd:/system/network.service
> --------------------
>
>
> Although network is working.
>
>
> Code:
> --------------------
> romantsa:~ # systemd-analyze time
> Startup finished in 12836ms (kernel) + 347599ms (userspace) = 360435ms
> romantsa:~ # systemd-analyze blame
> 35983ms ntp.service
> 27093ms yastwc.service
> 23801ms webmin.service
> 23170ms mysql.service
> 8263ms nfsserver.service
> 6247ms smb.service
> 5044ms storage-after-cryptsetup.service
> 4536ms lvm.service
> 4432ms squid.service
> 2871ms remount-rootfs.service
> 2405ms cpufreq.service
> 2404ms purge-kernels.service
> 2401ms systemd-logind.service
> 2327ms nmb.service
> 1908ms bootsplash-startup.service
> 1864ms systemd-vconsole-setup.service
> 1832ms auditd.service
> 1788ms sshd.service
> 1647ms deluged.service
> 1404ms ddclient.service
> 1402ms localnet.service
> 1341ms yastws.service
> 1100ms cycle.service
> 975ms pure-ftpd.service
> 945ms var-lock.mount
> 941ms var-run.mount
> 937ms network-remotefs.service
> 909ms media.mount
> 900ms sys-kernel-debug.mount
> 896ms dev-mqueue.mount
> 888ms sys-kernel-security.mount
> 884ms dev-hugepages.mount
> 774ms mcelog.service
> 642ms console-kit-daemon.service
> 627ms collectd.service
> 623ms nscd.service
> 599ms deluge-webd.service
> 571ms syslog.service
> 546ms irq_balancer.service
> 540ms systemd-readahead-collect.service
> 521ms cifs.service
> 511ms systemd-sysctl.service
> 489ms systemd-remount-api-vfs.service
> 444ms splash.service
> 400ms udev.service
> 399ms udev-trigger.service
> 283ms rpcbind.service
> 255ms apache2.service
> 246ms dbus.service
> 229ms nfs.service
> 228ms systemd-tmpfiles-setup.service
> 210ms snmpd.service
> 155ms splash_early.service
> 136ms acpid.service
> 79ms console-kit-log-system-start.service
> 66ms systemd-user-sessions.service
> 57ms srv.mount
> 33ms rc-local.service
> 33ms bootsplash-quit.service
> 25ms fbset.service
> --------------------
>
>
> It hasn’t been rebooted since the upgrade but i remember that it took a
> lot time to reboot and i had to take a monitor a keyboard to go to the
> basement and find out that it was working. So i suspect that again
> network service had timeout. I will reboot it some time tomorrow a
> report.
Certainly 360 sec to boot is excessive. When I switched to autofs for my NFS
volumes, my time reduced from 100 sec to 40 sec.
Most of your long times involve the network startup. Is there something funky
there? Is mysql also involved with the network too?
Your system waits almost 36 sec to start ntp. Assuming your server only boots to
level 3, what does ‘ls /etc/init.d/rc3.d/*ntp’ yield? Is it being started too
early? I should think that S99ntp would be appropriate.