ulatency and ulatency-gui doesn't start on Arch

Question

ulatency and ulatency-gui doesn't start on Arch

dragonnn opened this issue 12 years ago · 7 comments

It shows me some python erros:

Traceback (most recent call last):
File "/usr/bin/ulatency", line 1200, in
main()
File "/usr/bin/ulatency", line 1148, in main
tree = Tree(**kwargs)
File "/usr/bin/ulatency", line 445, in init
path = self.get_path()
File "/usr/bin/ulatency", line 498, in get_path
path = CGROUP_MOUNTS.get(self.tree, None)[0]
TypeError: 'NoneType' object has no attribute 'getitem'

Answer 1 · 2013-03-24T20:29:58.000Z

Hi, this seems to be from my fork. I will check this.

Answer 2 · 2013-03-24T20:46:51.000Z

Please attach output from
$ grep cgroup /proc/mounts

Answer 3 · 2013-03-24T20:49:42.000Z

Sure, no problem:
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.sh 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.sh 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.sh 0 0
cgroup /sys/fs/cgroup/bfqio cgroup rw,nosuid,nodev,noexec,relatime,bfqio,release_agent=/usr/lib/ulatencyd/ulatencyd_cleanup.sh 0 0
/sys/fs/cgroup/memory /sys/fs/cgroup/ulatencyd/memory cgroup rw,relatime,name=ulatencyd.memory 0 0
/sys/fs/cgroup/blkio /sys/fs/cgroup/ulatencyd/blkio cgroup rw,relatime,name=ulatencyd.blkio 0 0
/sys/fs/cgroup/bfqio /sys/fs/cgroup/ulatencyd/bfqio cgroup rw,relatime,name=ulatencyd.bfqio 0 0
/sys/fs/cgroup/cpuset /sys/fs/cgroup/ulatencyd/cpuset cgroup rw,relatime,name=ulatencyd.cpuset 0 0

Answer 4 · 2013-03-24T21:16:41.000Z

You seem not to have cpu cgroup subsystem mounted. Is this intentional?

ulatency-gui tries to list cpu tree when it starts and this is hardcoded. I will add detection of cpu tree available and if not, fallback to other one.

Answer 5 · 2013-03-24T21:33:44.000Z

No is isn't intentional, I don't know why it isn't mounted, I am using 3.8.4 kernel with ck, uksm and bfq patchset, systemd version is 198-1. This should be useful:
└─[22:29 nie,24 mar 13:$]→ zcat /proc/config.gz | grep CGROUP
CONFIG_CGROUPS=y
/# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
/# CONFIG_CGROUP_HUGETLB is not set
/# CONFIG_CGROUP_PERF is not set
CONFIG_BLK_CGROUP=y
/# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_BFQIO=y
CONFIG_NET_CLS_CGROUP=y
CONFIG_NETPRIO_CGROUP=m
Seems like 3.8.4 kernel don't have CGROUP_CPUACCT config (it is for cpu cgroup I think)?

Answer 6 · 2013-03-24T22:50:10.000Z

Fixed in ulatency client. I will try to look why cgroup is not mounted on your system later, right now I am constantly disturbing by other duties.

Answer 7 · 2013-03-25T08:14:59.000Z

Thanks ;). Fell free to contact me when you have some questions.