I hope it's okay if I post my response to the cockpit mailing list.
On 06.03.2016 11:01, Jean-Paul Geerets wrote:
recently i fount the application "cockpit".
it looks great and i wanna give it a try on my vps.
it is a openvz with centos7 on it.
install was very easy, not a problem.
after login to the website, it kicks me out in a few seconds.
when searching, i found these errors:
---
cockpit-protocol-Message: grep: couldn't run grep: Failed to change to
directory '/sys/devices/virtual/dmi/id' (No such file or directory)
cockpit-bridge-Message: Reauthorizing unix-user:<username>
cockpit-polkit: user <username>was reauthorized
cockpit-bridge-Message: cockpit-polkit helper exited with status: 0
cockpit-protocol-Message: grep: couldn't run grep: Failed to change to
directory '/sys/devices/virtual/dmi/id' (No such file or directory)
cockpit-bridge-Message: error loading contents /proc/vmstat: Failed to
open file '/proc/diskstats': No such file or directory
cockpit-bridge-Message: error loading contents /proc/vmstat: Failed to
open file '/proc/diskstats': No such file or directory
cockpit-bridge-Message: error loading contents /proc/diskstats: Failed
to open file '/proc/diskstats': No such file or directory
exec gdb failed: No such file or directory
Error: signal Segmentation fault:
cockpit-bridge(+0x35269)[0x7fd7df09c269]
/lib64/libc.so.6(+0x35670)[0x7fd7dd74e670]
/lib64/libglib-2.0.so.0(g_slice_alloc+0xa7)[0x7fd7de5ab4d7]
/lib64/libglib-2.0.so.0(g_slice_alloc0+0xe)[0x7fd7de5ab9ae]
/lib64/libjson-glib-1.0.so.0(+0x1a17e)[0x7fd7de33b17e]
/lib64/libjson-glib-1.0.so.0(json_node_set_int+0x7d)[0x7fd7de3319fd]
/lib64/libjson-glib-1.0.so.0(json_node_init_int+0x26)[0x7fd7de331a46]
/lib64/libjson-glib-1.0.so.0(json_object_set_int_member+0x2b)[0x7fd7de33217b]
cockpit-bridge(+0x19066)[0x7fd7df080066]
---
version of cockpit-ws:
---
Version: 0.93
Protocol: 1
Authorization: crypt1
---
i hope you can give me some advice on what to do to get this running.
This bug is in the error handling of the code that fails to read
diskstats. The bug was fixed recently in version 0.96:
https://github.com/cockpit-project/cockpit/issues/3812
Hope that helps.
Cheers,
Stef