LinuxQuestions.org - Ubunt 9.04 slow boot

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - Ubunt 9.04 slow boot (https://www.linuxquestions.org/questions/ubuntu-63/ubunt-9-04-slow-boot-894619/)

Ubunt 9.04 slow boot

Hi there!

My Ubuntu boot very slow and I'm getting the following messages in dmesg which can point to the matter of slowing down the boot process:

Code:

[    5.983058] type=1505 audit(1312030470.538:2): operation="profile_load" pid=483 name=/usr/share/gdm/guest-session/Xsession

[    6.003696] type=1505 audit(1312030470.558:3): operation="profile_load" pid=484 name=/sbin/dhclient3

[    6.004503] type=1505 audit(1312030470.558:4): operation="profile_load" pid=484 name=/usr/lib/NetworkManager/nm-dhcp-client.action

[    6.004975] type=1505 audit(1312030470.558:5): operation="profile_load" pid=484 name=/usr/lib/connman/scripts/dhclient-script

[    6.057519] type=1505 audit(1312030470.608:6): operation="profile_load" pid=485 name=/usr/bin/evince

[    6.069471] type=1505 audit(1312030470.618:7): operation="profile_load" pid=485 name=/usr/bin/evince-previewer

[    6.076404] type=1505 audit(1312030470.628:8): operation="profile_load" pid=485 name=/usr/bin/evince-thumbnailer

[    6.138883] type=1505 audit(1312030470.688:9): operation="profile_load" pid=488 name=/usr/bin/freshclam

[    6.154024] type=1505 audit(1312030470.708:10): operation="profile_load" pid=489 name=/usr/lib/cups/backend/cups-pdf

[    6.154974] type=1505 audit(1312030470.708:11): operation="profile_load" pid=489 name=/usr/sbin/cupsd

[  30.885054] udev: starting version 147

Note the time between the last two lines. I didn't find any information in the internet about what audit is... Any comments and advices are welcome!..

Looking at it, it's not audit (which seems to be some kind of logging utility), but /usr/sbin/cupsd which is slowing you down (look at the ends of the lines). Do you use your printer at all? Because cupsd is your printer daemon.

EDIT: Sorry, I think this will work better for version 9:

Code:

sudo update-rc.d -f cups remove

This will stop it from starting at boot time (hopefully)

Quote:

Originally Posted by Snark1994 (Post 4429423)

Code:

sudo update-rc.d -f cups remove

This will stop it from starting at boot time (hopefully)

Thanks for reply! I don't use printers - this was one of the first services to disable on my laptop. And I don't run auditd either. Here is output

Code:

/home/sapfeer $ pgrep -fl audit



/home/sapfeer $ pgrep -fl cup



/home/sapfeer $ find /etc/rc* -iname \*cup\*

/etc/rc1.d/K80cups

/etc/rc2.d/K80cups

/etc/rc3.d/K80cups

/etc/rc4.d/K80cups

/etc/rc5.d/K80cups

...so unfortunately, that's not my case. It seems that some process like audit is trying to load monitored applications profiles and it tries to find cupsd which is disabled and slows down the boot process

Huh. I've done a bit more research; it's not auditd, it's AppArmour. I'm not entirely sure how to configure it, but this link should help :)

Quote:

Originally Posted by Snark1994 (Post 4429473)

Huh. I've done a bit more research; it's not auditd, it's AppArmour. I'm not entirely sure how to configure it, but this link should help :)

Thanks for reply! Could you please share your way how did you find out that it was apparmor?.. I'm interested on how did you investigate it) But unfortunately, disabling cupsd profile didn't make boot process faster:

Code:

/home/sapfeer $ sudo apparmor_status 

apparmor module is loaded.

4 profiles are loaded.

4 profiles are in enforce mode.

  /usr/lib/connman/scripts/dhclient-script

  /usr/share/gdm/guest-session/Xsession

  /sbin/dhclient3

  /usr/lib/NetworkManager/nm-dhcp-client.action

0 profiles are in complain mode.

1 processes have profiles defined.

1 processes are in enforce mode :

  /sbin/dhclient3 (2153) 

0 processes are in complain mode.

0 processes are unconfined but have a profile defined.

Probably, little more information could make situation clearer:

Code:

4.463935] PM: Marking nosave pages: 0000000000001000 - 0000000000006000

[    4.463939] PM: Marking nosave pages: 000000000009f000 - 0000000000100000

[    4.463944] PM: Basic memory bitmaps created

[    4.473160] PM: Basic memory bitmaps freed

[    4.477163] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[001e8c000170872e]

[    4.510125] kjournald starting.  Commit interval 5 seconds

[    4.510155] EXT3-fs: mounted filesystem with ordered data mode.

[    5.941849] type=1505 audit(1312107574.576:2): operation="profile_load" pid=483 name=/usr/share/gdm/guest-session/Xsession

[    5.962491] type=1505 audit(1312107574.596:3): operation="profile_load" pid=484 name=/sbin/dhclient3

[    5.963310] type=1505 audit(1312107574.596:4): operation="profile_load" pid=484 name=/usr/lib/NetworkManager/nm-dhcp-client.action

[    5.963782] type=1505 audit(1312107574.596:5): operation="profile_load" pid=484 name=/usr/lib/connman/scripts/dhclient-script

[  30.699228] udev: starting version 147

[  30.745031] lp: driver loaded but no devices found

[  30.788719] EXT3 FS on sda2, internal journal

[  30.902619] cfg80211: Calling CRDA to update world regulatory domain

[  30.917811] nvidia: module license 'NVIDIA' taints kernel.

[  30.917815] Disabling lock debugging due to kernel taint

Can my problem be connected to udev?.

Well, I'd seen AppArmour come up as top result in google a couple of times, but had ignored it because I was foolishly sure that auditd was generating them. Eventually I searched for "ubuntu 9 dmesg audit" and the second result was this.

And yes, it seems to be udev. There's a bug report, which is mentioned to affect Lucid/Maverick/Natty. No mention is made of Jaunty/Karmic, but there doesn't seem to be any consensus on what's actually going wrong...

A similar problem is described here, which is solved, but there the pause is after the udev message rather than before. Still, no harm in trying :)

Couple of other suggestions; you're running version 9, which is no longer supported. Have you considered upgrading to at least Maverick? It wouldn't need to replace your current install, you could do it side-by-side until you've checked whether the problem persists. It's probably a good idea anyway, as you're missing out on potentially important updates. If that fails, and the problem is big enough to bother you, I would humbly suggest trying another distro. I eventually got annoyed enough at Ubuntu's speed issues that (after a couple of false starts) I settled on Arch as a nice, relatively easy to use, configurable and fast distribution. Obviously, it's down to personal taste ;)

Best of luck,