-
Notifications
You must be signed in to change notification settings - Fork 726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"error opening device /dev/sysdig0" #30
Comments
Thanks for using sysdig! Which distribution are you using, and can you send the output of |
(The dashes are the hostname, which I'm scrubbing.) On Thu, Apr 3, 2014 at 2:12 PM, Gianluca Borello
|
Distribution? I might have to replicate it here and see if you're actually using a kernel version for which the headers are still available from the distro repo. |
Ubuntu 10.04 On Thu, Apr 3, 2014 at 2:16 PM, Gianluca Borello
|
It looks like the custom kernels distributed by Linode don't ship with kernel headers, and there's no trivial way to get them. I managed to make it work on Ubuntu 10.04 on Linode by switching to a distribution-provided kernel (for which the kernel headers are correctly available from the Canonical repos) and enabling pv-grub under the linode console. These are roughly the steps that I followed: https://library.linode.com/custom-instances/pv-grub-howto#sph_ubuntu-10-04-lts-lucid I understand this can be a pain in the ass, but unfortunately how cloud providers decide to ship kernels is totally out of our control, we can just advise to use the kernels from your original linux distribution in this case. |
Ouch, that's a bummer! I probably won't make that switch, sorry to say, but Thanks for your help. On Thu, Apr 3, 2014 at 4:44 PM, Gianluca Borello
|
Thanks! If sysdig gets more traction, we'll put some more effort into improving the binary installation by providing precompiled modules for a bunch of kernel versions out there. I see that those Linode kernels all have a /proc/config.gz, so in theory we might be able to regenerate them on our machines and build a sysdig-probe binary. That's definitely a whole lot of work. In the meantime I'm closing the issue, please if you have a chance try sysdig on other machines :) |
I was excited to finally get a chance to use sysdig; a friend recommended it to me a couple of months back and I luckily haven't needed it until now. I unfortunately also ran into this issue (customer's server is Ubuntu 10.04 on Linode as well) so I'm still waiting for the chance to try out the product. |
I got the same error on fedora 21(Linux localhost.localdomain 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) |
What version of the kernel-devel you currently have installed? |
my kernel-devel is kernel-devel-3.17.8-300.fc21.x86_64. |
So if this is installed it should work. Please send the output of:
Also, make sure to run sysdig as root |
All log, And it don't work, What happened? [root@localhost chenhao]# dnf install sysdig
依赖关系解决。
==========================================================================================================================
软件包 架构 版本 仓库 大小
==========================================================================================================================
安装:
sysdig x86_64 0.1.94-1 draios 549 k
事务概要
==========================================================================================================================
安装 1 Package
总下载:549 k
安装大小:1.8 M
确定吗?[y/N]:y
下载软件包:
sysdig-0.1.94-x86_64.rpm 58 kB/s | 549 kB 00:09
--------------------------------------------------------------------------------------------------------------------------
总计 58 kB/s | 549 kB 00:09
运行事务检查
事务检查成功。
运行事务测试
事务测试成功。
运行事务
安装: sysdig-0.1.94-1.x86_64 1/1
Creating symlink /var/lib/dkms/sysdig/0.1.94/source ->
/usr/src/sysdig-0.1.94
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make KERNELRELEASE=3.17.8-300.fc21.x86_64 -C /lib/modules/3.17.8-300.fc21.x86_64/build M=/var/lib/dkms/sysdig/0.1.94/build...
cleaning build area...
DKMS: build completed.
sysdig-probe:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.17.8-300.fc21.x86_64/extra/
Adding any weak-modules
depmod...
DKMS: install completed.
验证: sysdig-0.1.94-1.x86_64 1/1
已安装:
sysdig.x86_64 0.1.94-1
完毕!
[root@localhost chenhao]# sysdig
Unable to load the driver
error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded.
[root@localhost chenhao]# rpm -qa|grep kernel
kernel-core-3.17.8-300.fc21.x86_64
abrt-addon-kerneloops-2.3.0-3.fc21.x86_64
kernel-headers-3.17.8-300.fc21.x86_64
libreport-plugin-kerneloops-2.3.0-5.fc21.x86_64
kernel-devel-3.17.8-300.fc21.x86_64
kernel-3.17.8-300.fc21.x86_64
kernel-modules-3.17.8-300.fc21.x86_64
[root@localhost chenhao]# /usr/lib/dkms/dkms_autoinstaller start
dkms: running auto installation service for kernel 3.17.8-300.fc21.x86_64
Done.
[root@localhost chenhao]# sysdig
Unable to load the driver
error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded.
[root@localhost chenhao]# ls /lib/modules
3.17.8-300.fc21.x86_64
[root@localhost chenhao]# find /lib/modules | grep sysdig
/lib/modules/3.17.8-300.fc21.x86_64/extra/sysdig-probe.ko |
I just tried with a brand new fc21 and it worked out of the box for me. Can you try and see what's the output for:
|
[root@localhost ~]# modprobe sysdig-probe
modprobe: ERROR: could not insert 'sysdig_probe': Required key not available
[root@localhost ~]# insmod /lib/modules/3.17.8-300.fc21.x86_64/extra/sysdig-probe.ko
insmod: ERROR: could not insert module /lib/modules/3.17.8-300.fc21.x86_64/extra/sysdig-probe.ko: Required key not available
[root@localhost ~]# cat /var/log/messages
cat: /var/log/messages: 没有那个文件或目录 |
Looks like you have secure boot enabled on your system, and so your kernel refuses to load any module that didn't ship with the distribution. Would you be able to try disabling secure boot? You can use this thread as a reference: Unfortunately, unless the Fedora maintainers decide to ship sysdig in their distribution (and sign the precompiled module with their key) that seems like the only feasible solution. |
Thank you for your answer.It worked after i turned secure boot off. |
I'm having the same error on Amazon Linux
|
Please make sure the kernel devel files were updated, and try to relaunch dkms and post the output if you got any error:
|
I couldn't start, but after |
Thanks so much, Reeze! That solved it for me as well |
Thanks do much Reeze! It also solved my problem |
you need run this command:
it's works. |
I ran into this error after attempting the "basic install" for Linux as outlined here. I'm running a Fedora 23 VM that hadn't been updated in probably 2 months. Anyway, it would have been nice if the basic install instructions had cautioned me to make sure my system was up to date before running the It also wasn't clear to me how to fix things at this point. I ended up using the a package remove / install and now it appears to be working:
|
Usually if your system is out-of-date it fails to download the exact version of kernel-headers because they may be not available anymore. In that case you can upgrade the kernel and relaunch manually |
am also facing the same problem |
@magoo23 Have you installed kernel-headers? The package is called |
luca3m let me try and install the kernel headers |
😭
|
@ahjdzx you are apparently running in secure boot mode, so it really makes sense that a third party module doesn't work. I suggest to disable it from your BIOS, or follow the instructions at http://askubuntu.com/questions/762254/why-do-i-get-required-key-not-available-when-install-dkms-modules-in-ubuntu-16 Essentially, this comment still applies: #30 (comment) |
I am trying to run sysdig on https://www.scaleway.com/. I am running into an error: $ sysdig
Unable to load the driver
error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded. I have installed sysdig using: rpm --import https://s3.amazonaws.com/download.draios.com/DRAIOS-GPG-KEY.public
curl -s -o /etc/yum.repos.d/draios.repo http://download.draios.com/stable/rpm/draios.repo
rpm -i http://mirror.us.leaseweb.net/epel/6/i386/epel-release-6-8.noarch.rpm
yum -y install kernel-devel-$(uname -r) The following has failed: $ yum -y install kernel-devel-$(uname -r)
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.nl.leaseweb.net
* epel: mirror.1000mbps.com
* extras: mirror.1000mbps.com
* updates: mirror.1000mbps.com
No package kernel-devel-4.5.7-std-3 available.
Error: Nothing to do I don't understand whats the reason the kernel version appears as "4.5.7-std-3": $ uname -a
Linux k8s-master-0001 4.5.7-std-3 #1 SMP Tue Jul 12 09:56:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7" The installed kernel-header version is v3.10: $ yum list kernel*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.nl.leaseweb.net
* epel: mirror.1000mbps.com
* extras: mirror.1000mbps.com
* updates: mirror.1000mbps.com
Installed Packages
kernel-devel.x86_64 3.10.0-514.2.2.el7 @updates
kernel-headers.x86_64 3.10.0-514.2.2.el7 @updates
Available Packages
kernel.x86_64 3.10.0-514.2.2.el7 updates
kernel-abi-whitelists.noarch 3.10.0-514.2.2.el7 updates
kernel-debug.x86_64 3.10.0-514.2.2.el7 updates
kernel-debug-devel.x86_64 3.10.0-514.2.2.el7 updates
kernel-doc.noarch 3.10.0-514.2.2.el7 updates
kernel-tools.x86_64 3.10.0-514.2.2.el7 updates
kernel-tools-libs.x86_64 3.10.0-514.2.2.el7 updates
kernel-tools-libs-devel.x86_64 3.10.0-514.2.2.el7 updates What am I missing? |
Never used Scaleway, but these are my comments:
|
This is a dedicated server. |
Same issue here with CentOS 7 [root@dcosb tmp]# modprobe sysdig-probe [root@dcosb tmp]# uname -r [root@dcosb tmp]# sudo yum -y install kernel-devel-$(uname -r)
[root@dcosb tmp]# /usr/lib/dkms/dkms_autoinstaller start BUT
|
3.10.0-327 kernel headers are not available any more on centos repositories, you have two options:
|
Upgraded to newest kernel, everything works, thanks @luca3m |
@luca3m I am getting the same problem with: [root@k8s-worker ~]# uname -r
4.5.7-std-3
Here is the full installation log:
|
Has this been done? |
I have prepared the kernel, then exported
Is it me missing something? |
Im using in WSL "uname -a" : Linux BR2L11792L 4.4.0-17763-Microsoft #864-Microsoft Thu Nov 07 15:22:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux and still getting the error output from sysdig: "Unable to load the driver error opening device /dev/sysdig0. Make sure you have root credentials and that the sysdig-probe module is loaded." |
Hi @Josh7GAS. The issue you have chimed in on has been closed for longer than WSL has existed :) The sysdig tool does not formally support WSL. WSL2 runs a Linux kernel inside a virtual machine (available here), so there's a possibility that sysdig might be able to run on top of WSL2 without too much major surgery, although it would come with the caveat that it would only monitor syscalls performed by the WSL virtual machine and not by the host Windows system. However, all of the above is entirely speculative. I don't even have a Windows system to try to run it myself. |
The full error message:
Installation did fail to install linux headers. Any advice?
The text was updated successfully, but these errors were encountered: