About turning off services?

Hi,
I am new to openSUSE. My system seems to start slowly, about 90 seconds >:(
I use systemd-analyze blame and I see that storage-after-cryptsetup.service and lvm.service take a long time to start. I am thinking about shut those off because as I read, I dont use use encrypted partition.
If my system does not boot because of those, can I make them boot like normal?
I want to make sure before trying :stuck_out_tongue:

Thanks lol!

Hello and welcome here.

Please, allways tell what version of openSUSE you are using when asking questions or explaining problems. The fact that you talk about systemd may lead to the conslusion that you are using 12.1 (andthat only because it is at tthe moment the only supported one with systemd by incident), but it is better that you simply say so then that others have find out by reading your post from top to bottom even before the start to assess your problem.

Also it is allways better to show instead of only to tell. That means that in this case it would probably be better to post the output of your analysing tool. And please, post any computer text beteen CODE tags (http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html), I ask this because that feature is not easy to find, but instrumental in the corrct interpretation of copied/pasted computer text.

Have a look in YaST>System>System services to see if you can turn some of them off there.

On 2012-06-20 17:36, dpdh wrote:
>
> Hi,
> I am new to openSUSE. My system seems to start slowly, about 90 seconds
>> :frowning:
> I use systemd-analyze blame and I see that
> storage-after-cryptsetup.service and lvm.service take a long time to
> start. I am thinking about shut those off because as I read, I dont use
> use encrypted partition.

If they take to long and you are not using lvm nor encripted partition, the
interesting thing would be determining why they take so long and report the
bug or correct the wrong configuration.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Also wold help if you show output of fdisk -l (as root and that is a lower case L not a one)
Maybe you do have a encrypted LVM partition. It would help to know for sure.

Thanks hcw for the guide and others for replying :slight_smile:
It is openSUSE 12.1
Here the output results

systemd-analyze blame


29343ms storage-after-cryptsetup.service
 22496ms lvm.service
 14815ms remount-rootfs.service
 12611ms systemd-vconsole-setup.service
  6668ms bootsplash-startup.service
  6611ms localnet.service
  5354ms media.mount
  5330ms var-run.mount
  5154ms var-lock.mount
  5102ms dev-hugepages.mount
  5083ms udev-trigger.service
  5074ms dev-mqueue.mount
  5050ms sys-kernel-security.mount
  5026ms sys-kernel-debug.mount
  4891ms systemd-remount-api-vfs.service
  3235ms systemd-sysctl.service
  1368ms windows-D.mount
  1151ms windows-C.mount
  1109ms windows-E.mount
  1108ms systemd-logind.service
  1041ms bootsplash-quit.service
   819ms syslog.service
   508ms systemd-readahead-replay.service
   504ms SuSEfirewall2_setup.service
   484ms systemd-readahead-collect.service
   460ms udev.service
   396ms cpufreq.service
   391ms brld.service
   391ms purge-kernels.service
   383ms microcode.ctl.service
   379ms fbset.service
   375ms SuSEfirewall2_init.service
   375ms console-kit-log-system-start.service
   328ms systemd-user-sessions.service
   327ms rc-local.service
   291ms network.service
   232ms avahi-daemon.service
   212ms dbus.service
   204ms NetworkManager.service
   197ms console-kit-daemon.service
   159ms autofs.service
   156ms cups.service
   156ms network-remotefs.service
   141ms xdm.service
   136ms acpid.service
   128ms splash_early.service
   127ms bluez-coldplug.service
   127ms splash.service
   124ms sbl.service
   116ms quota.service
   109ms nscd.service
    75ms systemd-tmpfiles-setup.service
    64ms sshd.service
    24ms sys-fs-fuse-connections.mount

fdisk -l


Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6e186e18

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63   235121094   117560516    7  HPFS/NTFS/exFAT
/dev/sda2       235122688   337522687    51200000    7  HPFS/NTFS/exFAT
/dev/sda3   *   337522688   484200447    73338880    f  W95 Ext'd (LBA)
/dev/sda4       484202496   488397167     2097336   82  Linux swap / Solaris
/dev/sda5       337524736   463892479    63183872    7  HPFS/NTFS/exFAT
/dev/sda6       463894528   484200447    10152960   83  Linux


On 2012-06-21 08:46, dpdh wrote:
>
> Thanks hcw for the guide and others for replying :slight_smile:
> It is openSUSE 12.1
> Here the output results
>
> systemd-analyze blame

I personally prefer “systemd-analyze plot > plotfile.svg”. If you do, post
the svg, do not convert to png.

You should look in the log to find out why those services take so long. If
they are waiting while other services run, then it might not matter.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

I was planning on using system-analyze plot but I got an error

systemd-analyze plot > plotfile.svg
Traceback (most recent call last):
  File "/usr/bin/systemd-analyze", line 113, in <module>
    import cairo, os
ImportError: No module named cairo



Seeing the 29 and 22 secs and your partitioninng table, I am realy interested now if you use LVM. Thus I would like to see he output of

df -h

BTW you do not seem to have a seperate* /home* partition.

On 2012-06-21 11:36, dpdh wrote:

> Oops, I got error
>
> Code:
> --------------------
> systemd-analyze plot > plotfile.svg
> Traceback (most recent call last):
> File “/usr/bin/systemd-analyze”, line 113, in <module>
> import cairo, os
> ImportError: No module named cairo
>
>
>
> --------------------

Wow. No idea…


#!/usr/bin/python
....
elif sys.argv[1] == 'plot':
import cairo, os

someone that knows python may know. I have these installed:


Elanor:~ # rpm -qa | grep -i cairo
python-gobject-cairo-3.0.2-2.3.1.x86_64
libcairo2-1.10.2-14.1.3.x86_64
libcairomm-1_0-1-1.10.0-4.1.3.x86_64
python-cairo-1.10.0-3.1.3.x86_64
libcairo-gobject2-1.10.2-14.1.3.x86_64
libcairo2-32bit-1.10.2-14.1.3.x86_64
Elanor:~ #

I did not select them to be installed myself.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Am 21.06.2012 11:36, schrieb dpdh:
> import cairo, os
> ImportError: No module named cairo
>
Is python-cairo installed? If not install it.


PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

Thanks, I will try to install python-cairo.

Yah, I dont have /home separately, may it cause any problem??


linux-04rx:~ # df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          9.6G  3.9G  5.2G  43% /
devtmpfs        1.5G  8.0K  1.5G   1% /dev
tmpfs           1.5G  1.8M  1.5G   1% /dev/shm
tmpfs           1.5G  788K  1.5G   1% /run
/dev/sda6       9.6G  3.9G  5.2G  43% /
tmpfs           1.5G     0  1.5G   0% /sys/fs/cgroup
tmpfs           1.5G     0  1.5G   0% /media
tmpfs           1.5G  788K  1.5G   1% /var/run
tmpfs           1.5G  788K  1.5G   1% /var/lock
/dev/sda1       113G   86G   27G  77% /windows/C
/dev/sda5        61G   55G  5.5G  92% /windows/E
/dev/sda2        49G   48G  1.8G  97% /windows/D


Thanks for posting. It shows that you indeed do not use LVM.

And no. Not having a seperate* /home *is no problem, not in connection with this case. But it is generaly seen as usefull because you then can install/upgrade your system while keeping all of your users data nicely seperated in a file system that will not change for one bit during that (re)install. It is also the default when installing.
And I personaly value the seperation between system data and the data of the users simply as a neat and secure feature.

On 2012-06-21 18:26, hcvv wrote:
>
> Thanks for posting. It shows that you indeed do not use LVM.

Then he needs to look at the log.

> And no. Not having a seperate- /home -is no problem, not in connection
> with this case. But it is generaly seen as usefull because you then can
> install/upgrade your system while keeping all of your users data nicely
> seperated in a file system that will not change for one bit during that
> (re)install. It is also the default when installing.
> And I personaly value the seperation between system data and the data
> of the users simply as a neat and secure feature.

Absolutely… but he is dedicating less than 10 GB to Linux. In such a case
I don’t recommend a separate /home.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Thanks to martin_helm, I have installed python-cairo

systemd-analyze plot > boot.svg

The file boot.svg is here

Btw, how do you know that I dont use LVM base on the result? And base on error message such as “no module name cairo” like before, how to figure out which package is missing?
(I use yast to find packages with “cairo” and it shows ton of them, dont know what to choose!)
ps: do I ask a lot!?

fdisk -l told us the type of partitions LVM has its own unique number ID

Am 22.06.2012 03:26, schrieb dpdh:
> And base
> on error message such as “no module name cairo” like before, how to
> figure out which package is missing?


martinh@ganymed:~> file /usr/bin/systemd-analyze
/usr/bin/systemd-analyze: a /usr/bin/python script, ASCII text

shows that systemd-analyze is a python script, so it has to be a missing
module in python.
From experience the python modules are in packages named
python-something, from that the conclusion was easy.


PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

As @gogalthorp says: the partition type tells if there is any partition that is ment to be used for LVM. If this is done is something else, but at boot the Kernel will at least check there.

The df -h will show if you have any file system mounted from an LVM logical volume. They will not show as* /dev/sd*…, but as /dev/mapper/…

The second may look as being superfluous after you checked the first. But there are other possibilities to use LVM then based on partitions.

Thanks, I have learn many new things :smiley:

That is the correct spirit! Do not try to much at a time, but asking when you can not follow our strain of thoughts is a good thing to increase knowledge IMHO.