LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page cgmanager not starting -current
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 05-20-2016, 08:29 PM   #1
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
cgmanager not starting -current

Code:
root@hp635:~# ps -ef | grep cgmanager
root      2536  2305  0 20:19 pts/0    00:00:00 grep cgmanager
root@hp635:~# /etc/rc.d/rc.cgmanager start
Starting cgmanager:  /usr/sbin/cgmanager --daemon
cgmanager:cgmanager.c:1522: Assertion failed in main: server != NULL
/etc/rc.d/rc.cgmanager: line 10:  2545 Aborted                 /usr/sbin/cgmanager --daemon
root@hp635:~#
I have two machines running -current. Both show this behavior.
Last edited by Richard Cranium; 05-20-2016 at 08:31 PM.
 
Old 05-20-2016, 08:57 PM   #2
glorsplitz
Senior Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 1,308

Rep: Reputation: 368Reputation: 368Reputation: 368Reputation: 368
all up to date current 64 vbox vm, I see this, just after boot

# ps -ef | grep cgmanager
root 665 1 0 21:54 ? 00:00:00 /usr/sbin/cgmanager --daemon
root 1357 1343 0 21:55 pts/0 00:00:00 grep cgmanager

# /etc/rc.d/rc.cgmanager stop
Stopping cgmanager.
Terminated

# /etc/rc.d/rc.cgmanager start
Starting cgmanager: /usr/sbin/cgmanager --daemon

# ps -ef | grep cgmanager
root 1373 1 0 21:55 ? 00:00:00 /usr/sbin/cgmanager --daemon
root 1375 1343 0 21:55 pts/0 00:00:00 grep cgmanager
 
Old 05-20-2016, 08:58 PM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
it's stated runnning on VM here
Code:
ps aux | grep cgmanager
root       608  0.0  0.0  15316     4 ?        S    May17   0:00 /usr/sbin/cgmanager --daemon
willysr  13803  0.0  0.0   9640  1856 pts/2    S+   08:57   0:00 grep cgmanager
 
Old 05-20-2016, 09:03 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
I'm not running in VM. cgmanager is supposed to run on the host, according to https://linuxcontainers.org/cgmanager/introduction/
 
Old 05-20-2016, 10:13 PM   #5
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 914

Rep: Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619
Quote:
Originally Posted by Richard Cranium View Post
Code:
root@hp635:~# ps -ef | grep cgmanager
root      2536  2305  0 20:19 pts/0    00:00:00 grep cgmanager
root@hp635:~# /etc/rc.d/rc.cgmanager start
Starting cgmanager:  /usr/sbin/cgmanager --daemon
cgmanager:cgmanager.c:1522: Assertion failed in main: server != NULL
/etc/rc.d/rc.cgmanager: line 10:  2545 Aborted                 /usr/sbin/cgmanager --daemon
root@hp635:~#
I have two machines running -current. Both show this behavior.
Are the machines running a complete installation, in particular dbus?
From cgmanager.c:
Code:
        /* Setup the DBus server */
        server = nih_dbus_server (CGMANAGER_DBUS_PATH, client_connect,
                                  client_disconnect);
        nih_assert (server != NULL);
where 'nih_assert (server != NULL);' is at the line 1522 where cgmanager aborted.

chris
 
Old 05-21-2016, 10:15 AM   #6
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Yep...
Code:
cranium@hp635:/var/log/packages$ ls dbus-*               
dbus-1.10.8-x86_64-1  dbus-glib-0.106-x86_64-1  dbus-python-1.2.4-x86_64-1
cranium@hp635:/var/log/packages$  ps -ef | grep dbus
message+  1159     1  0 May20 ?        00:00:06 /usr/bin/dbus-daemon --system
cranium   1725     1  0 May20 ?        00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session
cranium   1726     1  0 May20 ?        00:00:09 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
cranium   1912  1897  0 May20 ?        00:00:01 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
cranium  15925 15434  0 10:06 pts/0    00:00:00 grep dbus
cranium@hp635:/var/log/packages$
I always do the complete installation drill.
 
Old 05-21-2016, 11:36 AM   #7
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
I applied last night's updates and am now running kernel 4.4.11. After reboot, cgmanager still doesn't start.

strace -f /usr/sbin/cgmanager tells me that it is looking for the file /sys/fs/cgroup/cgmanager/sock, which is supposed to be created by the call quoted by chris.willing, above.

Digging in /var/log/syslog gives me...
Code:
May 21 10:44:10 hp635 console-kit-daemon[1240]: WARNING: Failed to open connection to cgmanager. Is the cgmanager daemon running?
Now, /sys/fs/cgroup/cgmanager is in a cgroup filesystem which doesn't appear to allow random file creation. Certainly 'touch /sys/fs/cgroup/cgmanager/sock' as root fails with "permission denied". (Yes, I know that's not how you make a unix socket. I was trying to see what error messages that would generate when I attempted to run cgmanager again.)
 
Old 05-21-2016, 12:44 PM   #8
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,090

Rep: Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173Reputation: 4173
I would check if rc.S (that takes care of mounting the cgroup subsystems) is the latest version: eventually reinstall sysvinit-scripts and put the /etc/rc.d/rc.*.new files in place.
 
Old 05-21-2016, 02:23 PM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
sysvinit-scripts-2.0-noarch-31.txz

Reinstalled via slackpkg. None of the scripts differed from the package (other than rc.local and inittab). inittab differed only at the initial runlevel (4).
 
Old 05-21-2016, 06:45 PM   #10
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 914

Rep: Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619
Quote:
Originally Posted by Richard Cranium View Post
...
Now, /sys/fs/cgroup/cgmanager is in a cgroup filesystem which doesn't appear to allow random file creation. Certainly 'touch /sys/fs/cgroup/cgmanager/sock' as root fails with "permission denied". (Yes, I know that's not how you make a unix socket. I was trying to see what error messages that would generate when I attempted to run cgmanager again.)
That definitely needs fixing - I did a similar command 'touch /sys/fs/cgroup/cgmanager/sockX' (since cgmanager has already created sock) and it worked fine. What do your preceding directories look like? I have:
Code:
root@d6:~# ls -l /sys/fs/
total 0
drwxr-xr-x 14 root root 280 May 13 22:14 cgroup/
drwxr-xr-x 15 root root   0 May 13 22:15 ext4/
drwxr-xr-x  3 root root   0 May 13 22:14 fuse/
dr-xr-xr-x  2 root root   0 May 22 09:29 pstore/
and
Code:
root@d6:~# ls -l /sys/fs/cgroup/
total 0
dr-xr-xr-x 4 root root  0 May 22 09:25 blkio/
drwxr-xr-x 2 root root 60 May 22 09:27 cgmanager/
dr-xr-xr-x 4 root root  0 May 22 09:25 cpu/
dr-xr-xr-x 4 root root  0 May 22 09:25 cpuacct/
dr-xr-xr-x 4 root root  0 May 22 09:25 cpuset/
dr-xr-xr-x 4 root root  0 May 22 09:25 devices/
dr-xr-xr-x 4 root root  0 May 22 09:25 freezer/
dr-xr-xr-x 4 root root  0 May 22 09:25 memory/
dr-xr-xr-x 4 root root  0 May 22 09:25 net_cls/
dr-xr-xr-x 4 root root  0 May 22 09:25 net_prio/
dr-xr-xr-x 4 root root  0 May 22 09:25 perf_event/
dr-xr-xr-x 4 root root  0 May 22 09:25 pids/
and
Code:
root@d6:~# ls -l /sys/fs/cgroup/cgmanager/
total 0
srwxrwxrwx 1 root root 0 May 13 22:14 sock=
Also, do you have any old manual cgroup mounts still active? They'd be left over from previous installations - I vaguely remember having them in 13.37 & maybe 14.0 - and they might confuse things these days. Running 'mount |grep cg' should be empty.

chris
 
Old 05-21-2016, 08:37 PM   #11
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
This was a clean install on a new ssd.

Yo ho! The directory contents of /sys/fs/cgroup/ is very different on my machine.
Code:
root@hp635:~# ls -l /sys/fs/
total 0
dr-xr-xr-x  4 root root 0 May 21 11:06 cgroup/
drwxr-xr-x 10 root root 0 May 21 19:04 ext4/
drwxr-xr-x  3 root root 0 May 21 10:43 fuse/
dr-xr-xr-x  2 root root 0 May 21 19:04 pstore/
root@hp635:~# ls -l /sys/fs/cgroup/
total 0
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_merged
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_merged_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_queued
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_queued_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_bytes
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_bytes_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_time_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_serviced
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_serviced_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_wait_time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_wait_time_recursive
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.leaf_weight
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.leaf_weight_device
--w------- 1 root root 0 May 21 10:51 blkio.reset_stats
-r--r--r-- 1 root root 0 May 21 10:51 blkio.sectors
-r--r--r-- 1 root root 0 May 21 10:51 blkio.sectors_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.throttle.io_service_bytes
-r--r--r-- 1 root root 0 May 21 10:51 blkio.throttle.io_serviced
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.read_bps_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.read_iops_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.write_bps_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.write_iops_device
-r--r--r-- 1 root root 0 May 21 10:51 blkio.time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.time_recursive
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.weight
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.weight_device
drwxr-xr-x 2 root root 0 May 21 11:06 cgmanager/
-rw-r--r-- 1 root root 0 May 21 10:51 cgroup.clone_children
--w--w--w- 1 root root 0 May 21 10:51 cgroup.event_control
-rw-r--r-- 1 root root 0 May 21 10:51 cgroup.procs
-r--r--r-- 1 root root 0 May 21 10:51 cgroup.sane_behavior
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.cfs_period_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.cfs_quota_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.rt_period_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.rt_runtime_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.shares
-r--r--r-- 1 root root 0 May 21 10:51 cpu.stat
-r--r--r-- 1 root root 0 May 21 10:51 cpuacct.stat
-rw-r--r-- 1 root root 0 May 21 10:51 cpuacct.usage
-r--r--r-- 1 root root 0 May 21 10:51 cpuacct.usage_percpu
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.cpu_exclusive
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.cpus
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.effective_cpus
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.effective_mems
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mem_exclusive
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mem_hardwall
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_migrate
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.memory_pressure
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_pressure_enabled
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_spread_page
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_spread_slab
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mems
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.sched_load_balance
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.sched_relax_domain_level
--w------- 1 root root 0 May 21 10:51 devices.allow
--w------- 1 root root 0 May 21 10:51 devices.deny
-r--r--r-- 1 root root 0 May 21 10:51 devices.list
-rw-r--r-- 1 root root 0 May 21 10:51 memory.failcnt
--w------- 1 root root 0 May 21 10:51 memory.force_empty
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.slabinfo
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.max_usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.memsw.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.move_charge_at_immigrate
-rw-r--r-- 1 root root 0 May 21 10:51 memory.oom_control
---------- 1 root root 0 May 21 10:51 memory.pressure_level
-rw-r--r-- 1 root root 0 May 21 10:51 memory.soft_limit_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.stat
-rw-r--r-- 1 root root 0 May 21 10:51 memory.swappiness
-r--r--r-- 1 root root 0 May 21 10:51 memory.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.use_hierarchy
-rw-r--r-- 1 root root 0 May 21 10:51 net_cls.classid
-rw-r--r-- 1 root root 0 May 21 10:51 net_prio.ifpriomap
-r--r--r-- 1 root root 0 May 21 10:51 net_prio.prioidx
-rw-r--r-- 1 root root 0 May 21 10:51 notify_on_release
-rw-r--r-- 1 root root 0 May 21 10:51 release_agent
drwxrwxr-x 2 root root 0 May 21 10:43 sysdefault/
-rw-r--r-- 1 root root 0 May 21 10:51 tasks
root@hp635:~# ls -l /sys/fs/cgroup/cgmanager/
total 0
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_merged
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_merged_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_queued
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_queued_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_bytes
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_bytes_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_service_time_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_serviced
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_serviced_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_wait_time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.io_wait_time_recursive
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.leaf_weight
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.leaf_weight_device
--w------- 1 root root 0 May 21 10:51 blkio.reset_stats
-r--r--r-- 1 root root 0 May 21 10:51 blkio.sectors
-r--r--r-- 1 root root 0 May 21 10:51 blkio.sectors_recursive
-r--r--r-- 1 root root 0 May 21 10:51 blkio.throttle.io_service_bytes
-r--r--r-- 1 root root 0 May 21 10:51 blkio.throttle.io_serviced
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.read_bps_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.read_iops_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.write_bps_device
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.throttle.write_iops_device
-r--r--r-- 1 root root 0 May 21 10:51 blkio.time
-r--r--r-- 1 root root 0 May 21 10:51 blkio.time_recursive
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.weight
-rw-r--r-- 1 root root 0 May 21 10:51 blkio.weight_device
-rw-r--r-- 1 root root 0 May 21 10:51 cgroup.clone_children
--w--w--w- 1 root root 0 May 21 10:51 cgroup.event_control
-rw-r--r-- 1 root root 0 May 21 10:51 cgroup.procs
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.cfs_period_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.cfs_quota_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.rt_period_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.rt_runtime_us
-rw-r--r-- 1 root root 0 May 21 10:51 cpu.shares
-r--r--r-- 1 root root 0 May 21 10:51 cpu.stat
-r--r--r-- 1 root root 0 May 21 10:51 cpuacct.stat
-rw-r--r-- 1 root root 0 May 21 10:51 cpuacct.usage
-r--r--r-- 1 root root 0 May 21 10:51 cpuacct.usage_percpu
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.cpu_exclusive
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.cpus
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.effective_cpus
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.effective_mems
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mem_exclusive
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mem_hardwall
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_migrate
-r--r--r-- 1 root root 0 May 21 10:51 cpuset.memory_pressure
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_spread_page
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.memory_spread_slab
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.mems
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.sched_load_balance
-rw-r--r-- 1 root root 0 May 21 10:51 cpuset.sched_relax_domain_level
--w------- 1 root root 0 May 21 10:51 devices.allow
--w------- 1 root root 0 May 21 10:51 devices.deny
-r--r--r-- 1 root root 0 May 21 10:51 devices.list
-r--r--r-- 1 root root 0 May 21 10:51 freezer.parent_freezing
-r--r--r-- 1 root root 0 May 21 10:51 freezer.self_freezing
-rw-r--r-- 1 root root 0 May 21 10:51 freezer.state
-rw-r--r-- 1 root root 0 May 21 10:51 memory.failcnt
--w------- 1 root root 0 May 21 10:51 memory.force_empty
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.slabinfo
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.tcp.usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.kmem.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.max_usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.failcnt
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.limit_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.memsw.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.memsw.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.move_charge_at_immigrate
-rw-r--r-- 1 root root 0 May 21 10:51 memory.oom_control
---------- 1 root root 0 May 21 10:51 memory.pressure_level
-rw-r--r-- 1 root root 0 May 21 10:51 memory.soft_limit_in_bytes
-r--r--r-- 1 root root 0 May 21 10:51 memory.stat
-rw-r--r-- 1 root root 0 May 21 10:51 memory.swappiness
-r--r--r-- 1 root root 0 May 21 10:51 memory.usage_in_bytes
-rw-r--r-- 1 root root 0 May 21 10:51 memory.use_hierarchy
-rw-r--r-- 1 root root 0 May 21 10:51 net_cls.classid
-rw-r--r-- 1 root root 0 May 21 10:51 net_prio.ifpriomap
-r--r--r-- 1 root root 0 May 21 10:51 net_prio.prioidx
-rw-r--r-- 1 root root 0 May 21 10:51 notify_on_release
-r--r--r-- 1 root root 0 May 21 10:51 pids.current
-rw-r--r-- 1 root root 0 May 21 10:51 pids.max
-rw-r--r-- 1 root root 0 May 21 10:51 tasks
root@hp635:~#
 
Old 05-21-2016, 09:43 PM   #12
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 914

Rep: Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619
My reading of your different /sys/fs/cgroup contents is that in rc.S (just before cgmanager would be started), autodetection of cgroup controllers failed so everything is lumped into the cgroup directory - the line: mount -t cgroup cgroup /sys/fs/cgroup. That line is reached based on failure of:
Code:
if [ -x /usr/bin/lssubsys -a -x /usr/bin/tr -a -x /usr/bin/sed ]; then
raising the question of why that test of common executables would fail. I presume you have them and they're executable?


The other problem is that your cgroup directory is not writable by owner.
Quote:
Originally Posted by Richard Cranium View Post
This was a clean install on a new ssd.

Yo ho! The directory contents of /sys/fs/cgroup/ is very different on my machine.
Code:
root@hp635:~# ls -l /sys/fs/
total 0
dr-xr-xr-x  4 root root 0 May 21 11:06 cgroup/
drwxr-xr-x 10 root root 0 May 21 19:04 ext4/
drwxr-xr-x  3 root root 0 May 21 10:43 fuse/
dr-xr-xr-x  2 root root 0 May 21 19:04 pstore/
I'm not sure why that would be so but, for now, you could try adding a line in rc.S 'chmod 0755 /sys/fs/cgroup' just after the line 'if [ -d /sys/fs/cgroup ]; then' (then reboot).

chris
Last edited by chris.willing; 05-21-2016 at 09:45 PM. Reason: typo
 
Old 05-22-2016, 12:39 AM   #13
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by chris.willing View Post
My reading of your different /sys/fs/cgroup contents is that in rc.S (just before cgmanager would be started), autodetection of cgroup controllers failed so everything is lumped into the cgroup directory - the line: mount -t cgroup cgroup /sys/fs/cgroup. That line is reached based on failure of:
Code:
if [ -x /usr/bin/lssubsys -a -x /usr/bin/tr -a -x /usr/bin/sed ]; then
raising the question of why that test of common executables would fail. I presume you have them and they're executable?
They certainly appear to be...
Code:
cranium@hp635:~$ ls -l /usr/bin/lssubsys 
-rwxr-xr-x 1 root root 9152 Aug 25  2014 /usr/bin/lssubsys*
flacy@hp635:~$ ls -l /usr/bin/tr
lrwxrwxrwx 1 root root 12 Apr 18 22:38 /usr/bin/tr -> ../../bin/tr*
flacy@hp635:~$ ls -l /usr/bin/sed
lrwxrwxrwx 1 root root 8 Apr  4 08:08 /usr/bin/sed -> /bin/sed*
cranium@hp635:~$
Quote:
The other problem is that your cgroup directory is not writable by owner.


I'm not sure why that would be so but, for now, you could try adding a line in rc.S 'chmod 0755 /sys/fs/cgroup' just after the line 'if [ -d /sys/fs/cgroup ]; then' (then reboot).

chris
I shall do that and report back shortly.
 
Old 05-22-2016, 12:57 AM   #14
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Original Poster
Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
That does not appear to make a positive difference...
Code:
root@hp635:~# ls -l /sys/fs/
total 0
dr-xr-xr-x  2 root root 0 May 22 00:45 cgroup/
drwxr-xr-x 10 root root 0 May 22 00:45 ext4/
drwxr-xr-x  3 root root 0 May 22 00:45 fuse/
dr-xr-xr-x  2 root root 0 May 22 00:45 pstore/
root@hp635:~# ls -l /sys/fs/cgroup/
total 0
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_merged
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_merged_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_queued
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_queued_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_service_bytes
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_service_bytes_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_service_time
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_service_time_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_serviced
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_serviced_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_wait_time
-r--r--r-- 1 root root 0 May 22 00:48 blkio.io_wait_time_recursive
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.leaf_weight
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.leaf_weight_device
--w------- 1 root root 0 May 22 00:48 blkio.reset_stats
-r--r--r-- 1 root root 0 May 22 00:48 blkio.sectors
-r--r--r-- 1 root root 0 May 22 00:48 blkio.sectors_recursive
-r--r--r-- 1 root root 0 May 22 00:48 blkio.throttle.io_service_bytes
-r--r--r-- 1 root root 0 May 22 00:48 blkio.throttle.io_serviced
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.throttle.read_bps_device
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.throttle.read_iops_device
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.throttle.write_bps_device
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.throttle.write_iops_device
-r--r--r-- 1 root root 0 May 22 00:48 blkio.time
-r--r--r-- 1 root root 0 May 22 00:48 blkio.time_recursive
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.weight
-rw-r--r-- 1 root root 0 May 22 00:48 blkio.weight_device
-rw-r--r-- 1 root root 0 May 22 00:48 cgroup.clone_children
--w--w--w- 1 root root 0 May 22 00:48 cgroup.event_control
-rw-r--r-- 1 root root 0 May 22 00:48 cgroup.procs
-r--r--r-- 1 root root 0 May 22 00:48 cgroup.sane_behavior
-rw-r--r-- 1 root root 0 May 22 00:44 cpu.cfs_period_us
-rw-r--r-- 1 root root 0 May 22 00:44 cpu.cfs_quota_us
-rw-r--r-- 1 root root 0 May 22 00:48 cpu.rt_period_us
-rw-r--r-- 1 root root 0 May 22 00:48 cpu.rt_runtime_us
-rw-r--r-- 1 root root 0 May 22 00:48 cpu.shares
-r--r--r-- 1 root root 0 May 22 00:48 cpu.stat
-r--r--r-- 1 root root 0 May 22 00:48 cpuacct.stat
-rw-r--r-- 1 root root 0 May 22 00:48 cpuacct.usage
-r--r--r-- 1 root root 0 May 22 00:48 cpuacct.usage_percpu
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.cpu_exclusive
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.cpus
-r--r--r-- 1 root root 0 May 22 00:48 cpuset.effective_cpus
-r--r--r-- 1 root root 0 May 22 00:48 cpuset.effective_mems
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.mem_exclusive
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.mem_hardwall
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.memory_migrate
-r--r--r-- 1 root root 0 May 22 00:48 cpuset.memory_pressure
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.memory_pressure_enabled
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.memory_spread_page
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.memory_spread_slab
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.mems
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.sched_load_balance
-rw-r--r-- 1 root root 0 May 22 00:48 cpuset.sched_relax_domain_level
--w------- 1 root root 0 May 22 00:48 devices.allow
--w------- 1 root root 0 May 22 00:48 devices.deny
-r--r--r-- 1 root root 0 May 22 00:48 devices.list
-rw-r--r-- 1 root root 0 May 22 00:48 memory.failcnt
--w------- 1 root root 0 May 22 00:48 memory.force_empty
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.failcnt
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.limit_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 22 00:48 memory.kmem.slabinfo
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.tcp.failcnt
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.tcp.limit_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.kmem.tcp.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 22 00:48 memory.kmem.tcp.usage_in_bytes
-r--r--r-- 1 root root 0 May 22 00:48 memory.kmem.usage_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.limit_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.max_usage_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.memsw.failcnt
-rw-r--r-- 1 root root 0 May 22 00:44 memory.memsw.limit_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.memsw.max_usage_in_bytes
-r--r--r-- 1 root root 0 May 22 00:48 memory.memsw.usage_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.move_charge_at_immigrate
-rw-r--r-- 1 root root 0 May 22 00:44 memory.oom_control
---------- 1 root root 0 May 22 00:48 memory.pressure_level
-rw-r--r-- 1 root root 0 May 22 00:48 memory.soft_limit_in_bytes
-r--r--r-- 1 root root 0 May 22 00:48 memory.stat
-rw-r--r-- 1 root root 0 May 22 00:44 memory.swappiness
-r--r--r-- 1 root root 0 May 22 00:48 memory.usage_in_bytes
-rw-r--r-- 1 root root 0 May 22 00:48 memory.use_hierarchy
-rw-r--r-- 1 root root 0 May 22 00:48 net_cls.classid
-rw-r--r-- 1 root root 0 May 22 00:48 net_prio.ifpriomap
-r--r--r-- 1 root root 0 May 22 00:48 net_prio.prioidx
-rw-r--r-- 1 root root 0 May 22 00:48 notify_on_release
-rw-r--r-- 1 root root 0 May 22 00:48 release_agent
-rw-r--r-- 1 root root 0 May 22 00:48 tasks
root@hp635:~#
 
Old 05-22-2016, 02:57 AM   #15
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 914

Rep: Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619Reputation: 619
Quote:
Originally Posted by Richard Cranium View Post
That does not appear to make a positive difference...
Code:
root@hp635:~# ls -l /sys/fs/
total 0
dr-xr-xr-x  2 root root 0 May 22 00:45 cgroup/
drwxr-xr-x 10 root root 0 May 22 00:45 ext4/
drwxr-xr-x  3 root root 0 May 22 00:45 fuse/
dr-xr-xr-x  2 root root 0 May 22 00:45 pstore/
root@hp635:~# ls -l /sys/fs/cgroup/
...
Are you able to change that permission manually (forgetting the script for now) i.e. chmod u+w /sys/fs/cgroup ?

It might also be worth searching for "cgroup" in /var/log/messages & syslog to check whether there have been any problems reported mounting/initialising cgroups correctly.

chris
 
  


Reply
Page 1 of 2 1 2


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error starting pavucontrol on Slackware-current (32bit only) allend Slackware 2 01-18-2016 07:42 PM
Should I run cgmanager on desktop? BratPit Slackware 1 11-19-2015 05:08 PM
[SOLVED] Problem starting Xorg Slackware-Current with nouveau Melke Slackware 14 05-04-2015 04:11 PM
vbox 4.1.10, slackware current 64, kde not starting for regular user glorsplitz Slackware 1 03-27-2012 07:55 PM
[SOLVED] Slackware64-current (16/1/2011) - KDE not starting samac Slackware 3 01-16-2011 04:46 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:18 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration