systemd-analyze critical chain some wrong...

gor0 · 02-04-2015, 06:28 AM

Code:

# systemd-analyze critical-chain
The time after the unit is active or started is printe
The time the unit takes to start is printed after the 

graphical.target @1min 12.265s
`-multi-user.target @1min 12.265s
  `-wicd.service @1min 2.067s +10.197s
    `-basic.target @1min 2.064s
      `-sockets.target @1min 2.064s
        `-dbus.socket @1min 2.064s
          `-sysinit.target @1min 2.063s
            `-systemd-update-utmp.service @1min 2.013s
              `-systemd-tmpfiles-setup.service @1min 1
                `-systemd-journal-flush.service @56.81
                  `-systemd-journald.service @1.660s +
                    `-systemd-journald.socket @1.504s
                      `--.slice @1.235s
lines 1-16/16 (END)...skipping...
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 12.265s
`-multi-user.target @1min 12.265s
  `-wicd.service @1min 2.067s +10.197s
    `-basic.target @1min 2.064s
      `-sockets.target @1min 2.064s
        `-dbus.socket @1min 2.064s
          `-sysinit.target @1min 2.063s
            `-systemd-update-utmp.service @1min 2.013s +46ms
              `-systemd-tmpfiles-setup.service @1min 1.796s +216ms
                `-systemd-journal-flush.service @56.816s +4.976s
                  `-systemd-journald.service @1.660s +55.153s                                                                         
                    `-systemd-journald.socket @1.504s                                                                                 
                      `--.slice @1.235s

*wicd service on RED...

someone versed on Arch and systemd can look that?

tia!

Head_on_a_Stick · 02-04-2015, 07:03 AM

It could be that your systemd log files are huge; check the size of /var/log/journal

You can limit log size by modifying /etc/systemd/journald.conf
https://wiki.archlinux.org/index.php...nal_size_limit

See man journald.conf

gor0 · 02-04-2015, 02:38 PM

Dude...is this 'normal' ?

just 2 files on /var/log/journal ??

Head_on_a_Stick · 02-04-2015, 02:46 PM

Quote:

Originally Posted by gor0

Dude...is this 'normal' ?

just 2 files on /var/log/journal ??

That's what mine looks like

They are folders -- the logs are in the one named with a long alphanumeric string.

How big is the folder on the left?

Mine is 123.7MiB ATM.

If yours is several GiB then that's why systemd is taking so long to boot -- delete the contents (if you have no outstanding issues on your system) and modify your /etc/systemd/journald.conf to limit the size as set out in my link above and described more fully in man journald.conf

gor0 · 02-04-2015, 06:36 PM

Quote:

Originally Posted by Head_on_a_Stick

They are folders -- the logs are in the one named with a long alphanumeric string.

How big is the folder on the left?

Mine is 123.7MiB ATM.

If yours is several GiB then that's why systemd is taking so long to boot -- delete the contents (if you have no outstanding issues on your system) and modify your /etc/systemd/journald.conf to limit the size as set out in my link above and described more fully in man journald.conf

Yep,it is the logs folders: 456.0 MiB ,12 files,0 subfolders

I'd like to erase that folder...

Head_on_a_Stick · 02-05-2015, 01:33 AM

Quote:

Originally Posted by gor0

I'd like to erase that folder...

Just delete the contents.

Make sure your system is functioning properly first though...

gor0 · 02-05-2015, 04:06 PM

sorry 4 botherin u...

can I erase all of that?

tia!

Head_on_a_Stick · 02-05-2015, 04:09 PM

Yes I'm pretty sure it will all be re-created by systemd; just move them to a different location if you're worried -- you can always just move them back if there's a problem.